Agent extension standards
Skill nklisch/skilltap/.agents/skills/agent-extension-standards
Current attested Codex, Claude Code, and Agent Skills extension contracts for skilltap. Use when designing, implementing, reviewing, or documenting harness adapters; plugin or marketplace manifests; native plugin lifecycle; skill directories or SKILL.md frontmatter; AGENTS.md/CLAUDE.md bridges; configuration scopes; compatibility transfer; adoption, reconciliation, status, or update behavior.From its SKILL.md
npx -y skills add nklisch/skilltap --skill agent-extension-standardsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.8 KB, 523 tokens by cl100k_base, as published. Nobody here has run it
Agent Extension Standards
Ground extension work in the current research substrate. Do not reuse remembered Claude-only marketplace assumptions or flatten the two harnesses into a generic plugin format.
Load the applicable contract
Read .research/analysis/briefs/current-agent-extension-standards.md before
making an architectural or behavioral decision in this domain.
Load a specialist brief when exact native details matter:
- Codex:
.research/analysis/campaigns/marketplace-standards/specialists/codex.md - Claude Code:
.research/analysis/campaigns/marketplace-standards/specialists/claude.md - Agent Skills:
.research/analysis/campaigns/marketplace-standards/specialists/agent-skills.md
Use attestations under .research/attestation/ for source-direct verification.
Treat specialist briefs and the parent synthesis as analytical guidance, not
primary sources. Never cite .research/.import-holding/ as evidence.
Preserve these boundaries
- Treat a skill as its complete directory with top-level
SKILL.md. Never manage only the Markdown file when sibling resources exist. - Use
.agents/skills/as skilltap's canonical portable placement when the skill is compatible. Create harness-native links or copies through adapters. - Keep Codex and Claude plugin manifests, catalogs, identities, caches, scopes, consent, and update semantics distinct.
- Prefer deterministic native marketplace and plugin operations. Do not mutate a native plugin cache as an installation API.
- Keep
~/AGENTS.mdas skilltap's canonical global instruction file and model~/.codex/AGENTS.mdand~/.claude/CLAUDE.mdas native bridges, including their precedence and divergence hazards. - Separate desired skilltap state, native declared state, and effective installed state.
- Classify transfer as faithful, materializable, partial, or blocked. Surface material consequences for piecewise operation-scoped approval.
- Register only sources selected by the user. Do not add search, browsing, ranking, recommendation, or inventory-discovery behavior.
Check freshness
The authoritative brief is dated 2026-07-10 and carries explicit revisit
triggers. When a decision depends on a native command, schema, path, or lifecycle
that may have changed, verify the current official primary source. If the
contract moved, refresh the .research/ attestations and synthesis before
changing foundation docs or implementation.
What ships with it: 1 file
246 B alongside SKILL.md
agents/
- openai.yaml246 B
Gives 0 of the 12 instructions most memory context skills give in 523 tokens
Counted across 754 of the 1,056 authors here whose files we hold, read 2026-09-06
- Preserve existing content structurein 15 of 754, across 9 files
- Front-load the leading wordin 14 of 754, across 10 files
- Update existing entries instead of duplicatingin 14 of 754, across 7 files
- Keep CLAUDE.md under one hundred linesin 14 of 754, across 12 files
- Read CLAUDE.md at the project rootin 14 of 754
- Keep each meaning in a single source of truthin 12 of 754, across 8 files
- Redact sensitive information before committingin 11 of 754, across 4 files
- Scan for all CLAUDE.md filesin 11 of 754, across 7 files
- Use frontmatter for metadata on filesin 10 of 754, across 3 files
- Repeat user interactions 10 timesin 10 of 754, across 4 files
- Write the CLAUDE.md file into the target folderin 10 of 754, across 8 files
- Use memlab to process snapshotsin 9 of 754, across 3 files
Said here and by no other author read
- Ground extension work in the current research substrate
- Read the current agent extension standards brief
- Load a specialist brief when exact native details matter
- Treat a skill as its complete directory with top-level SKILL md
- Use canonical portable placement when the skill is compatible
- Keep native plugin manifests and update semantics distinct
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.