capability-intake
Skill0 starsChanged 22 days agoMITView on GitHub
Study one newly installed skill, MCP server, plugin, agent pack, hook, integration or tool and document only behaviour required for actual workflows.
In this repository33 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/setup-project-context/templates/CLAUDE.mdCLAUDE.md
- backend-architectureSkill
- build-review-loopSkill
- competitor-market-analysisSkill
- context-auditSkill
- data-analysis-insightsSkill
- data-privacy-securitySkill
- dev-agentsSkill
- dev-patternsSkill
- frontend-system-designSkill
- idea-validatorSkill
- intellectual-property-licensingSkill
- international-legal-researchSkill
- legal-document-drafterSkill
- llm-councilSkill
- make-slidesSkill
- password-authentication-securitySkill
- privacy-data-protection-lawSkill
- project-estimation-planningSkill
- project-startSkill
- rea-researchSkill
- requirements-business-analystSkill
- secrets-credential-managerSkill
- seo-tech-stackSkill
- setup-project-contextSkill
- shopify-ui-auditSkill
- site-incidentSkill
- sop-process-builderSkill
- task-dispatchSkill
- technical-feasibilitySkill
- tech-research-intelligenceSkill
- update-mdSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 12 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈12
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Use this workflow when the user says:
- Distinctive: line 27
Do not automatically register every installation.
- Distinctive: line 28
Do not bulk-read other capabilities.
- Distinctive: line 29
Do not invoke a capability simply to inspect it when its own configuration or documentation is sufficient.
- Distinctive: line 30
Do not modify startup context unless a new permanent universal rule is required.
- Distinctive: line 31
Do not update agent routing unless the capability materially changes delegation policy.
- Distinctive: line 32
Do not add project notes unless a capability is actually required by that project.
- Distinctive: line 33
Do not duplicate automatic hook behaviour.
- Distinctive: line 34
Do not deploy, push, tag, release, merge or commit.
- Very specific: line 42
Read only minimum source required to understand that single capability: its own manifest, config, SKILL.md, README, or directly relevant …
- Distinctive: line 57
When the capability can access databases, project files, client data, analytics records, credentials or external systems:
- Distinctive: line 60
Do not approve automatic cross-project use.
- Distinctive: line 61
Do not add a project dependency unless the project genuinely requires it.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Capability Intake
New capability: $ARGUMENTS
Objective
Study one newly added capability and update only the minimum required documentation when it changes actual workflow, routing, safety or a confirmed project dependency.
Activation Examples
Use this workflow when the user says:
I installed <capability>. Check it.Add this MCP if required.Study this plugin and update the setup if useful.I added a new skill. Keep it only where required.Check this new agent pack.
Restrictions
- Study one new capability at a time.
- Do not automatically register every installation.
- Do not bulk-read other capabilities.
- Do not invoke a capability simply to inspect it when its own configuration or documentation is sufficient.
- Do not modify startup context unless a new permanent universal rule is required.
- Do not update agent routing unless the capability materially changes delegation policy.
- Do not add project notes unless a capability is actually required by that project.
- Do not duplicate automatic hook behaviour.
- Do not deploy, push, tag, release, merge or commit.
Intake Process
- Identify capability type: Skill / MCP server / Plugin / Agent or agent pack / Hook / Integration / Other tool.
- Identify capability scope: Global or user-level / Project-specific / Development-only / Fallback-only / Production-sensitive.
- Read only minimum source required to understand that single capability: its own manifest, config, SKILL.md, README, or directly relevant routing file.
- Determine:
- Exact outcome supported.
- Whether it duplicates an approved workflow.
- Whether it should remain installed but undocumented.
- Whether it is useful on demand.
- Whether it creates a new safety or production risk.
- Whether it changes task dispatch or agent policy.
- Whether it is essential for one project.
- Whether it can access data, databases, private files, analytics, credentials or external systems.
- Whether no documentation change is required.
Data Access Capability Check
When the capability can access databases, project files, client data, analytics records, credentials or external systems:
- Determine whether it can read or modify cross-project data.
- Record a safety note only when it changes real access risk or workflow.
- Do not approve automatic cross-project use.
- Do not add a project dependency unless the project genuinely requires it.
Allowed Decisions
Ignore for Documentation
Capability is installed but does not affect an approved workflow, routing or safety rule. Action: update nothing.
Add as Approved On-Demand Capability
Capability is useful for a defined real global workflow but not every session.
Action: add one concise entry to ~/.claude/capability-registry.md. Do not update global CLAUDE.md.
Add as Project-Specific Dependency
Capability is required only for one project.
Action: add a concise note to <project>/docs/12-MCP.md (MCP/AI tooling), docs/13-INTEGRATIONS.md (third-party service) or docs/06-AGENTS.md (agent/workflow) — unmigrated: context.md. Add a line to <project>/CLAUDE.md only when essential in routine project work.
Update Agent Policy
An agent or delegated capability materially changes actual routing.
Action: add only required policy or routing note to ~/.claude/agent.md. Do not copy full pack documentation.
Update Universal Rule
A permanent rule applies nearly every session.
Action: add one concise rule to ~/.claude/CLAUDE.md (use rarely).
Update Safety or Hook Reference
A new capability changes automatic safety, lifecycle or destructive-action behaviour. Action: record only the required operational note. Do not duplicate automatic behaviour.
Required Response Format
Capability Reviewed
- Name: <capability name>
- Type: <skill / MCP / plugin / agent / hook / integration / tool>
- Scope: <global / project-specific / fallback / production-sensitive>
- Purpose: <one concise line>
Decision
- <Ignore for documentation / Add as on-demand capability / Add to project context / Update agent policy / Update universal rule / Update safety reference>
Reason
- <short factual bullet>
Files Updated
- <file path>: <minimal change made>
Git Summary
- Modified configuration or Markdown files: <file paths or None>
- Application source files modified: None
- Commit created: No
- Push performed: NoDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

