aiskillstore/skill-creator
skills/barissozen/skill-creator/SKILL.md
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
$ install --global
skillsauthnpx skillsauth add aiskillstore/marketplace skill-creatorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Mar 31, 2026, 1:27 AM59.9s5 files scanned
SKILL.md
- name:
- skill-creator
- description:
- Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Skill Creator
This skill provides guidance for creating effective skills.
When to Use
- Creating a new skill from scratch
- Updating an existing skill
- Organizing skill structure (scripts, references, assets)
- Packaging skills for distribution
- Reviewing skill quality
Workflow
Step 1: Understand Requirements
Gather examples of how the skill will be used.
Step 2: Plan Contents
Identify scripts, references, and assets needed.
Step 3: Initialize Structure
Run init_skill.py to create directory structure.
Step 4: Edit SKILL.md
Define purpose, triggers, and workflow.
Step 5: Package
Run package_skill.py to validate and zip.
Step 6: Iterate
Test and improve based on real usage.
About Skills
Skills are modular, self-contained packages that extend Claude's capabilities by providing specialized knowledge, workflows, and tools. Think of them as "onboarding guides" for specific domains or tasks—they transform Claude from a general-purpose agent into a specialized agent equipped with procedural knowledge that no model can fully possess.
What Skills Provide
- Specialized workflows - Multi-step procedures for specific domains
- Tool integrations - Instructions for working with specific file formats or APIs
- Domain expertise - Company-specific knowledge, schemas, business logic
- Bundled resources - Scripts, references, and assets for complex and repetitive tasks
Anatomy of a Skill
Every skill consists of a required SKILL.md file and optional bundled resources:
skill-name/
├── SKILL.md (required)
│ ├── YAML frontmatter metadata (required)
│ │ ├── name: (required)
│ │ └── description: (required)
│ └── Markdown instructions (required)
└── Bundled Resources (optional)
├── scripts/ - Executable code (Python/Bash/etc.)
├── references/ - Documentation to load into context as needed
└── assets/ - Files used in output (templates, icons, fonts, etc.)
Progressive Disclosure Design
Skills use a three-level loading system to manage context efficiently:
- Metadata (name + description) - Always in context (~100 words)
- SKILL.md body - When skill triggers (<5k words)
- Bundled resources - As needed by Claude (Unlimited*)
*Unlimited because scripts can be executed without reading into context window.
Skill Creation Process
Step 1: Understand the Skill with Examples
To create an effective skill, clearly understand concrete examples of how the skill will be used.
Questions to ask:
- "What functionality should this skill support?"
- "Can you give examples of how this skill would be used?"
- "What would a user say that should trigger this skill?"
Step 2: Plan the Reusable Skill Contents
Analyze each example by:
- Considering how to execute on the example from scratch
- Identifying what scripts, references, and assets would be helpful
When to use scripts/: When the same code is being rewritten repeatedly or deterministic reliability is needed.
When to use references/: For documentation that Claude should reference while working (schemas, API docs, policies).
When to use assets/: For files used in output (templates, images, boilerplate code).
Step 3: Initialize the Skill
Run the initialization script to create the skill structure:
python .claude/skills/skill-creator/scripts/init_skill.py <skill-name> --path <output-directory>
Step 4: Edit the Skill
Writing Style: Use imperative/infinitive form (verb-first instructions), not second person.
Answer these questions in SKILL.md:
- What is the purpose of the skill, in a few sentences?
- When should the skill be used?
- How should Claude use the skill? (Reference all bundled resources)
Step 5: Package the Skill
python .claude/skills/skill-creator/scripts/package_skill.py <path/to/skill-folder>
Step 6: Iterate
After testing, improve based on real usage:
- Use the skill on real tasks
- Notice struggles or inefficiencies
- Update SKILL.md or bundled resources
- Test again
Best Practices
- Keep SKILL.md under 5k words; move detailed content to references/
- Include grep patterns for large reference files (>10k words)
- Delete unused example directories created by init script
- Avoid information duplication between SKILL.md and references
- Use descriptive metadata - it determines when Claude uses the skill
Related Skills
aiskillstore/hig-components-content
development
VerifiedTrustedCommunity
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about charts component, collection view, image view, web view, color well, image well, activity view, lockup, data visualization, content display, displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says how should I display charts, what's the best way to show images, should I use a web view, how do I build a grid of items, what component shows media, or how do I present a share sheet. Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.
244SKILL.mdUpdated Apr 10, 2026
aiskillstore/helpdesk-automation
tools
VerifiedTrustedCommunity
Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.
244SKILL.mdUpdated Apr 10, 2026
aiskillstore/haskell-pro
testing
VerifiedTrustedCommunity
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
244SKILL.mdUpdated Apr 10, 2026
aiskillstore/graphql
tools
VerifiedTrustedCommunity
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.
244SKILL.mdUpdated Apr 10, 2026