skill-creator
Create Better Claude Skills
Skill authors need a repeatable process for turning workflows into useful AI skills. This skill provides clear steps for examples, resource planning, metadata, packaging, and iteration.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "skill-creator" from https://skillstore.io/skills/bom-98-skill-creator.md and its manifest at https://skillstore.io/api/skills/bom-98-skill-creator/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "skill-creator". I want a skill that helps with monthly finance reports.
Expected outcome:
A useful result would define the target report workflow, identify reusable finance schema references, and recommend concise SKILL.md instructions.
Using "skill-creator". My SKILL.md is too long and includes many examples.
Expected outcome:
A useful result would move detailed examples into reference files and keep only essential activation and workflow guidance in SKILL.md.
Using "skill-creator". I need to package a skill for another Claude instance.
Expected outcome:
A useful result would check metadata, file organization, optional scripts, references, assets, validation steps, and packaging readiness.
Security Audit
SafeThe reviewed skill is a documentation-only guide for creating Claude skills. Static findings are false positives caused by Markdown code fences, inline code examples, documentation links, and safe environment-file guidance; no malicious intent, prompt injection, exfiltration, or executable payload was found.
Risk Factors
โ๏ธ External commands (34)
๐ Network access (3)
๐ Filesystem access (1)
๐ Env variables (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/bom-98-skill-creator/audits/10?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/bom-98-skill-creator?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/bom-98-skill-creator?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/bom-98-skill-creator/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/bom-98-skill-creator.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
BOM-98. (2026). skill-creator security audit report (audit version 10) [Author version unspecified]. Skillstore. https://skillstore.io/skills/bom-98-skill-creator/audits/10BibTeX citation
@techreport{bom-98-bom-98-skill-creator-2026,
author = {BOM-98},
title = {skill-creator security audit report (audit version 10)},
institution = {Skillstore},
year = {2026},
number = {10},
url = {https://skillstore.io/skills/bom-98-skill-creator/audits/10},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "skill-creator security audit report (audit version 10)"
version: "unspecified"
type: report
authors:
- name: "BOM-98"
date-released: "2026-07-09"
url: "https://skillstore.io/skills/bom-98-skill-creator/audits/10"
identifiers:
- type: other
value: "skillstore:bom-98-skill-creator:audit:10"
description: "Skillstore immutable audit report identifier"
Compare variants
24 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
89jobrien-skill-creator
2026-08-21
vercel-labs-skill-creator
2026-08-21
7spade-skill-creator
2026-08-21
daviddworetzky-skill-creator
2026-08-21
bom-98-skill-creator
2026-08-21
doyajin174-skill-creator
2026-08-21
cesaraugustusgrob-skill-creator
2026-08-21
skill-creator
2026-08-21
cam10001110101-skill-creator
2026-08-21
astrabit-cpt-skill-creator
2026-08-21
zhanlincui-skill-creator
2026-08-21
barissozen-skill-creator
2026-08-21
abdullahmalik17-skill-creator
2026-08-21
langchain-ai-skill-creator
2026-08-21
daothihuong2111-skill-creator
2026-08-21
benderfendor-skill-creator
2026-08-21
92bilal26-skill-creator
2026-08-21
sickn33-skill-creator
2026-08-21
artemisai-skill-creator
2026-08-21
davila7-skill-creator
2026-08-21
chinchillaenterprises-skill-creator
2026-08-21
azeem-2-skill-creator
2026-08-21
davila7-skill-development
2026-08-21
composiohq-skill-creator
2026-08-21
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Design a new domain skill
Turn repeated domain work into a structured skill with clear triggers, workflows, and supporting resources.
Improve an existing skill
Review a current skill for metadata quality, resource organization, and progressive disclosure.
Package reusable team knowledge
Organize scripts, references, and assets so another Claude instance can perform specialized work consistently.
Try These Prompts
Help me plan a new Claude skill for [task]. Ask only the most important questions first, then suggest the SKILL.md structure and resources.
Here are example requests for a skill: [examples]. Identify which scripts, references, and assets should be included, and explain why.
Review this skill name and description for activation quality: [metadata]. Make it concise, specific, and third-person.
Review this skill package outline: [outline]. Check progressive disclosure, resource placement, SKILL.md length, packaging readiness, and iteration risks.
Best Practices
- Start with concrete user examples before writing the final skill instructions.
- Keep SKILL.md concise and move detailed material into referenced resources.
- Use scripts only when repeatability or deterministic execution is important.
Avoid
- Do not place all domain knowledge directly in SKILL.md when references would work better.
- Do not write vague metadata that prevents automatic skill activation.
- Do not keep generated example files that are not needed by the final skill.