terrylica/cc-skills

create

Create a new plugin for Claude Code marketplace with validation, ADR, and release automation.

Voir la source

Mode d’emploi

  1. Copiez la commande et examinez le paquet avant de l’installer dans votre environnement agent.
  2. Consultez le document original pour les outils, identifiants et environnements requis.
  3. Décrivez les entrées et le livrable souhaité ; comparez la sortie aux sources.
npx skills add https://github.com/terrylica/cc-skills --skill create

Avant de commencer

  • L’installation n’inclut ni abonnement au modèle, ni quota API, ni accès aux fichiers.
  • Étoiles et installations reflètent l’activité, pas un test indépendant de qualité ou de sécurité.
Document Skill original

Rendu depuis le dépôt source en conservant titres, exemples, code, tableaux, liens et images.

<!-- ⛔⛔⛔ MANDATORY: READ THIS ENTIRE FILE BEFORE ANY ACTION ⛔⛔⛔ -->

⛔ Create Plugin — STOP AND READ

DO NOT ACT ON ASSUMPTIONS. Read this file first.

This is a structured workflow command for creating a new plugin in a Claude Code marketplace.

Your FIRST and ONLY action right now: Execute the TodoWrite below.

Self-Evolving Skill: This skill improves through use. If instructions are wrong, parameters drifted, or a workaround was needed — fix this file immediately, don't defer. Only update for real, reproducible issues.

⛔ MANDATORY FIRST ACTION: TodoWrite Initialization

YOUR FIRST ACTION MUST BE the TodoWrite call below.

DO NOT:

  • ❌ Create any directories before TodoWrite
  • ❌ Read marketplace.json before TodoWrite
  • ❌ Ask questions before TodoWrite
  • ❌ Jump to any phase without completing Step 0

Step 0.1: Detect Marketplace Root

Before executing TodoWrite, verify you're in a marketplace directory:

bash
/usr/bin/env bash << 'PREFLIGHT_EOF'
# Check for marketplace.json in cwd
if [ -f ".claude-plugin/marketplace.json" ]; then
  echo "✅ Marketplace detected: $(jq -r .name .claude-plugin/marketplace.json)"
else
  echo "❌ Not a marketplace directory. Run from a marketplace root."
  exit 1
fi
PREFLIGHT_EOF

Step 0.2: Execute MANDATORY TodoWrite

Execute TodoWrite NOW with this template:

TodoWrite with todos:

- "[Plugin] Phase 0: Detect marketplace root" | in_progress
- "[Plugin] Phase 0: Interactive prompts (name, category, components)" | pending
- "[Plugin] Phase 0: Confirm plugin doesn't exist" | pending
- "[Plugin] Phase 1: Skill → plugin-structure (scaffold)" | pending
- "[Plugin] Phase 1: Create plugin directory + plugin.json" | pending
- "[Plugin] Phase 1: Skill → implement-plan-preflight (ADR)" | pending
- "[Plugin] Phase 2: Skill → skill-architecture (if has-skills)" | pending
- "[Plugin] Phase 2: Skill → hook-development (if has-hooks)" | pending
- "[Plugin] Phase 2: Skill → command-development (if has-commands)" | pending
- "[Plugin] Phase 2: Skill → agent-development (if has-agents)" | pending
- "[Plugin] Phase 2: Agent → skill-reviewer (if skills created)" | pending
- "[Plugin] Phase 3: Add to marketplace.json" | pending
- "[Plugin] Phase 3: Run validate-plugins.mjs" | pending
- "[Plugin] Phase 3: Skill → code-hardcode-audit" | pending
- "[Plugin] Phase 3: Agent → plugin-validator" | pending
- "[Plugin] Phase 4: Git commit (conventional format)" | pending
- "[Plugin] Phase 4: Push to remote" | pending
- "[Plugin] Phase 4: Skill → semantic-release" | pending

After TodoWrite completes, proceed to Phase 0 section below.


Quick Reference

Skills Invoked (Optimized Sequence)

OrderSkillPhasePurposeInvocation
1plugin-structure1Directory & manifestSkill(plugin-dev:plugin-structure)
2implement-plan-preflight1ADR + Design Spec + DiagramsSkill(itp:implement-plan-preflight)
3skill-architecture2Create skills (if has-skills)Skill(plugin-dev:skill-architecture)
4hook-development2Create hooks (if has-hooks)Skill(plugin-dev:hook-development)
5command-development2Create commands (if has-commands)Skill(plugin-dev:command-development)
6agent-development2Create agents (if has-agents)Skill(plugin-dev:agent-development)
7code-hardcode-audit3Quality auditSkill(itp:code-hardcode-audit)
8plugin-validator3Silent failure auditSkill(plugin-dev:plugin-validator)
9release-full4Run the repo's release pipelinemoon run repo:release-full

Skills EXCLUDED (Redundant)

SkillReason Excluded
plugin-dev:skill-developmentUse skill-architecture instead (3x more comprehensive)
plugin-dev:plugin-settingsMerged into hook-development

Agents Spawned

PhaseAgentPurposeInvocation
2skill-reviewerReview skill qualityTask(plugin-dev:skill-reviewer)
3plugin-validatorValidate final structureTask(plugin-dev:plugin-validator)

File Locations

ArtifactPathNotes
Plugin Directoryplugins/{name}/Main plugin folder
Plugin Manifestplugins/{name}/plugin.jsonRequired manifest
Plugin READMEplugins/{name}/README.mdDocumentation
Marketplace JSON.claude-plugin/marketplace.jsonMust add plugin entry
ADRdocs/adr/YYYY-MM-DD-{name}.mdCreated by preflight skill
Design Specdocs/design/YYYY-MM-DD-{name}/spec.mdCreated by preflight skill

Phase 0: Discovery & Validation

Detect marketplace root, gather plugin name/category/components via interactive prompts, confirm the plugin does not already exist.

Detailed steps: Phase 0 Reference

Phase 0 Gate

  • [ ] Marketplace root detected (.claude-plugin/marketplace.json exists)
  • [ ] Plugin name collected (kebab-case, no spaces)
  • [ ] Category selected
  • [ ] Components selected (skills/hooks/commands/agents)
  • [ ] Plugin directory does NOT exist
  • [ ] Plugin NOT in marketplace.json

Phase 1: Scaffold Plugin

  1. Invoke `Skill(plugin-dev:plugin-structure)` -- directory & manifest patterns
  2. Create plugin directory with component subdirs based on user selections
  3. Generate `plugin.json` using marketplace version
  4. Invoke `Skill(itp:implement-plan-preflight)` -- creates ADR + Design Spec + diagrams

Detailed steps: Phase 1 Reference

Phase 1 Gate

  • [ ] Plugin directory exists: plugins/$PLUGIN_NAME/
  • [ ] plugin.json created with marketplace version
  • [ ] ADR exists: docs/adr/$ADR_ID.md
  • [ ] Design spec exists: docs/design/$ADR_ID/spec.md
  • [ ] Both diagrams in ADR (Before/After + Architecture)

Phase 2: Component Creation (Conditional)

Execute ONLY the skills for components the user selected:

ComponentSkill InvocationThen
SkillsSkill(plugin-dev:skill-architecture)Spawn Task(plugin-dev:skill-reviewer)
HooksSkill(plugin-dev:hook-development)--
CommandsSkill(plugin-dev:command-development)--
AgentsSkill(plugin-dev:agent-development)--

Detailed steps: Phase 2 Reference

Phase 2 Gate

  • [ ] All selected components created
  • [ ] If skills: skill-reviewer agent completed review
  • [ ] Files follow plugin-dev patterns

Phase 3: Registration & Validation

  1. Add plugin to `marketplace.json` (include hooks field if hooks exist)
  2. Run `node scripts/validate-plugins.mjs` -- expect all-pass
  3. Invoke `Skill(itp:code-hardcode-audit)` -- quality audit
  4. Run silent failure audit on all hook entry points
  5. Spawn `Task(plugin-dev:plugin-validator)` -- structural validation

Detailed steps: Phase 3 Reference

Phase 3 Gate

  • [ ] Plugin added to marketplace.json
  • [ ] validate-plugins.mjs passes
  • [ ] code-hardcode-audit passes
  • [ ] silent-failure-audit passes (no errors)
  • [ ] plugin-validator agent approves

Phase 4: Commit & Release

  1. Stage changes: plugin dir, marketplace.json, ADR, design spec
  2. Conventional commit: feat($PLUGIN_NAME): add plugin for [brief description]
  3. Push to remote
  4. Run `moon run repo:release-full` -- the repo's release pipeline: tag, changelog, GitHub release

Detailed steps: Phase 4 Reference

Phase 4 Success Criteria

  • [ ] All changes committed with conventional commit
  • [ ] Pushed to remote
  • [ ] semantic-release completed
  • [ ] New version tag created
  • [ ] GitHub release published

Troubleshooting

See Troubleshooting Reference for common issues and fixes.

Post-Execution Reflection

After this skill completes, reflect before closing the task:

  1. Locate yourself. — Find this SKILL.md's canonical path (Glob for this skill's name) before editing. All corrections target THIS file and its sibling references/ — never other documentation.
  2. What failed? — Fix the instruction that caused it. If it could recur, add it as an anti-pattern.
  3. What worked better than expected? — Promote it to recommended practice. Document why.
  4. What drifted? — Any script, reference, or external dependency that no longer matches reality gets fixed now.
  5. Log it. — Every change gets an evolution-log entry with trigger, fix, and evidence.

Do NOT defer. The next invocation inherits whatever you leave behind.



du même dépôt

Autres Skills

Tous les Skills
terrylica
Communauté

academic-pdf-to-gfm

Convert academic PDF papers to GitHub-renderable GFM markdown with math equations. TRIGGERS - PDF, GitHub markdown, math

Installations / 1h
1
GitHub Stars
2
Mis à jour
5 nov.
terrylica
Communauté

adr-code-traceability

Add ADR references to code for traceability. TRIGGERS - ADR traceability, code reference, document decision in code.

Installations / 1h
1
GitHub Stars
2
Mis à jour
5 nov.
terrylica
Communauté

arxiv-source-first-paper-ingest

Read an arXiv paper faithfully by fetching the authors' own LaTeX source instead of OCR-ing the PDF. Extracts every display equation with its label, environment and enclosing proposition, renders each to MathML, and proves usability by compiling each formula with a real TeX engine. Use when you need a paper's formulas exactly — to replicate a method, implement a loss function or custom objective, verify a quoted number, or check a claim against what the authors actually wrote. TRIGGERS - read th

Installations / 1h
1
GitHub Stars
2
Mis à jour
5 nov.
terrylica
Communauté

azure-provision

Bootstrap Azure automation when interactive az login is blocked by a Conditional Access policy (error 530035, "Device state: Unregistered"). Mints a service principal through the Azure Portal session ONCE — using Microsoft Graph over a captured token, not DOM clicking — then provisions resource groups, Cognitive Services / AI Language / Speech resources and their keys entirely via az/REST, writing key AND endpoint together into the SCS vault. Use when az login fails but the portal works, when mo

Installations / 1h
1
GitHub Stars
2
Mis à jour
5 nov.