marketplace dev

Other Community

Skill notes

Phase 0: Evidence Intake

Before editing an existing marketplace, collect evidence instead of relying on the default template: Read the current .claude-plugin/marketplace.json. Read this repo's marketplace rules (CLAUDE.md, README install section, changelog). Read official docs for marketplace/plugin path semantics.

Step 1: Discover all skills

For each skill, extract from SKILL.md frontmatter: name — the skill identifier description — the ORIGINAL text, do NOT rewrite or translate

Step 2: Read the repo metadata

VERSION file (if exists) — this becomes metadata.version README.md — understand the project, author info, categories LICENSE — note the license type Git remotes — identify upstream vs fork (git remote -v)

Step 3: Determine categories

Group skills by function. Categories are freeform strings. Good patterns: business-diagnostics, content-creation, thinking-tools, utilities developer-tools, productivity, documentation, security Ask the user to confirm categories if grouping is ambiguous.

Step 4: Choose plugin boundaries

Claude Code has three separate levels: Marketplace name is used for install identity: plugin@marketplace. Plugin name is the slash namespace: /plugin-name:skill-name. Skill name comes from SKILL.md frontmatter when the skill path points to a directory containing SKILL.md directly.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@daymade · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Phase 0: Evidence Intake

Before editing an existing marketplace, collect evidence instead of relying on the default template: Read the current `.claude-plugin/marketplace.json`. Read this repo's marketplace rules (`CLAUDE.md`, README install section, changelog). Read official docs for marketplace/plugin path semantics.

02
Phase 1: Analyze the Target Repo

Phase 1: Analyze the Target Repo

03
Step 1: Discover all skills

For each skill, extract from SKILL.md frontmatter: `name` — the skill identifier `description` — the ORIGINAL text, do NOT rewrite or translate

04
Step 2: Read the repo metadata

`VERSION` file (if exists) — this becomes `metadata.version` `README.md` — understand the project, author info, categories `LICENSE` — note the license type Git remotes — identify upstream vs fork (`git remote -v`)

05
Step 3: Determine categories

Group skills by function. Categories are freeform strings. Good patterns: `business-diagnostics`, `content-creation`, `thinking-tools`, `utilities` `developer-tools`, `productivity`, `documentation`, `security` Ask the user to confirm categories if grouping is ambiguous.

06
Step 4: Choose plugin boundaries

Claude Code has three separate levels: Marketplace name is used for install identity: `plugin@marketplace`. Plugin name is the slash namespace: `/plugin-name:skill-name`. Skill name comes from `SKILL.md` frontmatter when the skill path points to a directory containing `SKILL.md` directly.

07
Phase 2: Create marketplace.json

Phase 2: Create marketplace.json

08
Phase 3: Validate

Phase 3: Validate

09
Step 1: One-shot pre-flight check

Run the bundled validator. It runs four checks in sequence and exits non-zero on any required failure: What it checks: · Check · Failure means 1 · JSON syntax of `.claude-plugin/marketplace.json` · file is not parseable JSON

10
Step 2: Installation test

Step 2: Installation test

11
Step 3: Cache footprint test

After installation or update, inspect the actual cache. This is the only way to confirm `source` produced the intended snapshot: Expected results: Single-skill plugin cache: `SKILL.md` plus its own `scripts/`, `references/`, `assets/` as applicable.

12
Step 4: GitHub installation test (if pushed)

Step 4: GitHub installation test (if pushed)

13
Phase 4: Create PR

Phase 4: Create PR

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.