Design agent capability

Skill ImYourBoyRoy/agent-continuity-stack/skills/design-agent-capability

Repository-centered instructions, skills, memory conventions, client adapters, and lifecycle safeguards for consistent work across AI coding agents.

Install

npx -y skills add ImYourBoyRoy/agent-continuity-stack --skill design-agent-capability

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

10 days oldThe repository was created 10 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
0 stars0 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.

What its author says it does

Copied from the file, not written here

Design or consolidate durable agent capabilities: instructions, skills, scripts, integrations, hooks, workflows, subagents, or bundles. Use for repeated workflows or overlap; inventory existing capabilities first.

SKILL.md

3.3 KB, 600 tokens by cl100k_base, as published. Nobody here has run it

Design Agent Capability

Choose the smallest durable artifact that solves a demonstrated repeated problem. This skill chooses and designs the capability type. Once durable instruction files are selected, use maintain-agent-instructions to audit or edit their actual client and repository surfaces.

Inventory first

Inspect applicable:

global and repository instructions
installed and repository-local skills
scripts, CLIs, hooks, and CI enforcement
MCP servers and app connectors
client-specific commands, workflows, and subagents
runbooks and templates

Identify ownership and overlap. Prefer strengthening the current owner over creating another broadly triggered capability.

Choose the artifact

Need	Preferred artifact
One task or temporary constraint	Prompt/thread context
Always-on repository convention	Repository instruction
Reusable on-demand procedure or expertise	Agent Skill
Deterministic repeatable transformation	Script or CLI
External live data or authorized action	MCP/app connector
Mechanical lifecycle enforcement	Hook or CI
Scheduled or chained operation	Client workflow/automation
Isolated delegated role	Client-specific subagent
Multi-capability distribution	Client plugin/bundle

Do not assume every client implements subagents, hooks, plugins, or workflows in the same way. Read references/client-surfaces.md when cross-client support is required.

Design a portable skill

Use the open Agent Skills core: one directory, exact SKILL.md, and YAML name plus description.
Put all trigger information in the description.
Keep the body imperative, focused, and below 500 lines.
Move conditional detail into directly linked references/.
Add scripts only for deterministic work that is repeatedly reimplemented.
Use relative paths within the skill.
Describe capabilities before client-specific tool names; provide adapters and fallbacks when a tool is optional.
Keep exact hosts, paths, credentials, device IDs, repositories, and release commands in repository-local overlays.
Add optional client metadata only in namespaced locations that other hosts can ignore safely.

Define the contract

Specify:

discriminative triggers and non-triggers
required inputs and discovered context
workflow and decision gates
allowed mutations and approval boundaries
tools, optional dependencies, and fallbacks
failure behavior
evidence and output contract
maintenance owner and update source

Validate

Run structural validation.
Scan for personal paths, private hosts, credentials, and client-only assumptions.
Test explicit invocation and representative implicit triggers.
Test a near-miss prompt that should not trigger.
Forward-test on a synthetic repository when behavior is complex.
Confirm instructions do not claim precedence a host does not provide.

Return the inventory, artifact decision, structure, safety boundaries, portability assessment, tests, and installation options.