mirror of
https://github.com/ngthanhvu/kr-phim.git
synced 2026-08-10 12:27:47 +00:00
feat: add 188+ agent skills (.agents/) and update project guidelines
- Add 188+ AI agent skill files across 11 categories (Development, DevOps, Security, Data, Design, Writing, Integrations, Documents & Media, Education) - Update CLAUDE.md with new CI/CD Builder skill reference - Update AGENTS.md with complete skill index organized by category - Update .cursorrules configuration file - Add .gitea/ workflows directory
This commit is contained in:
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: ab-test-designer
|
||||
display_name: A/B Test Designer
|
||||
description: Design and analyze A/B tests — sample sizes, significance testing, multiple comparisons, and results interpretation.
|
||||
category: Data & Analytics
|
||||
platforms: [claude.ai, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [ab-test-designer]
|
||||
---
|
||||
|
||||
# A/B Test Designer
|
||||
|
||||
## Overview
|
||||
|
||||
Design and analyze A/B tests — sample sizes, significance testing, multiple comparisons, and results interpretation.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **A/B Test Designer** when you need to:
|
||||
|
||||
- Work with a/b test designer tasks in your project or workflow
|
||||
- Automate a/b test designer operations at scale
|
||||
- Generate production-quality a/b test designer output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your a/b test designer request
|
||||
2. Apply best practices and conventions for Data & Analytics
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with a/b test designer.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for a/b test designer in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready a/b test designer setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened a/b test designer implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: accessibility-checker
|
||||
display_name: Accessibility Checker
|
||||
description: Audit and fix accessibility issues — WCAG 2.2 compliance, ARIA labels, color contrast, keyboard navigation, and screen-reader compatibility.
|
||||
category: Creative & Design
|
||||
platforms: [claude.ai, claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [accessibility-checker]
|
||||
---
|
||||
|
||||
# Accessibility Checker
|
||||
|
||||
## Overview
|
||||
|
||||
Audit and fix accessibility issues — WCAG 2.2 compliance, ARIA labels, color contrast, keyboard navigation, and screen-reader compatibility.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Accessibility Checker** when you need to:
|
||||
|
||||
- Work with accessibility checker tasks in your project or workflow
|
||||
- Automate accessibility checker operations at scale
|
||||
- Generate production-quality accessibility checker output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your accessibility checker request
|
||||
2. Apply best practices and conventions for Creative & Design
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with accessibility checker.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for accessibility checker in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready accessibility checker setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened accessibility checker implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: axe, lighthouse
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: action-tracker
|
||||
display_name: Action Tracker
|
||||
description: Track and manage action items — owners, deadlines, status updates, and escalation workflows.
|
||||
category: Business & Productivity
|
||||
platforms: [claude.ai, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [action-tracker]
|
||||
---
|
||||
|
||||
# Action Tracker
|
||||
|
||||
## Overview
|
||||
|
||||
Track and manage action items — owners, deadlines, status updates, and escalation workflows.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Action Tracker** when you need to:
|
||||
|
||||
- Work with action tracker tasks in your project or workflow
|
||||
- Automate action tracker operations at scale
|
||||
- Generate production-quality action tracker output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your action tracker request
|
||||
2. Apply best practices and conventions for Business & Productivity
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with action tracker.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for action tracker in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready action tracker setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened action tracker implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: alerting-config
|
||||
display_name: Alerting Config
|
||||
description: Design alert configurations — thresholds, severity levels, routing, de-duplication, and escalation policies.
|
||||
category: DevOps & Infrastructure
|
||||
platforms: [claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [alerting-config]
|
||||
---
|
||||
|
||||
# Alerting Config
|
||||
|
||||
## Overview
|
||||
|
||||
Design alert configurations — thresholds, severity levels, routing, de-duplication, and escalation policies.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Alerting Config** when you need to:
|
||||
|
||||
- Work with alerting config tasks in your project or workflow
|
||||
- Automate alerting config operations at scale
|
||||
- Generate production-quality alerting config output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your alerting config request
|
||||
2. Apply best practices and conventions for DevOps & Infrastructure
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with alerting config.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for alerting config in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready alerting config setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened alerting config implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: pagerduty, alertmanager
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: algorithmic-art
|
||||
display_name: Algorithmic Art
|
||||
description: Generate creative algorithmic and generative art using code — fractals, parametric patterns, noise fields, and procedural imagery.
|
||||
category: Creative & Design
|
||||
platforms: [claude.ai, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [algorithmic-art]
|
||||
---
|
||||
|
||||
# Algorithmic Art
|
||||
|
||||
## Overview
|
||||
|
||||
Generate creative algorithmic and generative art using code — fractals, parametric patterns, noise fields, and procedural imagery.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Algorithmic Art** when you need to:
|
||||
|
||||
- Work with algorithmic art tasks in your project or workflow
|
||||
- Automate algorithmic art operations at scale
|
||||
- Generate production-quality algorithmic art output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your algorithmic art request
|
||||
2. Apply best practices and conventions for Creative & Design
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with algorithmic art.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for algorithmic art in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready algorithmic art setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened algorithmic art implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: python, p5js
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: angular-component
|
||||
display_name: Angular Component
|
||||
description: Develop Angular components — services, pipes, directives, reactive forms, RxJS, and Angular Material.
|
||||
category: Development
|
||||
platforms: [claude.ai, claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [angular-component]
|
||||
---
|
||||
|
||||
# Angular Component
|
||||
|
||||
## Overview
|
||||
|
||||
Develop Angular components — services, pipes, directives, reactive forms, RxJS, and Angular Material.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Angular Component** when you need to:
|
||||
|
||||
- Work with angular component tasks in your project or workflow
|
||||
- Automate angular component operations at scale
|
||||
- Generate production-quality angular component output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your angular component request
|
||||
2. Apply best practices and conventions for Development
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with angular component.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for angular component in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready angular component setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened angular component implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: angular, typescript, rxjs
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: api-designer
|
||||
display_name: API Designer
|
||||
description: Design RESTful and RPC APIs — OpenAPI specs, request/response schemas, error codes, versioning, and documentation.
|
||||
category: Development
|
||||
platforms: [claude.ai, claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [api-designer]
|
||||
---
|
||||
|
||||
# API Designer
|
||||
|
||||
## Overview
|
||||
|
||||
Design RESTful and RPC APIs — OpenAPI specs, request/response schemas, error codes, versioning, and documentation.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **API Designer** when you need to:
|
||||
|
||||
- Work with api designer tasks in your project or workflow
|
||||
- Automate api designer operations at scale
|
||||
- Generate production-quality api designer output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your api designer request
|
||||
2. Apply best practices and conventions for Development
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with api designer.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for api designer in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready api designer setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened api designer implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: openapi, swagger
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: aws-architect
|
||||
display_name: AWS Architect
|
||||
description: Design AWS architectures — VPCs, EC2, ECS, Lambda, RDS, S3, CloudFront, and Well-Architected Framework reviews.
|
||||
category: DevOps & Infrastructure
|
||||
platforms: [claude.ai, claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [aws-architect]
|
||||
---
|
||||
|
||||
# AWS Architect
|
||||
|
||||
## Overview
|
||||
|
||||
Design AWS architectures — VPCs, EC2, ECS, Lambda, RDS, S3, CloudFront, and Well-Architected Framework reviews.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **AWS Architect** when you need to:
|
||||
|
||||
- Work with aws architect tasks in your project or workflow
|
||||
- Automate aws architect operations at scale
|
||||
- Generate production-quality aws architect output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your aws architect request
|
||||
2. Apply best practices and conventions for DevOps & Infrastructure
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with aws architect.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for aws architect in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready aws architect setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened aws architect implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: aws, terraform
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: azure-architect
|
||||
display_name: Azure Architect
|
||||
description: Design Azure architectures — AKS, Functions, Cosmos DB, Service Bus, and Azure AD integration patterns.
|
||||
category: DevOps & Infrastructure
|
||||
platforms: [claude.ai, claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [azure-architect]
|
||||
---
|
||||
|
||||
# Azure Architect
|
||||
|
||||
## Overview
|
||||
|
||||
Design Azure architectures — AKS, Functions, Cosmos DB, Service Bus, and Azure AD integration patterns.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Azure Architect** when you need to:
|
||||
|
||||
- Work with azure architect tasks in your project or workflow
|
||||
- Automate azure architect operations at scale
|
||||
- Generate production-quality azure architect output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your azure architect request
|
||||
2. Apply best practices and conventions for DevOps & Infrastructure
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with azure architect.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for azure architect in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready azure architect setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened azure architect implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: azure, terraform
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: bias-detector
|
||||
display_name: Bias Detector
|
||||
description: Detect cognitive and statistical biases — confirmation bias, survivorship bias, sampling issues, and logical fallacies.
|
||||
category: Research & Analysis
|
||||
platforms: [claude.ai, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [bias-detector]
|
||||
---
|
||||
|
||||
# Bias Detector
|
||||
|
||||
## Overview
|
||||
|
||||
Detect cognitive and statistical biases — confirmation bias, survivorship bias, sampling issues, and logical fallacies.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Bias Detector** when you need to:
|
||||
|
||||
- Work with bias detector tasks in your project or workflow
|
||||
- Automate bias detector operations at scale
|
||||
- Generate production-quality bias detector output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your bias detector request
|
||||
2. Apply best practices and conventions for Research & Analysis
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with bias detector.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for bias detector in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready bias detector setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened bias detector implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: blog-writer
|
||||
display_name: Blog Writer
|
||||
description: Write SEO-optimized blog posts — research, outline, draft, and polish articles that rank and convert.
|
||||
category: Writing & Communication
|
||||
platforms: [claude.ai, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [blog-writer]
|
||||
---
|
||||
|
||||
# Blog Writer
|
||||
|
||||
## Overview
|
||||
|
||||
Write SEO-optimized blog posts — research, outline, draft, and polish articles that rank and convert.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Blog Writer** when you need to:
|
||||
|
||||
- Work with blog writer tasks in your project or workflow
|
||||
- Automate blog writer operations at scale
|
||||
- Generate production-quality blog writer output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your blog writer request
|
||||
2. Apply best practices and conventions for Writing & Communication
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with blog writer.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for blog writer in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready blog writer setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened blog writer implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: brand-guidelines
|
||||
display_name: Brand Guidelines
|
||||
description: Create and enforce brand identity guidelines — logo usage, color palettes, typography, tone-of-voice, and asset libraries.
|
||||
category: Creative & Design
|
||||
platforms: [claude.ai, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [brand-guidelines]
|
||||
---
|
||||
|
||||
# Brand Guidelines
|
||||
|
||||
## Overview
|
||||
|
||||
Create and enforce brand identity guidelines — logo usage, color palettes, typography, tone-of-voice, and asset libraries.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Brand Guidelines** when you need to:
|
||||
|
||||
- Work with brand guidelines tasks in your project or workflow
|
||||
- Automate brand guidelines operations at scale
|
||||
- Generate production-quality brand guidelines output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your brand guidelines request
|
||||
2. Apply best practices and conventions for Creative & Design
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with brand guidelines.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for brand guidelines in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready brand guidelines setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened brand guidelines implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: business-plan
|
||||
display_name: Business Plan
|
||||
description: Write comprehensive business plans — executive summary, market analysis, financial projections, and competitive positioning.
|
||||
category: Business & Productivity
|
||||
platforms: [claude.ai, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [business-plan]
|
||||
---
|
||||
|
||||
# Business Plan
|
||||
|
||||
## Overview
|
||||
|
||||
Write comprehensive business plans — executive summary, market analysis, financial projections, and competitive positioning.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Business Plan** when you need to:
|
||||
|
||||
- Work with business plan tasks in your project or workflow
|
||||
- Automate business plan operations at scale
|
||||
- Generate production-quality business plan output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your business plan request
|
||||
2. Apply best practices and conventions for Business & Productivity
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with business plan.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for business plan in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready business plan setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened business plan implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: canvas-design
|
||||
display_name: Canvas Design
|
||||
description: Design and render graphics on HTML5 Canvas — illustrations, diagrams, UI mockups, and interactive visual elements.
|
||||
category: Creative & Design
|
||||
platforms: [claude.ai, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [canvas-design]
|
||||
---
|
||||
|
||||
# Canvas Design
|
||||
|
||||
## Overview
|
||||
|
||||
Design and render graphics on HTML5 Canvas — illustrations, diagrams, UI mockups, and interactive visual elements.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Canvas Design** when you need to:
|
||||
|
||||
- Work with canvas design tasks in your project or workflow
|
||||
- Automate canvas design operations at scale
|
||||
- Generate production-quality canvas design output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your canvas design request
|
||||
2. Apply best practices and conventions for Creative & Design
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with canvas design.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for canvas design in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready canvas design setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened canvas design implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: javascript, canvas
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: chart-designer
|
||||
display_name: Chart Designer
|
||||
description: Design and generate publication-quality charts — bar, line, pie, scatter, heatmaps, and interactive D3 visualizations.
|
||||
category: Creative & Design
|
||||
platforms: [claude.ai, claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [chart-designer]
|
||||
---
|
||||
|
||||
# Chart Designer
|
||||
|
||||
## Overview
|
||||
|
||||
Design and generate publication-quality charts — bar, line, pie, scatter, heatmaps, and interactive D3 visualizations.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Chart Designer** when you need to:
|
||||
|
||||
- Work with chart designer tasks in your project or workflow
|
||||
- Automate chart designer operations at scale
|
||||
- Generate production-quality chart designer output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your chart designer request
|
||||
2. Apply best practices and conventions for Creative & Design
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with chart designer.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for chart designer in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready chart designer setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened chart designer implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: python, matplotlib, d3
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: chrome-extension
|
||||
display_name: Chrome Extension
|
||||
description: Build Chrome/Edge extensions — manifest v3, content scripts, service workers, popup UIs, and Chrome API integrations.
|
||||
category: Development
|
||||
platforms: [claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [chrome-extension]
|
||||
---
|
||||
|
||||
# Chrome Extension
|
||||
|
||||
## Overview
|
||||
|
||||
Build Chrome/Edge extensions — manifest v3, content scripts, service workers, popup UIs, and Chrome API integrations.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Chrome Extension** when you need to:
|
||||
|
||||
- Work with chrome extension tasks in your project or workflow
|
||||
- Automate chrome extension operations at scale
|
||||
- Generate production-quality chrome extension output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your chrome extension request
|
||||
2. Apply best practices and conventions for Development
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with chrome extension.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for chrome extension in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready chrome extension setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened chrome extension implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: javascript, manifest-v3
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,278 @@
|
||||
---
|
||||
name: ci-cd-builder
|
||||
display_name: CI/CD Builder
|
||||
description: Create CI/CD pipelines — GitHub Actions, GitLab CI, Jenkins, and CircleCI with test, build, and deploy stages. Use when setting up automation, continuous integration, deployment workflows, or pipeline configuration.
|
||||
---
|
||||
|
||||
# CI/CD Builder
|
||||
|
||||
## Overview
|
||||
|
||||
Create CI/CD pipelines for the CineK projects (`kr-phim` and `telegram-bot`) with test, build, and deploy stages. Supports GitHub Actions as the primary CI/CD platform.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **CI/CD Builder** when you need to:
|
||||
|
||||
- Set up GitHub Actions workflows for CI/CD
|
||||
- Automate testing, building, and deployment pipelines
|
||||
- Configure staging vs production deployment environments
|
||||
- Add cache optimization, parallel jobs, or artifact management
|
||||
- Set up auto-deploy on push to main/master branches
|
||||
|
||||
## Project Context
|
||||
|
||||
### kr-phim (Nuxt 4 + Vue 3 + Tailwind v4)
|
||||
- **Build command:** `npm run build`
|
||||
- **Dev command:** `npm run dev`
|
||||
- **Test command:** `npm run test` (if configured)
|
||||
- **Lint command:** `npm run lint`
|
||||
- **Type check:** `npm run typecheck` (if configured)
|
||||
- **Package manager:** npm
|
||||
- **Runtime:** Node.js 20+
|
||||
- **Docker:** Uses docker-compose for development and production
|
||||
|
||||
### telegram-bot
|
||||
- Check `package.json` for exact scripts
|
||||
- May use Python/Node depending on implementation
|
||||
|
||||
## GitHub Actions Workflow Structure
|
||||
|
||||
### Directory Layout
|
||||
|
||||
```
|
||||
.github/
|
||||
├── workflows/
|
||||
│ ├── ci.yml # Continuous Integration (every PR/push)
|
||||
│ ├── deploy-staging.yml # Staging deployment (main branch)
|
||||
│ └── deploy-production.yml # Production deployment (tag/release)
|
||||
├── ISSUE_TEMPLATE/
|
||||
└── PULL_REQUEST_TEMPLATE.md
|
||||
```
|
||||
|
||||
### CI Workflow (ci.yml)
|
||||
|
||||
```yaml
|
||||
name: CI
|
||||
|
||||
on:
|
||||
pull_request:
|
||||
branches: [main, develop]
|
||||
push:
|
||||
branches: [main, develop]
|
||||
|
||||
jobs:
|
||||
lint-and-test:
|
||||
runs-on: ubuntu-latest
|
||||
|
||||
steps:
|
||||
- name: Checkout code
|
||||
uses: actions/checkout@v4
|
||||
|
||||
- name: Setup Node.js
|
||||
uses: actions/setup-node@v4
|
||||
with:
|
||||
node-version: '20'
|
||||
cache: 'npm'
|
||||
cache-dependency-path: kr-phim/package-lock.json
|
||||
|
||||
- name: Install dependencies
|
||||
working-directory: ./kr-phim
|
||||
run: npm ci
|
||||
|
||||
- name: Lint
|
||||
working-directory: ./kr-phim
|
||||
run: npm run lint
|
||||
|
||||
- name: Type check
|
||||
working-directory: ./kr-phim
|
||||
run: npm run typecheck || echo "No typecheck script"
|
||||
|
||||
- name: Build
|
||||
working-directory: ./kr-phim
|
||||
run: npm run build
|
||||
```
|
||||
|
||||
### Deploy Staging (deploy-staging.yml)
|
||||
|
||||
```yaml
|
||||
name: Deploy Staging
|
||||
|
||||
on:
|
||||
push:
|
||||
branches: [main]
|
||||
|
||||
jobs:
|
||||
deploy-staging:
|
||||
runs-on: ubuntu-latest
|
||||
|
||||
steps:
|
||||
- name: Checkout code
|
||||
uses: actions/checkout@v4
|
||||
|
||||
- name: Setup Node.js
|
||||
uses: actions/setup-node@v4
|
||||
with:
|
||||
node-version: '20'
|
||||
cache: 'npm'
|
||||
|
||||
- name: Install dependencies
|
||||
working-directory: ./kr-phim
|
||||
run: npm ci
|
||||
|
||||
- name: Build
|
||||
working-directory: ./kr-phim
|
||||
run: npm run build
|
||||
env:
|
||||
NODE_ENV: production
|
||||
${{ secrets.STAGING_ENV_VARS }}
|
||||
|
||||
- name: Deploy to staging
|
||||
uses: appleboy/ssh-action@v1
|
||||
with:
|
||||
host: ${{ secrets.STAGING_SERVER_HOST }}
|
||||
username: ${{ secrets.STAGING_SERVER_USER }}
|
||||
key: ${{ secrets.STAGING_SERVER_SSH_KEY }}
|
||||
script: |
|
||||
cd /opt/cinek/staging
|
||||
docker compose pull
|
||||
docker compose up -d kr-phim
|
||||
```
|
||||
|
||||
### Deploy Production (deploy-production.yml)
|
||||
|
||||
```yaml
|
||||
name: Deploy Production
|
||||
|
||||
on:
|
||||
release:
|
||||
types: [published]
|
||||
push:
|
||||
tags:
|
||||
- 'v*'
|
||||
|
||||
jobs:
|
||||
deploy-production:
|
||||
runs-on: ubuntu-latest
|
||||
|
||||
steps:
|
||||
- name: Checkout code
|
||||
uses: actions/checkout@v4
|
||||
|
||||
- name: Setup Node.js
|
||||
uses: actions/setup-node@v4
|
||||
with:
|
||||
node-version: '20'
|
||||
cache: 'npm'
|
||||
|
||||
- name: Install dependencies
|
||||
working-directory: ./kr-phim
|
||||
run: npm ci
|
||||
|
||||
- name: Build
|
||||
working-directory: ./kr-phim
|
||||
run: npm run build
|
||||
env:
|
||||
NODE_ENV: production
|
||||
${{ secrets.PRODUCTION_ENV_VARS }}
|
||||
|
||||
- name: Deploy to production
|
||||
uses: appleboy/ssh-action@v1
|
||||
with:
|
||||
host: ${{ secrets.PRODUCTION_SERVER_HOST }}
|
||||
username: ${{ secrets.PRODUCTION_SERVER_USER }}
|
||||
key: ${{ secrets.PRODUCTION_SERVER_SSH_KEY }}
|
||||
script: |
|
||||
cd /opt/cinek/production
|
||||
docker compose pull
|
||||
docker compose up -d kr-phim
|
||||
```
|
||||
|
||||
## Docker-Based Deployment (Recommended)
|
||||
|
||||
Since the project uses Docker Compose, the preferred deployment strategy:
|
||||
|
||||
```yaml
|
||||
name: Deploy via Docker
|
||||
|
||||
on:
|
||||
workflow_dispatch:
|
||||
inputs:
|
||||
environment:
|
||||
description: 'Deploy to'
|
||||
required: true
|
||||
default: 'staging'
|
||||
type: choice
|
||||
options:
|
||||
- staging
|
||||
- production
|
||||
|
||||
jobs:
|
||||
deploy:
|
||||
runs-on: ubuntu-latest
|
||||
|
||||
steps:
|
||||
- name: Checkout code
|
||||
uses: actions/checkout@v4
|
||||
|
||||
- name: Build Docker image
|
||||
run: |
|
||||
docker build -t cinemk:$(echo ${{ github.sha }} | cut -c1-7) ./kr-phim
|
||||
|
||||
- name: Push to registry
|
||||
uses: docker/login-action@v3
|
||||
with:
|
||||
username: ${{ secrets.DOCKER_USERNAME }}
|
||||
password: ${{ secrets.DOCKER_PASSWORD }}
|
||||
|
||||
- name: Push image
|
||||
run: |
|
||||
docker tag cinemk:$(echo ${{ github.sha }} | cut -c1-7) ${{ secrets.DOCKER_REPO }}:latest
|
||||
docker tag cinemk:$(echo ${{ github.sha }} | cut -c1-7) ${{ secrets.DOCKER_REPO }}:${{ github.sha }}
|
||||
docker push ${{ secrets.DOCKER_REPO }}:latest
|
||||
docker push ${{ secrets.DOCKER_REPO }}:${{ github.sha }}
|
||||
```
|
||||
|
||||
## Best Practices
|
||||
|
||||
1. **Cache node_modules** — Use `actions/cache` or `actions/setup-node` with `cache: 'npm'`
|
||||
2. **Separate CI/CD** — Keep CI (tests/lint) separate from deployment workflows
|
||||
3. **Environment-specific secrets** — Use different secrets for staging vs production
|
||||
4. **Pipeline caching** — Cache Docker layers and build artifacts between runs
|
||||
5. **Parallel jobs** — Run lint, test, and build in parallel when possible
|
||||
6. **Rollback strategy** — Always keep previous image tags for quick rollback
|
||||
7. **Health checks** — Add post-deploy health check steps
|
||||
8. **Notifications** — Add Slack/Discord webhook notifications for deploy status
|
||||
|
||||
## Environment Variables
|
||||
|
||||
Common env vars needed across environments:
|
||||
|
||||
| Variable | Description |
|
||||
|----------|-------------|
|
||||
| `NODE_ENV` | `production` or `development` |
|
||||
| `DATABASE_URL` | Database connection string |
|
||||
| `NUXT_SECRET` | App secret key |
|
||||
| `REDIS_URL` | Redis connection (if used) |
|
||||
| `API_URL` | External API endpoints |
|
||||
|
||||
Store sensitive values in GitHub Secrets — never hardcode them.
|
||||
|
||||
## Common Pitfalls
|
||||
|
||||
- **Missing `.dockerignore`** — Ensure `node_modules`, `.git`, and logs are excluded
|
||||
- **Large images** — Use multi-stage builds to minimize image size
|
||||
- **Slow installs** — Always use `npm ci` instead of `npm install` in CI
|
||||
- **Port conflicts** — Verify ports don't clash in docker-compose
|
||||
- **Secrets leakage** — Never log or expose secrets in workflow outputs
|
||||
|
||||
## Integration Checklist
|
||||
|
||||
After creating a CI/CD pipeline:
|
||||
|
||||
- [ ] Add GitHub repository secrets for all required credentials
|
||||
- [ ] Test the workflow on a feature branch
|
||||
- [ ] Verify staging deployment works end-to-end
|
||||
- [ ] Confirm production deploy only triggers on release/tag
|
||||
- [ ] Add branch protection rules (require CI to pass)
|
||||
- [ ] Document the pipeline in team README
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: citation-manager
|
||||
display_name: Citation Manager
|
||||
description: Format and manage citations — APA, MLA, Chicago, IEEE, and Vancouver styles with BibTeX export.
|
||||
category: Research & Analysis
|
||||
platforms: [claude.ai, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [citation-manager]
|
||||
---
|
||||
|
||||
# Citation Manager
|
||||
|
||||
## Overview
|
||||
|
||||
Format and manage citations — APA, MLA, Chicago, IEEE, and Vancouver styles with BibTeX export.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Citation Manager** when you need to:
|
||||
|
||||
- Work with citation manager tasks in your project or workflow
|
||||
- Automate citation manager operations at scale
|
||||
- Generate production-quality citation manager output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your citation manager request
|
||||
2. Apply best practices and conventions for Research & Analysis
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with citation manager.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for citation manager in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready citation manager setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened citation manager implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: claude-api
|
||||
display_name: Claude API
|
||||
description: Build apps with the Anthropic Claude API — chat completions, tool use, streaming, vision, and multi-turn conversations.
|
||||
category: Development
|
||||
platforms: [claude.ai, claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [claude-api]
|
||||
---
|
||||
|
||||
# Claude API
|
||||
|
||||
## Overview
|
||||
|
||||
Build apps with the Anthropic Claude API — chat completions, tool use, streaming, vision, and multi-turn conversations.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Claude API** when you need to:
|
||||
|
||||
- Work with claude api tasks in your project or workflow
|
||||
- Automate claude api operations at scale
|
||||
- Generate production-quality claude api output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your claude api request
|
||||
2. Apply best practices and conventions for Development
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with claude api.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for claude api in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready claude api setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened claude api implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: python, typescript, anthropic-sdk
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: cli-builder
|
||||
display_name: CLI Builder
|
||||
description: Build polished command-line tools — argument parsing, help text, interactive prompts, progress bars, and shell completions.
|
||||
category: Development
|
||||
platforms: [claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [cli-builder]
|
||||
---
|
||||
|
||||
# CLI Builder
|
||||
|
||||
## Overview
|
||||
|
||||
Build polished command-line tools — argument parsing, help text, interactive prompts, progress bars, and shell completions.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **CLI Builder** when you need to:
|
||||
|
||||
- Work with cli builder tasks in your project or workflow
|
||||
- Automate cli builder operations at scale
|
||||
- Generate production-quality cli builder output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your cli builder request
|
||||
2. Apply best practices and conventions for Development
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with cli builder.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for cli builder in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready cli builder setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened cli builder implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: python, click, cobra, oclif
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: code-reviewer
|
||||
display_name: Code Reviewer
|
||||
description: Perform thorough code reviews — bugs, security issues, performance bottlenecks, style violations, and architectural concerns.
|
||||
category: Development
|
||||
platforms: [claude.ai, claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [code-reviewer]
|
||||
---
|
||||
|
||||
# Code Reviewer
|
||||
|
||||
## Overview
|
||||
|
||||
Perform thorough code reviews — bugs, security issues, performance bottlenecks, style violations, and architectural concerns.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Code Reviewer** when you need to:
|
||||
|
||||
- Work with code reviewer tasks in your project or workflow
|
||||
- Automate code reviewer operations at scale
|
||||
- Generate production-quality code reviewer output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your code reviewer request
|
||||
2. Apply best practices and conventions for Development
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with code reviewer.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for code reviewer in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready code reviewer setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened code reviewer implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: cohort-analyzer
|
||||
display_name: Cohort Analyzer
|
||||
description: Build cohort analyses — retention curves, LTV by cohort, churn funnels, and behavioral segmentation.
|
||||
category: Data & Analytics
|
||||
platforms: [claude.ai, claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [cohort-analyzer]
|
||||
---
|
||||
|
||||
# Cohort Analyzer
|
||||
|
||||
## Overview
|
||||
|
||||
Build cohort analyses — retention curves, LTV by cohort, churn funnels, and behavioral segmentation.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Cohort Analyzer** when you need to:
|
||||
|
||||
- Work with cohort analyzer tasks in your project or workflow
|
||||
- Automate cohort analyzer operations at scale
|
||||
- Generate production-quality cohort analyzer output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your cohort analyzer request
|
||||
2. Apply best practices and conventions for Data & Analytics
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with cohort analyzer.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for cohort analyzer in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready cohort analyzer setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened cohort analyzer implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: python, pandas
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: cohort-coach
|
||||
display_name: Cohort Coach
|
||||
description: Facilitate cohort-based learning — weekly prompts, peer challenges, group projects, and community engagement.
|
||||
category: Education & Learning
|
||||
platforms: [claude.ai, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [cohort-coach]
|
||||
---
|
||||
|
||||
# Cohort Coach
|
||||
|
||||
## Overview
|
||||
|
||||
Facilitate cohort-based learning — weekly prompts, peer challenges, group projects, and community engagement.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Cohort Coach** when you need to:
|
||||
|
||||
- Work with cohort coach tasks in your project or workflow
|
||||
- Automate cohort coach operations at scale
|
||||
- Generate production-quality cohort coach output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your cohort coach request
|
||||
2. Apply best practices and conventions for Education & Learning
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with cohort coach.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for cohort coach in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready cohort coach setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened cohort coach implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: color-palette
|
||||
display_name: Color Palette
|
||||
description: Build harmonious color palettes — complementary, analogous, triadic schemes with WCAG contrast checks and CSS variable exports.
|
||||
category: Creative & Design
|
||||
platforms: [claude.ai, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [color-palette]
|
||||
---
|
||||
|
||||
# Color Palette
|
||||
|
||||
## Overview
|
||||
|
||||
Build harmonious color palettes — complementary, analogous, triadic schemes with WCAG contrast checks and CSS variable exports.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Color Palette** when you need to:
|
||||
|
||||
- Work with color palette tasks in your project or workflow
|
||||
- Automate color palette operations at scale
|
||||
- Generate production-quality color palette output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your color palette request
|
||||
2. Apply best practices and conventions for Creative & Design
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with color palette.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for color palette in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready color palette setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened color palette implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: competitive-analyst
|
||||
display_name: Competitive Analyst
|
||||
description: Analyze competitors — feature matrices, pricing comparisons, positioning maps, and SWOT analysis.
|
||||
category: Research & Analysis
|
||||
platforms: [claude.ai, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [competitive-analyst]
|
||||
---
|
||||
|
||||
# Competitive Analyst
|
||||
|
||||
## Overview
|
||||
|
||||
Analyze competitors — feature matrices, pricing comparisons, positioning maps, and SWOT analysis.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Competitive Analyst** when you need to:
|
||||
|
||||
- Work with competitive analyst tasks in your project or workflow
|
||||
- Automate competitive analyst operations at scale
|
||||
- Generate production-quality competitive analyst output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your competitive analyst request
|
||||
2. Apply best practices and conventions for Research & Analysis
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with competitive analyst.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for competitive analyst in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready competitive analyst setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened competitive analyst implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: compliance-checker
|
||||
display_name: Compliance Checker
|
||||
description: Check compliance with standards — ISO 27001, SOC 2, PCI-DSS, HIPAA, and NIST frameworks.
|
||||
category: Security
|
||||
platforms: [claude.ai, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [compliance-checker]
|
||||
---
|
||||
|
||||
# Compliance Checker
|
||||
|
||||
## Overview
|
||||
|
||||
Check compliance with standards — ISO 27001, SOC 2, PCI-DSS, HIPAA, and NIST frameworks.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Compliance Checker** when you need to:
|
||||
|
||||
- Work with compliance checker tasks in your project or workflow
|
||||
- Automate compliance checker operations at scale
|
||||
- Generate production-quality compliance checker output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your compliance checker request
|
||||
2. Apply best practices and conventions for Security
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with compliance checker.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for compliance checker in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready compliance checker setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened compliance checker implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: concept-mapper
|
||||
display_name: Concept Mapper
|
||||
description: Build concept maps and knowledge graphs — nodes, relationships, hierarchies, and Mermaid/Graphviz exports.
|
||||
category: Education & Learning
|
||||
platforms: [claude.ai, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [concept-mapper]
|
||||
---
|
||||
|
||||
# Concept Mapper
|
||||
|
||||
## Overview
|
||||
|
||||
Build concept maps and knowledge graphs — nodes, relationships, hierarchies, and Mermaid/Graphviz exports.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Concept Mapper** when you need to:
|
||||
|
||||
- Work with concept mapper tasks in your project or workflow
|
||||
- Automate concept mapper operations at scale
|
||||
- Generate production-quality concept mapper output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your concept mapper request
|
||||
2. Apply best practices and conventions for Education & Learning
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with concept mapper.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for concept mapper in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready concept mapper setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened concept mapper implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: mermaid
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: content-calendar
|
||||
display_name: Content Calendar
|
||||
description: Plan content calendars — themes, publishing schedules, platform mix, repurposing strategies, and campaign alignment.
|
||||
category: Media & Content
|
||||
platforms: [claude.ai, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [content-calendar]
|
||||
---
|
||||
|
||||
# Content Calendar
|
||||
|
||||
## Overview
|
||||
|
||||
Plan content calendars — themes, publishing schedules, platform mix, repurposing strategies, and campaign alignment.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Content Calendar** when you need to:
|
||||
|
||||
- Work with content calendar tasks in your project or workflow
|
||||
- Automate content calendar operations at scale
|
||||
- Generate production-quality content calendar output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your content calendar request
|
||||
2. Apply best practices and conventions for Media & Content
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with content calendar.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for content calendar in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready content calendar setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened content calendar implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: contract-generator
|
||||
display_name: Contract Generator
|
||||
description: Draft professional legal contracts — NDAs, service agreements, employment contracts, and SaaS terms with customizable clauses.
|
||||
category: Documents & Files
|
||||
platforms: [claude.ai, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [contract-generator]
|
||||
---
|
||||
|
||||
# Contract Generator
|
||||
|
||||
## Overview
|
||||
|
||||
Draft professional legal contracts — NDAs, service agreements, employment contracts, and SaaS terms with customizable clauses.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Contract Generator** when you need to:
|
||||
|
||||
- Work with contract generator tasks in your project or workflow
|
||||
- Automate contract generator operations at scale
|
||||
- Generate production-quality contract generator output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your contract generator request
|
||||
2. Apply best practices and conventions for Documents & Files
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with contract generator.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for contract generator in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready contract generator setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened contract generator implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: copywriter
|
||||
display_name: Copywriter
|
||||
description: Write high-converting copy — landing pages, ads, product descriptions, taglines, and brand narratives.
|
||||
category: Writing & Communication
|
||||
platforms: [claude.ai, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [copywriter]
|
||||
---
|
||||
|
||||
# Copywriter
|
||||
|
||||
## Overview
|
||||
|
||||
Write high-converting copy — landing pages, ads, product descriptions, taglines, and brand narratives.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Copywriter** when you need to:
|
||||
|
||||
- Work with copywriter tasks in your project or workflow
|
||||
- Automate copywriter operations at scale
|
||||
- Generate production-quality copywriter output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your copywriter request
|
||||
2. Apply best practices and conventions for Writing & Communication
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with copywriter.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for copywriter in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready copywriter setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened copywriter implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: course-creator
|
||||
display_name: Course Creator
|
||||
description: Design full online courses — learning objectives, module outlines, lesson scripts, quizzes, and assessment rubrics.
|
||||
category: Education & Learning
|
||||
platforms: [claude.ai, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [course-creator]
|
||||
---
|
||||
|
||||
# Course Creator
|
||||
|
||||
## Overview
|
||||
|
||||
Design full online courses — learning objectives, module outlines, lesson scripts, quizzes, and assessment rubrics.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Course Creator** when you need to:
|
||||
|
||||
- Work with course creator tasks in your project or workflow
|
||||
- Automate course creator operations at scale
|
||||
- Generate production-quality course creator output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your course creator request
|
||||
2. Apply best practices and conventions for Education & Learning
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with course creator.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for course creator in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready course creator setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened course creator implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: css-art
|
||||
display_name: CSS Art
|
||||
description: Generate pure CSS art and illustrations — portraits, landscapes, UI elements, and interactive CSS-only animations.
|
||||
category: Creative & Design
|
||||
platforms: [claude.ai, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [css-art]
|
||||
---
|
||||
|
||||
# CSS Art
|
||||
|
||||
## Overview
|
||||
|
||||
Generate pure CSS art and illustrations — portraits, landscapes, UI elements, and interactive CSS-only animations.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **CSS Art** when you need to:
|
||||
|
||||
- Work with css art tasks in your project or workflow
|
||||
- Automate css art operations at scale
|
||||
- Generate production-quality css art output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your css art request
|
||||
2. Apply best practices and conventions for Creative & Design
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with css art.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for css art in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready css art setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened css art implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: css
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: csv-analyzer
|
||||
display_name: CSV Analyzer
|
||||
description: Analyze, clean, transform, and summarize CSV files — detect anomalies, compute statistics, and produce actionable insights.
|
||||
category: Documents & Files
|
||||
platforms: [claude.ai, claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [csv-analyzer]
|
||||
---
|
||||
|
||||
# CSV Analyzer
|
||||
|
||||
## Overview
|
||||
|
||||
Analyze, clean, transform, and summarize CSV files — detect anomalies, compute statistics, and produce actionable insights.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **CSV Analyzer** when you need to:
|
||||
|
||||
- Work with csv analyzer tasks in your project or workflow
|
||||
- Automate csv analyzer operations at scale
|
||||
- Generate production-quality csv analyzer output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your csv analyzer request
|
||||
2. Apply best practices and conventions for Documents & Files
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with csv analyzer.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for csv analyzer in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready csv analyzer setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened csv analyzer implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: python, pandas
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: curriculum-designer
|
||||
display_name: Curriculum Designer
|
||||
description: Design curricula — scope and sequence, standards alignment, unit plans, and pacing guides.
|
||||
category: Education & Learning
|
||||
platforms: [claude.ai, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [curriculum-designer]
|
||||
---
|
||||
|
||||
# Curriculum Designer
|
||||
|
||||
## Overview
|
||||
|
||||
Design curricula — scope and sequence, standards alignment, unit plans, and pacing guides.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Curriculum Designer** when you need to:
|
||||
|
||||
- Work with curriculum designer tasks in your project or workflow
|
||||
- Automate curriculum designer operations at scale
|
||||
- Generate production-quality curriculum designer output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your curriculum designer request
|
||||
2. Apply best practices and conventions for Education & Learning
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with curriculum designer.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for curriculum designer in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready curriculum designer setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened curriculum designer implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: customer-success
|
||||
display_name: Customer Success
|
||||
description: Build customer success playbooks — onboarding flows, health scoring, QBR templates, and churn intervention plans.
|
||||
category: Business & Productivity
|
||||
platforms: [claude.ai, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [customer-success]
|
||||
---
|
||||
|
||||
# Customer Success
|
||||
|
||||
## Overview
|
||||
|
||||
Build customer success playbooks — onboarding flows, health scoring, QBR templates, and churn intervention plans.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Customer Success** when you need to:
|
||||
|
||||
- Work with customer success tasks in your project or workflow
|
||||
- Automate customer success operations at scale
|
||||
- Generate production-quality customer success output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your customer success request
|
||||
2. Apply best practices and conventions for Business & Productivity
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with customer success.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for customer success in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready customer success setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened customer success implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: dark-mode-converter
|
||||
display_name: Dark Mode Converter
|
||||
description: Convert any UI to a polished dark mode — semantic color tokens, system preference detection, and smooth transitions.
|
||||
category: Creative & Design
|
||||
platforms: [claude.ai, claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [dark-mode-converter]
|
||||
---
|
||||
|
||||
# Dark Mode Converter
|
||||
|
||||
## Overview
|
||||
|
||||
Convert any UI to a polished dark mode — semantic color tokens, system preference detection, and smooth transitions.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Dark Mode Converter** when you need to:
|
||||
|
||||
- Work with dark mode converter tasks in your project or workflow
|
||||
- Automate dark mode converter operations at scale
|
||||
- Generate production-quality dark mode converter output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your dark mode converter request
|
||||
2. Apply best practices and conventions for Creative & Design
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with dark mode converter.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for dark mode converter in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready dark mode converter setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened dark mode converter implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: css, tailwind
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: dashboard-builder
|
||||
display_name: Dashboard Builder
|
||||
description: Build interactive data dashboards — Streamlit, Dash, Grafana, and Power BI reports with live data sources.
|
||||
category: Data & Analytics
|
||||
platforms: [claude.ai, claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [dashboard-builder]
|
||||
---
|
||||
|
||||
# Dashboard Builder
|
||||
|
||||
## Overview
|
||||
|
||||
Build interactive data dashboards — Streamlit, Dash, Grafana, and Power BI reports with live data sources.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Dashboard Builder** when you need to:
|
||||
|
||||
- Work with dashboard builder tasks in your project or workflow
|
||||
- Automate dashboard builder operations at scale
|
||||
- Generate production-quality dashboard builder output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your dashboard builder request
|
||||
2. Apply best practices and conventions for Data & Analytics
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with dashboard builder.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for dashboard builder in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready dashboard builder setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened dashboard builder implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: python, streamlit, plotly
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: data-cleaner
|
||||
display_name: Data Cleaner
|
||||
description: Clean messy datasets — handle missing values, fix dtypes, remove duplicates, normalize formats, and flag anomalies.
|
||||
category: Data & Analytics
|
||||
platforms: [claude.ai, claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [data-cleaner]
|
||||
---
|
||||
|
||||
# Data Cleaner
|
||||
|
||||
## Overview
|
||||
|
||||
Clean messy datasets — handle missing values, fix dtypes, remove duplicates, normalize formats, and flag anomalies.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Data Cleaner** when you need to:
|
||||
|
||||
- Work with data cleaner tasks in your project or workflow
|
||||
- Automate data cleaner operations at scale
|
||||
- Generate production-quality data cleaner output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your data cleaner request
|
||||
2. Apply best practices and conventions for Data & Analytics
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with data cleaner.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for data cleaner in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready data cleaner setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened data cleaner implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: python, pandas
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: data-storyteller
|
||||
display_name: Data Storyteller
|
||||
description: Turn data into compelling narratives — executive summaries, annotated charts, and data-driven presentations.
|
||||
category: Data & Analytics
|
||||
platforms: [claude.ai, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [data-storyteller]
|
||||
---
|
||||
|
||||
# Data Storyteller
|
||||
|
||||
## Overview
|
||||
|
||||
Turn data into compelling narratives — executive summaries, annotated charts, and data-driven presentations.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Data Storyteller** when you need to:
|
||||
|
||||
- Work with data storyteller tasks in your project or workflow
|
||||
- Automate data storyteller operations at scale
|
||||
- Generate production-quality data storyteller output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your data storyteller request
|
||||
2. Apply best practices and conventions for Data & Analytics
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with data storyteller.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for data storyteller in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready data storyteller setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened data storyteller implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: data-transformer
|
||||
display_name: Data Transformer
|
||||
description: Transform and reshape data — pivot, melt, aggregate, join, and apply complex business rules to datasets.
|
||||
category: Data & Analytics
|
||||
platforms: [claude.ai, claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [data-transformer]
|
||||
---
|
||||
|
||||
# Data Transformer
|
||||
|
||||
## Overview
|
||||
|
||||
Transform and reshape data — pivot, melt, aggregate, join, and apply complex business rules to datasets.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Data Transformer** when you need to:
|
||||
|
||||
- Work with data transformer tasks in your project or workflow
|
||||
- Automate data transformer operations at scale
|
||||
- Generate production-quality data transformer output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your data transformer request
|
||||
2. Apply best practices and conventions for Data & Analytics
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with data transformer.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for data transformer in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready data transformer setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened data transformer implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: python, pandas, spark
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: data-viz
|
||||
display_name: Data Visualization
|
||||
description: Transform raw data into compelling interactive visualizations — dashboards, maps, network graphs, and Sankey diagrams.
|
||||
category: Creative & Design
|
||||
platforms: [claude.ai, claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [data-viz]
|
||||
---
|
||||
|
||||
# Data Visualization
|
||||
|
||||
## Overview
|
||||
|
||||
Transform raw data into compelling interactive visualizations — dashboards, maps, network graphs, and Sankey diagrams.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Data Visualization** when you need to:
|
||||
|
||||
- Work with data visualization tasks in your project or workflow
|
||||
- Automate data visualization operations at scale
|
||||
- Generate production-quality data visualization output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your data visualization request
|
||||
2. Apply best practices and conventions for Creative & Design
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with data visualization.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for data visualization in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready data visualization setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened data visualization implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: d3, plotly, vega
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: db-schema-designer
|
||||
display_name: DB Schema Designer
|
||||
description: Design normalized relational database schemas — ERDs, indexes, constraints, migrations, and performance optimization.
|
||||
category: Development
|
||||
platforms: [claude.ai, claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [db-schema-designer]
|
||||
---
|
||||
|
||||
# DB Schema Designer
|
||||
|
||||
## Overview
|
||||
|
||||
Design normalized relational database schemas — ERDs, indexes, constraints, migrations, and performance optimization.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **DB Schema Designer** when you need to:
|
||||
|
||||
- Work with db schema designer tasks in your project or workflow
|
||||
- Automate db schema designer operations at scale
|
||||
- Generate production-quality db schema designer output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your db schema designer request
|
||||
2. Apply best practices and conventions for Development
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with db schema designer.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for db schema designer in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready db schema designer setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened db schema designer implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: postgresql, mysql, sqlite
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: debug-helper
|
||||
display_name: Debug Helper
|
||||
description: Diagnose and fix bugs systematically — error analysis, stack trace interpretation, root cause identification, and fix suggestions.
|
||||
category: Development
|
||||
platforms: [claude.ai, claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [debug-helper]
|
||||
---
|
||||
|
||||
# Debug Helper
|
||||
|
||||
## Overview
|
||||
|
||||
Diagnose and fix bugs systematically — error analysis, stack trace interpretation, root cause identification, and fix suggestions.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Debug Helper** when you need to:
|
||||
|
||||
- Work with debug helper tasks in your project or workflow
|
||||
- Automate debug helper operations at scale
|
||||
- Generate production-quality debug helper output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your debug helper request
|
||||
2. Apply best practices and conventions for Development
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with debug helper.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for debug helper in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready debug helper setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened debug helper implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: dependency-auditor
|
||||
display_name: Dependency Auditor
|
||||
description: Audit project dependencies — outdated packages, known CVEs, license conflicts, and upgrade recommendations.
|
||||
category: Security
|
||||
platforms: [claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [dependency-auditor]
|
||||
---
|
||||
|
||||
# Dependency Auditor
|
||||
|
||||
## Overview
|
||||
|
||||
Audit project dependencies — outdated packages, known CVEs, license conflicts, and upgrade recommendations.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Dependency Auditor** when you need to:
|
||||
|
||||
- Work with dependency auditor tasks in your project or workflow
|
||||
- Automate dependency auditor operations at scale
|
||||
- Generate production-quality dependency auditor output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your dependency auditor request
|
||||
2. Apply best practices and conventions for Security
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with dependency auditor.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for dependency auditor in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready dependency auditor setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened dependency auditor implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: design-system
|
||||
display_name: Design System
|
||||
description: Build complete design systems — component tokens, Storybook stories, Figma variables, and living style guides.
|
||||
category: Creative & Design
|
||||
platforms: [claude.ai, claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [design-system]
|
||||
---
|
||||
|
||||
# Design System
|
||||
|
||||
## Overview
|
||||
|
||||
Build complete design systems — component tokens, Storybook stories, Figma variables, and living style guides.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Design System** when you need to:
|
||||
|
||||
- Work with design system tasks in your project or workflow
|
||||
- Automate design system operations at scale
|
||||
- Generate production-quality design system output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your design system request
|
||||
2. Apply best practices and conventions for Creative & Design
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with design system.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for design system in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready design system setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened design system implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: react, storybook
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: discord-bot
|
||||
display_name: Discord Bot
|
||||
description: Create Discord bots — slash commands, embeds, voice, roles, threads, and Discord.js/Pycord implementations.
|
||||
category: Integrations & Automation
|
||||
platforms: [claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [discord-bot]
|
||||
---
|
||||
|
||||
# Discord Bot
|
||||
|
||||
## Overview
|
||||
|
||||
Create Discord bots — slash commands, embeds, voice, roles, threads, and Discord.js/Pycord implementations.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Discord Bot** when you need to:
|
||||
|
||||
- Work with discord bot tasks in your project or workflow
|
||||
- Automate discord bot operations at scale
|
||||
- Generate production-quality discord bot output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your discord bot request
|
||||
2. Apply best practices and conventions for Integrations & Automation
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with discord bot.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for discord bot in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready discord bot setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened discord bot implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: typescript, discord.js
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: doc-coauthoring
|
||||
display_name: Document Co-Authoring
|
||||
description: Collaborate on long-form documents — track changes, merge edits, maintain consistent voice, and manage review cycles.
|
||||
category: Writing & Communication
|
||||
platforms: [claude.ai, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [doc-coauthoring]
|
||||
---
|
||||
|
||||
# Document Co-Authoring
|
||||
|
||||
## Overview
|
||||
|
||||
Collaborate on long-form documents — track changes, merge edits, maintain consistent voice, and manage review cycles.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Document Co-Authoring** when you need to:
|
||||
|
||||
- Work with document co-authoring tasks in your project or workflow
|
||||
- Automate document co-authoring operations at scale
|
||||
- Generate production-quality document co-authoring output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your document co-authoring request
|
||||
2. Apply best practices and conventions for Writing & Communication
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with document co-authoring.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for document co-authoring in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready document co-authoring setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened document co-authoring implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: docker-composer
|
||||
display_name: Docker Composer
|
||||
description: Write Dockerfiles and docker-compose files — multi-stage builds, health checks, volumes, networks, and production configurations.
|
||||
category: Development
|
||||
platforms: [claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [docker-composer]
|
||||
---
|
||||
|
||||
# Docker Composer
|
||||
|
||||
## Overview
|
||||
|
||||
Write Dockerfiles and docker-compose files — multi-stage builds, health checks, volumes, networks, and production configurations.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Docker Composer** when you need to:
|
||||
|
||||
- Work with docker composer tasks in your project or workflow
|
||||
- Automate docker composer operations at scale
|
||||
- Generate production-quality docker composer output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your docker composer request
|
||||
2. Apply best practices and conventions for Development
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with docker composer.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for docker composer in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready docker composer setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened docker composer implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: docker
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: dockerfile-builder
|
||||
display_name: Dockerfile Builder
|
||||
description: Write optimized Dockerfiles — multi-stage builds, layer caching, security hardening, and minimal image sizes.
|
||||
category: DevOps & Infrastructure
|
||||
platforms: [claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [dockerfile-builder]
|
||||
---
|
||||
|
||||
# Dockerfile Builder
|
||||
|
||||
## Overview
|
||||
|
||||
Write optimized Dockerfiles — multi-stage builds, layer caching, security hardening, and minimal image sizes.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Dockerfile Builder** when you need to:
|
||||
|
||||
- Work with dockerfile builder tasks in your project or workflow
|
||||
- Automate dockerfile builder operations at scale
|
||||
- Generate production-quality dockerfile builder output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your dockerfile builder request
|
||||
2. Apply best practices and conventions for DevOps & Infrastructure
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with dockerfile builder.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for dockerfile builder in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready dockerfile builder setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened dockerfile builder implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: docker
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: docs-generator
|
||||
display_name: Docs Generator
|
||||
description: Auto-generate documentation from code — docstrings, API references, README files, and changelog entries.
|
||||
category: Education & Learning
|
||||
platforms: [claude.ai, claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [docs-generator]
|
||||
---
|
||||
|
||||
# Docs Generator
|
||||
|
||||
## Overview
|
||||
|
||||
Auto-generate documentation from code — docstrings, API references, README files, and changelog entries.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Docs Generator** when you need to:
|
||||
|
||||
- Work with docs generator tasks in your project or workflow
|
||||
- Automate docs generator operations at scale
|
||||
- Generate production-quality docs generator output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your docs generator request
|
||||
2. Apply best practices and conventions for Education & Learning
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with docs generator.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for docs generator in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready docs generator setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened docs generator implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: docx
|
||||
display_name: Word Document
|
||||
description: Create, read, edit, and manipulate Word .docx files with full formatting — tables of contents, headings, page numbers, letterheads, tracked changes.
|
||||
category: Documents & Files
|
||||
platforms: [claude.ai, claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [docx]
|
||||
---
|
||||
|
||||
# Word Document
|
||||
|
||||
## Overview
|
||||
|
||||
Create, read, edit, and manipulate Word .docx files with full formatting — tables of contents, headings, page numbers, letterheads, tracked changes.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Word Document** when you need to:
|
||||
|
||||
- Work with word document tasks in your project or workflow
|
||||
- Automate word document operations at scale
|
||||
- Generate production-quality word document output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your word document request
|
||||
2. Apply best practices and conventions for Documents & Files
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with word document.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for word document in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready word document setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened word document implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: python, python-docx
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: email-composer
|
||||
display_name: Email Composer
|
||||
description: Compose professional emails for any context — outreach, follow-ups, apologies, negotiations, and announcements.
|
||||
category: Writing & Communication
|
||||
platforms: [claude.ai, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [email-composer]
|
||||
---
|
||||
|
||||
# Email Composer
|
||||
|
||||
## Overview
|
||||
|
||||
Compose professional emails for any context — outreach, follow-ups, apologies, negotiations, and announcements.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Email Composer** when you need to:
|
||||
|
||||
- Work with email composer tasks in your project or workflow
|
||||
- Automate email composer operations at scale
|
||||
- Generate production-quality email composer output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your email composer request
|
||||
2. Apply best practices and conventions for Writing & Communication
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with email composer.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for email composer in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready email composer setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened email composer implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: epub-creator
|
||||
display_name: ePub Creator
|
||||
description: Package text and images into valid ePub 3 e-books — chapters, TOC, cover images, and metadata for Kindle and Apple Books.
|
||||
category: Documents & Files
|
||||
platforms: [claude.ai, claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [epub-creator]
|
||||
---
|
||||
|
||||
# ePub Creator
|
||||
|
||||
## Overview
|
||||
|
||||
Package text and images into valid ePub 3 e-books — chapters, TOC, cover images, and metadata for Kindle and Apple Books.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **ePub Creator** when you need to:
|
||||
|
||||
- Work with epub creator tasks in your project or workflow
|
||||
- Automate epub creator operations at scale
|
||||
- Generate production-quality epub creator output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your epub creator request
|
||||
2. Apply best practices and conventions for Documents & Files
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with epub creator.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for epub creator in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready epub creator setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened epub creator implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: python, ebooklib
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: etl-pipeline
|
||||
display_name: ETL Pipeline
|
||||
description: Build end-to-end ETL pipelines — extract from APIs/databases, transform, validate, and load into data warehouses.
|
||||
category: Data & Analytics
|
||||
platforms: [claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [etl-pipeline]
|
||||
---
|
||||
|
||||
# ETL Pipeline
|
||||
|
||||
## Overview
|
||||
|
||||
Build end-to-end ETL pipelines — extract from APIs/databases, transform, validate, and load into data warehouses.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **ETL Pipeline** when you need to:
|
||||
|
||||
- Work with etl pipeline tasks in your project or workflow
|
||||
- Automate etl pipeline operations at scale
|
||||
- Generate production-quality etl pipeline output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your etl pipeline request
|
||||
2. Apply best practices and conventions for Data & Analytics
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with etl pipeline.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for etl pipeline in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready etl pipeline setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened etl pipeline implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: python, airflow, dbt
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: exam-prep
|
||||
display_name: Exam Prep
|
||||
description: Prepare for exams — practice tests, weak-area drills, timed quizzes, and performance feedback.
|
||||
category: Education & Learning
|
||||
platforms: [claude.ai, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [exam-prep]
|
||||
---
|
||||
|
||||
# Exam Prep
|
||||
|
||||
## Overview
|
||||
|
||||
Prepare for exams — practice tests, weak-area drills, timed quizzes, and performance feedback.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Exam Prep** when you need to:
|
||||
|
||||
- Work with exam prep tasks in your project or workflow
|
||||
- Automate exam prep operations at scale
|
||||
- Generate production-quality exam prep output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your exam prep request
|
||||
2. Apply best practices and conventions for Education & Learning
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with exam prep.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for exam prep in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready exam prep setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened exam prep implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: explainer-writer
|
||||
display_name: Explainer Writer
|
||||
description: Explain complex topics simply — analogies, Feynman technique breakdowns, and layered explanations for any audience.
|
||||
category: Education & Learning
|
||||
platforms: [claude.ai, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [explainer-writer]
|
||||
---
|
||||
|
||||
# Explainer Writer
|
||||
|
||||
## Overview
|
||||
|
||||
Explain complex topics simply — analogies, Feynman technique breakdowns, and layered explanations for any audience.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Explainer Writer** when you need to:
|
||||
|
||||
- Work with explainer writer tasks in your project or workflow
|
||||
- Automate explainer writer operations at scale
|
||||
- Generate production-quality explainer writer output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your explainer writer request
|
||||
2. Apply best practices and conventions for Education & Learning
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with explainer writer.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for explainer writer in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready explainer writer setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened explainer writer implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: fact-checker
|
||||
display_name: Fact Checker
|
||||
description: Verify claims and sources — cross-reference facts, assess source credibility, and flag misinformation.
|
||||
category: Research & Analysis
|
||||
platforms: [claude.ai, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [fact-checker]
|
||||
---
|
||||
|
||||
# Fact Checker
|
||||
|
||||
## Overview
|
||||
|
||||
Verify claims and sources — cross-reference facts, assess source credibility, and flag misinformation.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Fact Checker** when you need to:
|
||||
|
||||
- Work with fact checker tasks in your project or workflow
|
||||
- Automate fact checker operations at scale
|
||||
- Generate production-quality fact checker output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your fact checker request
|
||||
2. Apply best practices and conventions for Research & Analysis
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with fact checker.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for fact checker in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready fact checker setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened fact checker implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: feature-engineer
|
||||
display_name: Feature Engineer
|
||||
description: Design and create ML features — encoding, scaling, interaction terms, embeddings, and feature selection.
|
||||
category: Data & Analytics
|
||||
platforms: [claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [feature-engineer]
|
||||
---
|
||||
|
||||
# Feature Engineer
|
||||
|
||||
## Overview
|
||||
|
||||
Design and create ML features — encoding, scaling, interaction terms, embeddings, and feature selection.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Feature Engineer** when you need to:
|
||||
|
||||
- Work with feature engineer tasks in your project or workflow
|
||||
- Automate feature engineer operations at scale
|
||||
- Generate production-quality feature engineer output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your feature engineer request
|
||||
2. Apply best practices and conventions for Data & Analytics
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with feature engineer.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for feature engineer in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready feature engineer setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened feature engineer implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: python, pandas, sklearn
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: feedback-analyzer
|
||||
display_name: Feedback Analyzer
|
||||
description: Analyze customer feedback — sentiment analysis, theme clustering, NPS interpretation, and improvement roadmaps.
|
||||
category: Business & Productivity
|
||||
platforms: [claude.ai, claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [feedback-analyzer]
|
||||
---
|
||||
|
||||
# Feedback Analyzer
|
||||
|
||||
## Overview
|
||||
|
||||
Analyze customer feedback — sentiment analysis, theme clustering, NPS interpretation, and improvement roadmaps.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Feedback Analyzer** when you need to:
|
||||
|
||||
- Work with feedback analyzer tasks in your project or workflow
|
||||
- Automate feedback analyzer operations at scale
|
||||
- Generate production-quality feedback analyzer output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your feedback analyzer request
|
||||
2. Apply best practices and conventions for Business & Productivity
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with feedback analyzer.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for feedback analyzer in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready feedback analyzer setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened feedback analyzer implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: financial-model
|
||||
display_name: Financial Model
|
||||
description: Build financial models — P&L projections, cash flow forecasts, unit economics, DCF valuations, and scenario analysis.
|
||||
category: Business & Productivity
|
||||
platforms: [claude.ai, claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [financial-model]
|
||||
---
|
||||
|
||||
# Financial Model
|
||||
|
||||
## Overview
|
||||
|
||||
Build financial models — P&L projections, cash flow forecasts, unit economics, DCF valuations, and scenario analysis.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Financial Model** when you need to:
|
||||
|
||||
- Work with financial model tasks in your project or workflow
|
||||
- Automate financial model operations at scale
|
||||
- Generate production-quality financial model output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your financial model request
|
||||
2. Apply best practices and conventions for Business & Productivity
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with financial model.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for financial model in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready financial model setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened financial model implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: python, excel
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: flashcard-maker
|
||||
display_name: Flashcard Maker
|
||||
description: Create Anki-compatible flashcard decks — spaced repetition, cloze deletions, images, and export to CSV/APKG.
|
||||
category: Education & Learning
|
||||
platforms: [claude.ai, claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [flashcard-maker]
|
||||
---
|
||||
|
||||
# Flashcard Maker
|
||||
|
||||
## Overview
|
||||
|
||||
Create Anki-compatible flashcard decks — spaced repetition, cloze deletions, images, and export to CSV/APKG.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Flashcard Maker** when you need to:
|
||||
|
||||
- Work with flashcard maker tasks in your project or workflow
|
||||
- Automate flashcard maker operations at scale
|
||||
- Generate production-quality flashcard maker output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your flashcard maker request
|
||||
2. Apply best practices and conventions for Education & Learning
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with flashcard maker.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for flashcard maker in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready flashcard maker setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened flashcard maker implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: form-filler
|
||||
display_name: Form Filler
|
||||
description: Automatically fill PDF and HTML forms from structured data — applications, registrations, and government forms.
|
||||
category: Documents & Files
|
||||
platforms: [claude.ai, claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [form-filler]
|
||||
---
|
||||
|
||||
# Form Filler
|
||||
|
||||
## Overview
|
||||
|
||||
Automatically fill PDF and HTML forms from structured data — applications, registrations, and government forms.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Form Filler** when you need to:
|
||||
|
||||
- Work with form filler tasks in your project or workflow
|
||||
- Automate form filler operations at scale
|
||||
- Generate production-quality form filler output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your form filler request
|
||||
2. Apply best practices and conventions for Documents & Files
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with form filler.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for form filler in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready form filler setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened form filler implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: python, pypdf2
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: gcp-architect
|
||||
display_name: GCP Architect
|
||||
description: Design Google Cloud architectures — GKE, Cloud Run, BigQuery, Pub/Sub, and Cloud Spanner solutions.
|
||||
category: DevOps & Infrastructure
|
||||
platforms: [claude.ai, claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [gcp-architect]
|
||||
---
|
||||
|
||||
# GCP Architect
|
||||
|
||||
## Overview
|
||||
|
||||
Design Google Cloud architectures — GKE, Cloud Run, BigQuery, Pub/Sub, and Cloud Spanner solutions.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **GCP Architect** when you need to:
|
||||
|
||||
- Work with gcp architect tasks in your project or workflow
|
||||
- Automate gcp architect operations at scale
|
||||
- Generate production-quality gcp architect output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your gcp architect request
|
||||
2. Apply best practices and conventions for DevOps & Infrastructure
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with gcp architect.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for gcp architect in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready gcp architect setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened gcp architect implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: gcp, terraform
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: gdpr-helper
|
||||
display_name: GDPR Helper
|
||||
description: Navigate GDPR compliance — data mapping, DPIAs, consent flows, breach notification templates, and privacy policies.
|
||||
category: Security
|
||||
platforms: [claude.ai, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [gdpr-helper]
|
||||
---
|
||||
|
||||
# GDPR Helper
|
||||
|
||||
## Overview
|
||||
|
||||
Navigate GDPR compliance — data mapping, DPIAs, consent flows, breach notification templates, and privacy policies.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **GDPR Helper** when you need to:
|
||||
|
||||
- Work with gdpr helper tasks in your project or workflow
|
||||
- Automate gdpr helper operations at scale
|
||||
- Generate production-quality gdpr helper output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your gdpr helper request
|
||||
2. Apply best practices and conventions for Security
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with gdpr helper.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for gdpr helper in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready gdpr helper setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened gdpr helper implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: github-actions
|
||||
display_name: GitHub Actions
|
||||
description: Build GitHub Actions workflows — CI, CD, automated releases, dependency updates, and custom composite actions.
|
||||
category: DevOps & Infrastructure
|
||||
platforms: [claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [github-actions]
|
||||
---
|
||||
|
||||
# GitHub Actions
|
||||
|
||||
## Overview
|
||||
|
||||
Build GitHub Actions workflows — CI, CD, automated releases, dependency updates, and custom composite actions.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **GitHub Actions** when you need to:
|
||||
|
||||
- Work with github actions tasks in your project or workflow
|
||||
- Automate github actions operations at scale
|
||||
- Generate production-quality github actions output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your github actions request
|
||||
2. Apply best practices and conventions for DevOps & Infrastructure
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with github actions.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for github actions in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready github actions setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened github actions implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: github-actions
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: github-integration
|
||||
display_name: GitHub Integration
|
||||
description: Integrate with GitHub — Actions, Apps, webhooks, Octokit, and repository automation workflows.
|
||||
category: Integrations & Automation
|
||||
platforms: [claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [github-integration]
|
||||
---
|
||||
|
||||
# GitHub Integration
|
||||
|
||||
## Overview
|
||||
|
||||
Integrate with GitHub — Actions, Apps, webhooks, Octokit, and repository automation workflows.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **GitHub Integration** when you need to:
|
||||
|
||||
- Work with github integration tasks in your project or workflow
|
||||
- Automate github integration operations at scale
|
||||
- Generate production-quality github integration output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your github integration request
|
||||
2. Apply best practices and conventions for Integrations & Automation
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with github integration.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for github integration in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready github integration setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened github integration implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: typescript, octokit
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: gitlab-ci
|
||||
display_name: GitLab CI
|
||||
description: Create GitLab CI/CD pipelines — stages, jobs, caching, artifacts, environments, and Auto DevOps customization.
|
||||
category: DevOps & Infrastructure
|
||||
platforms: [claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [gitlab-ci]
|
||||
---
|
||||
|
||||
# GitLab CI
|
||||
|
||||
## Overview
|
||||
|
||||
Create GitLab CI/CD pipelines — stages, jobs, caching, artifacts, environments, and Auto DevOps customization.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **GitLab CI** when you need to:
|
||||
|
||||
- Work with gitlab ci tasks in your project or workflow
|
||||
- Automate gitlab ci operations at scale
|
||||
- Generate production-quality gitlab ci output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your gitlab ci request
|
||||
2. Apply best practices and conventions for DevOps & Infrastructure
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with gitlab ci.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for gitlab ci in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready gitlab ci setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened gitlab ci implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: gitlab-ci
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: grant-writer
|
||||
display_name: Grant Writer
|
||||
description: Write compelling grant applications — needs statements, project narratives, budgets, and evaluation plans.
|
||||
category: Writing & Communication
|
||||
platforms: [claude.ai, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [grant-writer]
|
||||
---
|
||||
|
||||
# Grant Writer
|
||||
|
||||
## Overview
|
||||
|
||||
Write compelling grant applications — needs statements, project narratives, budgets, and evaluation plans.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Grant Writer** when you need to:
|
||||
|
||||
- Work with grant writer tasks in your project or workflow
|
||||
- Automate grant writer operations at scale
|
||||
- Generate production-quality grant writer output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your grant writer request
|
||||
2. Apply best practices and conventions for Writing & Communication
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with grant writer.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for grant writer in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready grant writer setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened grant writer implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: graphql-builder
|
||||
display_name: GraphQL Builder
|
||||
description: Design and implement GraphQL schemas — types, queries, mutations, subscriptions, resolvers, and federation.
|
||||
category: Development
|
||||
platforms: [claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [graphql-builder]
|
||||
---
|
||||
|
||||
# GraphQL Builder
|
||||
|
||||
## Overview
|
||||
|
||||
Design and implement GraphQL schemas — types, queries, mutations, subscriptions, resolvers, and federation.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **GraphQL Builder** when you need to:
|
||||
|
||||
- Work with graphql builder tasks in your project or workflow
|
||||
- Automate graphql builder operations at scale
|
||||
- Generate production-quality graphql builder output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your graphql builder request
|
||||
2. Apply best practices and conventions for Development
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with graphql builder.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for graphql builder in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready graphql builder setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened graphql builder implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: graphql, apollo, hasura
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: helm-chart-builder
|
||||
display_name: Helm Chart Builder
|
||||
description: Create Helm charts — templates, values, helpers, hooks, tests, and OCI chart publishing.
|
||||
category: DevOps & Infrastructure
|
||||
platforms: [claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [helm-chart-builder]
|
||||
---
|
||||
|
||||
# Helm Chart Builder
|
||||
|
||||
## Overview
|
||||
|
||||
Create Helm charts — templates, values, helpers, hooks, tests, and OCI chart publishing.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Helm Chart Builder** when you need to:
|
||||
|
||||
- Work with helm chart builder tasks in your project or workflow
|
||||
- Automate helm chart builder operations at scale
|
||||
- Generate production-quality helm chart builder output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your helm chart builder request
|
||||
2. Apply best practices and conventions for DevOps & Infrastructure
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with helm chart builder.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for helm chart builder in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready helm chart builder setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened helm chart builder implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: helm, kubernetes
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: icon-generator
|
||||
display_name: Icon Generator
|
||||
description: Generate consistent icon sets in SVG — line icons, filled icons, duotone, and multi-size PNG exports for apps and websites.
|
||||
category: Creative & Design
|
||||
platforms: [claude.ai, claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [icon-generator]
|
||||
---
|
||||
|
||||
# Icon Generator
|
||||
|
||||
## Overview
|
||||
|
||||
Generate consistent icon sets in SVG — line icons, filled icons, duotone, and multi-size PNG exports for apps and websites.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Icon Generator** when you need to:
|
||||
|
||||
- Work with icon generator tasks in your project or workflow
|
||||
- Automate icon generator operations at scale
|
||||
- Generate production-quality icon generator output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your icon generator request
|
||||
2. Apply best practices and conventions for Creative & Design
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with icon generator.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for icon generator in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready icon generator setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened icon generator implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: svg
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: image-captioner
|
||||
display_name: Image Captioner
|
||||
description: Generate alt text, captions, and metadata for images — accessibility compliance, social media, and SEO.
|
||||
category: Media & Content
|
||||
platforms: [claude.ai, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [image-captioner]
|
||||
---
|
||||
|
||||
# Image Captioner
|
||||
|
||||
## Overview
|
||||
|
||||
Generate alt text, captions, and metadata for images — accessibility compliance, social media, and SEO.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Image Captioner** when you need to:
|
||||
|
||||
- Work with image captioner tasks in your project or workflow
|
||||
- Automate image captioner operations at scale
|
||||
- Generate production-quality image captioner output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your image captioner request
|
||||
2. Apply best practices and conventions for Media & Content
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with image captioner.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for image captioner in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready image captioner setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened image captioner implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: infographic-builder
|
||||
display_name: Infographic Builder
|
||||
description: Build data-rich infographics as SVG or HTML — timelines, process flows, comparison charts, and statistical summaries.
|
||||
category: Creative & Design
|
||||
platforms: [claude.ai, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [infographic-builder]
|
||||
---
|
||||
|
||||
# Infographic Builder
|
||||
|
||||
## Overview
|
||||
|
||||
Build data-rich infographics as SVG or HTML — timelines, process flows, comparison charts, and statistical summaries.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Infographic Builder** when you need to:
|
||||
|
||||
- Work with infographic builder tasks in your project or workflow
|
||||
- Automate infographic builder operations at scale
|
||||
- Generate production-quality infographic builder output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your infographic builder request
|
||||
2. Apply best practices and conventions for Creative & Design
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with infographic builder.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for infographic builder in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready infographic builder setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened infographic builder implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: svg, d3
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: internal-comms
|
||||
display_name: Internal Comms
|
||||
description: Write internal communications — all-hands updates, policy announcements, team memos, and executive briefings.
|
||||
category: Writing & Communication
|
||||
platforms: [claude.ai, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [internal-comms]
|
||||
---
|
||||
|
||||
# Internal Comms
|
||||
|
||||
## Overview
|
||||
|
||||
Write internal communications — all-hands updates, policy announcements, team memos, and executive briefings.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Internal Comms** when you need to:
|
||||
|
||||
- Work with internal comms tasks in your project or workflow
|
||||
- Automate internal comms operations at scale
|
||||
- Generate production-quality internal comms output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your internal comms request
|
||||
2. Apply best practices and conventions for Writing & Communication
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with internal comms.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for internal comms in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready internal comms setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened internal comms implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: interview-guide
|
||||
display_name: Interview Guide
|
||||
description: Create qualitative interview guides — discussion guides, probing questions, thematic analysis, and synthesis frameworks.
|
||||
category: Research & Analysis
|
||||
platforms: [claude.ai, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [interview-guide]
|
||||
---
|
||||
|
||||
# Interview Guide
|
||||
|
||||
## Overview
|
||||
|
||||
Create qualitative interview guides — discussion guides, probing questions, thematic analysis, and synthesis frameworks.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Interview Guide** when you need to:
|
||||
|
||||
- Work with interview guide tasks in your project or workflow
|
||||
- Automate interview guide operations at scale
|
||||
- Generate production-quality interview guide output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your interview guide request
|
||||
2. Apply best practices and conventions for Research & Analysis
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with interview guide.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for interview guide in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready interview guide setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened interview guide implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: interview-questions
|
||||
display_name: Interview Questions
|
||||
description: Generate structured interview guides — behavioral, technical, and situational questions with scoring rubrics.
|
||||
category: Business & Productivity
|
||||
platforms: [claude.ai, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [interview-questions]
|
||||
---
|
||||
|
||||
# Interview Questions
|
||||
|
||||
## Overview
|
||||
|
||||
Generate structured interview guides — behavioral, technical, and situational questions with scoring rubrics.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Interview Questions** when you need to:
|
||||
|
||||
- Work with interview questions tasks in your project or workflow
|
||||
- Automate interview questions operations at scale
|
||||
- Generate production-quality interview questions output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your interview questions request
|
||||
2. Apply best practices and conventions for Business & Productivity
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with interview questions.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for interview questions in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready interview questions setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened interview questions implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: invoice-creator
|
||||
display_name: Invoice Creator
|
||||
description: Generate professional PDF invoices with line items, taxes, discounts, payment terms, and company branding.
|
||||
category: Documents & Files
|
||||
platforms: [claude.ai, claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [invoice-creator]
|
||||
---
|
||||
|
||||
# Invoice Creator
|
||||
|
||||
## Overview
|
||||
|
||||
Generate professional PDF invoices with line items, taxes, discounts, payment terms, and company branding.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Invoice Creator** when you need to:
|
||||
|
||||
- Work with invoice creator tasks in your project or workflow
|
||||
- Automate invoice creator operations at scale
|
||||
- Generate production-quality invoice creator output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your invoice creator request
|
||||
2. Apply best practices and conventions for Documents & Files
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with invoice creator.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for invoice creator in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready invoice creator setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened invoice creator implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: python, reportlab
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: jenkins-pipeline
|
||||
display_name: Jenkins Pipeline
|
||||
description: Write Jenkins declarative and scripted pipelines — stages, parallel execution, credentials, and shared libraries.
|
||||
category: DevOps & Infrastructure
|
||||
platforms: [claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [jenkins-pipeline]
|
||||
---
|
||||
|
||||
# Jenkins Pipeline
|
||||
|
||||
## Overview
|
||||
|
||||
Write Jenkins declarative and scripted pipelines — stages, parallel execution, credentials, and shared libraries.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Jenkins Pipeline** when you need to:
|
||||
|
||||
- Work with jenkins pipeline tasks in your project or workflow
|
||||
- Automate jenkins pipeline operations at scale
|
||||
- Generate production-quality jenkins pipeline output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your jenkins pipeline request
|
||||
2. Apply best practices and conventions for DevOps & Infrastructure
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with jenkins pipeline.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for jenkins pipeline in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready jenkins pipeline setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened jenkins pipeline implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: jenkins, groovy
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: jira-helper
|
||||
display_name: Jira Helper
|
||||
description: Automate Jira — issue creation, sprint management, JQL queries, and project reporting via REST API.
|
||||
category: Integrations & Automation
|
||||
platforms: [claude.ai, claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [jira-helper]
|
||||
---
|
||||
|
||||
# Jira Helper
|
||||
|
||||
## Overview
|
||||
|
||||
Automate Jira — issue creation, sprint management, JQL queries, and project reporting via REST API.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Jira Helper** when you need to:
|
||||
|
||||
- Work with jira helper tasks in your project or workflow
|
||||
- Automate jira helper operations at scale
|
||||
- Generate production-quality jira helper output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your jira helper request
|
||||
2. Apply best practices and conventions for Integrations & Automation
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with jira helper.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for jira helper in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready jira helper setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened jira helper implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: job-description
|
||||
display_name: Job Description
|
||||
description: Write inclusive, compelling job descriptions — role summaries, requirements, benefits, and bias-free language.
|
||||
category: Business & Productivity
|
||||
platforms: [claude.ai, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [job-description]
|
||||
---
|
||||
|
||||
# Job Description
|
||||
|
||||
## Overview
|
||||
|
||||
Write inclusive, compelling job descriptions — role summaries, requirements, benefits, and bias-free language.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Job Description** when you need to:
|
||||
|
||||
- Work with job description tasks in your project or workflow
|
||||
- Automate job description operations at scale
|
||||
- Generate production-quality job description output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your job description request
|
||||
2. Apply best practices and conventions for Business & Productivity
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with job description.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for job description in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready job description setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened job description implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: json-formatter
|
||||
display_name: JSON Formatter
|
||||
description: Format, validate, transform, and query JSON data — pretty-print, minify, diff two JSON objects, and extract fields with JSONPath.
|
||||
category: Documents & Files
|
||||
platforms: [claude.ai, claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [json-formatter]
|
||||
---
|
||||
|
||||
# JSON Formatter
|
||||
|
||||
## Overview
|
||||
|
||||
Format, validate, transform, and query JSON data — pretty-print, minify, diff two JSON objects, and extract fields with JSONPath.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **JSON Formatter** when you need to:
|
||||
|
||||
- Work with json formatter tasks in your project or workflow
|
||||
- Automate json formatter operations at scale
|
||||
- Generate production-quality json formatter output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your json formatter request
|
||||
2. Apply best practices and conventions for Documents & Files
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with json formatter.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for json formatter in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready json formatter setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened json formatter implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: node, python
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: keyword-researcher
|
||||
display_name: Keyword Researcher
|
||||
description: Research keywords — intent mapping, competition analysis, long-tail opportunities, and cluster groupings.
|
||||
category: Media & Content
|
||||
platforms: [claude.ai, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [keyword-researcher]
|
||||
---
|
||||
|
||||
# Keyword Researcher
|
||||
|
||||
## Overview
|
||||
|
||||
Research keywords — intent mapping, competition analysis, long-tail opportunities, and cluster groupings.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Keyword Researcher** when you need to:
|
||||
|
||||
- Work with keyword researcher tasks in your project or workflow
|
||||
- Automate keyword researcher operations at scale
|
||||
- Generate production-quality keyword researcher output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your keyword researcher request
|
||||
2. Apply best practices and conventions for Media & Content
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with keyword researcher.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for keyword researcher in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready keyword researcher setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened keyword researcher implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: kpi-tracker
|
||||
display_name: KPI Tracker
|
||||
description: Design KPI frameworks — define metrics, set targets, build tracking templates, and generate progress reports.
|
||||
category: Data & Analytics
|
||||
platforms: [claude.ai, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [kpi-tracker]
|
||||
---
|
||||
|
||||
# KPI Tracker
|
||||
|
||||
## Overview
|
||||
|
||||
Design KPI frameworks — define metrics, set targets, build tracking templates, and generate progress reports.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **KPI Tracker** when you need to:
|
||||
|
||||
- Work with kpi tracker tasks in your project or workflow
|
||||
- Automate kpi tracker operations at scale
|
||||
- Generate production-quality kpi tracker output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your kpi tracker request
|
||||
2. Apply best practices and conventions for Data & Analytics
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with kpi tracker.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for kpi tracker in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready kpi tracker setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened kpi tracker implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: kubernetes-helper
|
||||
display_name: Kubernetes Helper
|
||||
description: Author Kubernetes manifests — Deployments, Services, Ingress, ConfigMaps, Secrets, HPA, and Helm charts.
|
||||
category: Development
|
||||
platforms: [claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [kubernetes-helper]
|
||||
---
|
||||
|
||||
# Kubernetes Helper
|
||||
|
||||
## Overview
|
||||
|
||||
Author Kubernetes manifests — Deployments, Services, Ingress, ConfigMaps, Secrets, HPA, and Helm charts.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Kubernetes Helper** when you need to:
|
||||
|
||||
- Work with kubernetes helper tasks in your project or workflow
|
||||
- Automate kubernetes helper operations at scale
|
||||
- Generate production-quality kubernetes helper output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your kubernetes helper request
|
||||
2. Apply best practices and conventions for Development
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with kubernetes helper.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for kubernetes helper in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready kubernetes helper setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened kubernetes helper implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: kubernetes, helm
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: latex-writer
|
||||
display_name: LaTeX Writer
|
||||
description: Author and compile LaTeX documents — academic papers, theses, mathematical equations, bibliographies, and Beamer presentations.
|
||||
category: Documents & Files
|
||||
platforms: [claude.ai, claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [latex-writer]
|
||||
---
|
||||
|
||||
# LaTeX Writer
|
||||
|
||||
## Overview
|
||||
|
||||
Author and compile LaTeX documents — academic papers, theses, mathematical equations, bibliographies, and Beamer presentations.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **LaTeX Writer** when you need to:
|
||||
|
||||
- Work with latex writer tasks in your project or workflow
|
||||
- Automate latex writer operations at scale
|
||||
- Generate production-quality latex writer output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your latex writer request
|
||||
2. Apply best practices and conventions for Documents & Files
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with latex writer.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for latex writer in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready latex writer setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened latex writer implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: latex
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: learning-path
|
||||
display_name: Learning Path
|
||||
description: Design personalized learning paths — skill assessment, resource curation, milestones, and progress tracking.
|
||||
category: Education & Learning
|
||||
platforms: [claude.ai, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [learning-path]
|
||||
---
|
||||
|
||||
# Learning Path
|
||||
|
||||
## Overview
|
||||
|
||||
Design personalized learning paths — skill assessment, resource curation, milestones, and progress tracking.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Learning Path** when you need to:
|
||||
|
||||
- Work with learning path tasks in your project or workflow
|
||||
- Automate learning path operations at scale
|
||||
- Generate production-quality learning path output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your learning path request
|
||||
2. Apply best practices and conventions for Education & Learning
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with learning path.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for learning path in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready learning path setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened learning path implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: lesson-planner
|
||||
display_name: Lesson Planner
|
||||
description: Plan engaging lessons — objectives, warm-ups, instruction, guided practice, assessments, and differentiation strategies.
|
||||
category: Education & Learning
|
||||
platforms: [claude.ai, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [lesson-planner]
|
||||
---
|
||||
|
||||
# Lesson Planner
|
||||
|
||||
## Overview
|
||||
|
||||
Plan engaging lessons — objectives, warm-ups, instruction, guided practice, assessments, and differentiation strategies.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Lesson Planner** when you need to:
|
||||
|
||||
- Work with lesson planner tasks in your project or workflow
|
||||
- Automate lesson planner operations at scale
|
||||
- Generate production-quality lesson planner output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your lesson planner request
|
||||
2. Apply best practices and conventions for Education & Learning
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with lesson planner.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for lesson planner in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready lesson planner setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened lesson planner implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: linkedin-post
|
||||
display_name: LinkedIn Post
|
||||
description: Write LinkedIn posts that build personal brand — thought leadership, storytelling, and algorithm-friendly formatting.
|
||||
category: Writing & Communication
|
||||
platforms: [claude.ai, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [linkedin-post]
|
||||
---
|
||||
|
||||
# LinkedIn Post
|
||||
|
||||
## Overview
|
||||
|
||||
Write LinkedIn posts that build personal brand — thought leadership, storytelling, and algorithm-friendly formatting.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **LinkedIn Post** when you need to:
|
||||
|
||||
- Work with linkedin post tasks in your project or workflow
|
||||
- Automate linkedin post operations at scale
|
||||
- Generate production-quality linkedin post output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your linkedin post request
|
||||
2. Apply best practices and conventions for Writing & Communication
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with linkedin post.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for linkedin post in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready linkedin post setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened linkedin post implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: literature-reviewer
|
||||
display_name: Literature Reviewer
|
||||
description: Review academic literature — summarize papers, extract key findings, identify gaps, and synthesize research themes.
|
||||
category: Research & Analysis
|
||||
platforms: [claude.ai, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [literature-reviewer]
|
||||
---
|
||||
|
||||
# Literature Reviewer
|
||||
|
||||
## Overview
|
||||
|
||||
Review academic literature — summarize papers, extract key findings, identify gaps, and synthesize research themes.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Literature Reviewer** when you need to:
|
||||
|
||||
- Work with literature reviewer tasks in your project or workflow
|
||||
- Automate literature reviewer operations at scale
|
||||
- Generate production-quality literature reviewer output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your literature reviewer request
|
||||
2. Apply best practices and conventions for Research & Analysis
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with literature reviewer.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for literature reviewer in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready literature reviewer setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened literature reviewer implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: log-analyzer
|
||||
display_name: Log Analyzer
|
||||
description: Analyze application and infrastructure logs — pattern detection, error clustering, and anomaly identification.
|
||||
category: DevOps & Infrastructure
|
||||
platforms: [claude.ai, claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [log-analyzer]
|
||||
---
|
||||
|
||||
# Log Analyzer
|
||||
|
||||
## Overview
|
||||
|
||||
Analyze application and infrastructure logs — pattern detection, error clustering, and anomaly identification.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Log Analyzer** when you need to:
|
||||
|
||||
- Work with log analyzer tasks in your project or workflow
|
||||
- Automate log analyzer operations at scale
|
||||
- Generate production-quality log analyzer output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your log analyzer request
|
||||
2. Apply best practices and conventions for DevOps & Infrastructure
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with log analyzer.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for log analyzer in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready log analyzer setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened log analyzer implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: elasticsearch, loki
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: logo-designer
|
||||
display_name: Logo Designer
|
||||
description: Design SVG logos with multiple variants — primary, monochrome, favicon, and animated versions with brand alignment.
|
||||
category: Creative & Design
|
||||
platforms: [claude.ai, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [logo-designer]
|
||||
---
|
||||
|
||||
# Logo Designer
|
||||
|
||||
## Overview
|
||||
|
||||
Design SVG logos with multiple variants — primary, monochrome, favicon, and animated versions with brand alignment.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Logo Designer** when you need to:
|
||||
|
||||
- Work with logo designer tasks in your project or workflow
|
||||
- Automate logo designer operations at scale
|
||||
- Generate production-quality logo designer output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your logo designer request
|
||||
2. Apply best practices and conventions for Creative & Design
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with logo designer.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for logo designer in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready logo designer setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened logo designer implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: svg
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: mail-merge
|
||||
display_name: Mail Merge
|
||||
description: Generate personalized documents from templates and data sources — bulk letters, certificates, invoices, and email campaigns.
|
||||
category: Documents & Files
|
||||
platforms: [claude.ai, claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [mail-merge]
|
||||
---
|
||||
|
||||
# Mail Merge
|
||||
|
||||
## Overview
|
||||
|
||||
Generate personalized documents from templates and data sources — bulk letters, certificates, invoices, and email campaigns.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Mail Merge** when you need to:
|
||||
|
||||
- Work with mail merge tasks in your project or workflow
|
||||
- Automate mail merge operations at scale
|
||||
- Generate production-quality mail merge output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your mail merge request
|
||||
2. Apply best practices and conventions for Documents & Files
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with mail merge.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for mail merge in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready mail merge setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened mail merge implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: python
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: make-scenario
|
||||
display_name: Make Scenario
|
||||
description: Create Make (Integromat) scenarios — modules, routers, aggregators, and error handlers.
|
||||
category: Integrations & Automation
|
||||
platforms: [claude.ai, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [make-scenario]
|
||||
---
|
||||
|
||||
# Make Scenario
|
||||
|
||||
## Overview
|
||||
|
||||
Create Make (Integromat) scenarios — modules, routers, aggregators, and error handlers.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Make Scenario** when you need to:
|
||||
|
||||
- Work with make scenario tasks in your project or workflow
|
||||
- Automate make scenario operations at scale
|
||||
- Generate production-quality make scenario output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your make scenario request
|
||||
2. Apply best practices and conventions for Integrations & Automation
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with make scenario.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for make scenario in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready make scenario setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened make scenario implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: markdown-pro
|
||||
display_name: Markdown Pro
|
||||
description: Generate, format, and convert Markdown documents — README files, wikis, changelogs, and full documentation sites.
|
||||
category: Documents & Files
|
||||
platforms: [claude.ai, claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [markdown-pro]
|
||||
---
|
||||
|
||||
# Markdown Pro
|
||||
|
||||
## Overview
|
||||
|
||||
Generate, format, and convert Markdown documents — README files, wikis, changelogs, and full documentation sites.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Markdown Pro** when you need to:
|
||||
|
||||
- Work with markdown pro tasks in your project or workflow
|
||||
- Automate markdown pro operations at scale
|
||||
- Generate production-quality markdown pro output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your markdown pro request
|
||||
2. Apply best practices and conventions for Documents & Files
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with markdown pro.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for markdown pro in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready markdown pro setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened markdown pro implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: market-analyzer
|
||||
display_name: Market Analyzer
|
||||
description: Analyze markets — TAM/SAM/SOM sizing, Porter's Five Forces, SWOT analysis, and customer segmentation.
|
||||
category: Business & Productivity
|
||||
platforms: [claude.ai, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [market-analyzer]
|
||||
---
|
||||
|
||||
# Market Analyzer
|
||||
|
||||
## Overview
|
||||
|
||||
Analyze markets — TAM/SAM/SOM sizing, Porter's Five Forces, SWOT analysis, and customer segmentation.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Market Analyzer** when you need to:
|
||||
|
||||
- Work with market analyzer tasks in your project or workflow
|
||||
- Automate market analyzer operations at scale
|
||||
- Generate production-quality market analyzer output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your market analyzer request
|
||||
2. Apply best practices and conventions for Business & Productivity
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with market analyzer.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for market analyzer in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready market analyzer setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened market analyzer implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: market-researcher
|
||||
display_name: Market Researcher
|
||||
description: Conduct market research — survey design, interview scripts, secondary research synthesis, and insight reports.
|
||||
category: Research & Analysis
|
||||
platforms: [claude.ai, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [market-researcher]
|
||||
---
|
||||
|
||||
# Market Researcher
|
||||
|
||||
## Overview
|
||||
|
||||
Conduct market research — survey design, interview scripts, secondary research synthesis, and insight reports.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Market Researcher** when you need to:
|
||||
|
||||
- Work with market researcher tasks in your project or workflow
|
||||
- Automate market researcher operations at scale
|
||||
- Generate production-quality market researcher output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your market researcher request
|
||||
2. Apply best practices and conventions for Research & Analysis
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with market researcher.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for market researcher in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready market researcher setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened market researcher implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: mcp-builder
|
||||
display_name: MCP Builder
|
||||
description: Scaffold and implement Model Context Protocol servers — tools, resources, prompts, and sampling handlers.
|
||||
category: Development
|
||||
platforms: [claude-code, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [mcp-builder]
|
||||
---
|
||||
|
||||
# MCP Builder
|
||||
|
||||
## Overview
|
||||
|
||||
Scaffold and implement Model Context Protocol servers — tools, resources, prompts, and sampling handlers.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **MCP Builder** when you need to:
|
||||
|
||||
- Work with mcp builder tasks in your project or workflow
|
||||
- Automate mcp builder operations at scale
|
||||
- Generate production-quality mcp builder output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your mcp builder request
|
||||
2. Apply best practices and conventions for Development
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with mcp builder.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for mcp builder in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready mcp builder setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened mcp builder implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: typescript, python
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude-code, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: meeting-agenda
|
||||
display_name: Meeting Agenda
|
||||
description: Create effective meeting agendas — objectives, time boxes, pre-read materials, and decision frameworks.
|
||||
category: Business & Productivity
|
||||
platforms: [claude.ai, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [meeting-agenda]
|
||||
---
|
||||
|
||||
# Meeting Agenda
|
||||
|
||||
## Overview
|
||||
|
||||
Create effective meeting agendas — objectives, time boxes, pre-read materials, and decision frameworks.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Meeting Agenda** when you need to:
|
||||
|
||||
- Work with meeting agenda tasks in your project or workflow
|
||||
- Automate meeting agenda operations at scale
|
||||
- Generate production-quality meeting agenda output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your meeting agenda request
|
||||
2. Apply best practices and conventions for Business & Productivity
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with meeting agenda.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for meeting agenda in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready meeting agenda setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened meeting agenda implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: meeting-summarizer
|
||||
display_name: Meeting Summarizer
|
||||
description: Summarize meetings from transcripts — key decisions, action items, owners, deadlines, and follow-up emails.
|
||||
category: Writing & Communication
|
||||
platforms: [claude.ai, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [meeting-summarizer]
|
||||
---
|
||||
|
||||
# Meeting Summarizer
|
||||
|
||||
## Overview
|
||||
|
||||
Summarize meetings from transcripts — key decisions, action items, owners, deadlines, and follow-up emails.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Meeting Summarizer** when you need to:
|
||||
|
||||
- Work with meeting summarizer tasks in your project or workflow
|
||||
- Automate meeting summarizer operations at scale
|
||||
- Generate production-quality meeting summarizer output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your meeting summarizer request
|
||||
2. Apply best practices and conventions for Writing & Communication
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with meeting summarizer.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for meeting summarizer in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready meeting summarizer setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened meeting summarizer implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
@@ -0,0 +1,67 @@
|
||||
---
|
||||
name: midjourney-prompter
|
||||
display_name: Midjourney Prompter
|
||||
description: Engineer Midjourney prompts — style references, aspect ratios, negative prompts, and v6 parameter tuning.
|
||||
category: Media & Content
|
||||
platforms: [claude.ai, api]
|
||||
version: 1.0.0
|
||||
author: Claude Code
|
||||
tags: [midjourney-prompter]
|
||||
---
|
||||
|
||||
# Midjourney Prompter
|
||||
|
||||
## Overview
|
||||
|
||||
Engineer Midjourney prompts — style references, aspect ratios, negative prompts, and v6 parameter tuning.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use **Midjourney Prompter** when you need to:
|
||||
|
||||
- Work with midjourney prompter tasks in your project or workflow
|
||||
- Automate midjourney prompter operations at scale
|
||||
- Generate production-quality midjourney prompter output quickly
|
||||
|
||||
## Instructions
|
||||
|
||||
When this skill is active, Claude will:
|
||||
|
||||
1. Understand the full context of your midjourney prompter request
|
||||
2. Apply best practices and conventions for Media & Content
|
||||
3. Produce clean, well-structured, production-ready output
|
||||
4. Explain key decisions and offer alternatives where relevant
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1 — Basic Usage
|
||||
|
||||
**User:** Help me get started with midjourney prompter.
|
||||
|
||||
**Claude:** I'll walk you through the essential steps for midjourney prompter in your context...
|
||||
|
||||
### Example 2 — Advanced Usage
|
||||
|
||||
**User:** I need a production-ready midjourney prompter setup with full error handling.
|
||||
|
||||
**Claude:** Here's a complete, production-hardened midjourney prompter implementation...
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Always validate inputs before processing
|
||||
- Follow the conventions of the target platform or language
|
||||
- Prefer explicit over implicit — clarity beats cleverness
|
||||
- Include comments for non-obvious logic
|
||||
- Suggest tests or validation steps where appropriate
|
||||
|
||||
## Dependencies
|
||||
|
||||
Required: none
|
||||
|
||||
## Platforms
|
||||
|
||||
Available on: claude.ai, api
|
||||
|
||||
---
|
||||
|
||||
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user