mcp-developer-surface
Skill40 starsChanged 3 days agoApache-2.0View on GitHub
Use when changing the Hussh MCP developer surface, @hushh/mcp package behavior, developer API docs, or MCP setup guidance.
In this repository69 other files it gives its agents.
- AGENTS.mdAGENTS.md
- hushh-webapp/AGENTS.mdAGENTS.md
- impeccableSkill
- agent-orchestration-governanceSkill
- analytics-observability-governanceSkill
- animateSkill
- animation-vocabularySkill
- apple-designSkill
- autonomous-rca-governanceSkill
- backend-agents-operonsSkill
- backend-api-contractsSkill
- backend-runtime-governanceSkill
- backendSkill
- brandkitSkill
- client-env-paritySkill
- codex-skill-authoringSkill
- comms-communitySkill
- context-refreshSkill
- contributor-onboardingSkill
- docs-governanceSkill
- emil-design-engSkill
- find-animation-opportunitiesSkill
- founder-brief-curationSkill
- frontend-architectureSkill
- frontend-cache-coherenceSkill
- frontend-design-systemSkill
- frontend-native-surface-mapperSkill
- frontendSkill
- frontend-surface-placementSkill
- future-plannerSkill
- github-contribution-governanceSkill
- hushh-consent-mcpSkill
- hushh-icon-themeSkill
- iam-consent-governanceSkill
- imagegen-frontend-mobileSkill
- imagegen-frontend-webSkill
- improve-animationsSkill
- industrial-brutalist-uiSkill
- kai-test-account-resetSkill
- less-text-karma-jiSkill
- mobile-nativeSkill
- mobile-parity-auditSkill
- mobile-plugin-contractsSkill
- morphy-axSkill
- one-voice-governanceSkill
- oss-license-governanceSkill
- pdf-artifact-generationSkill
- pick-ui-librarySkill
- pkm-upgrade-rehearsalSkill
- planning-boardSkill
- pr-governance-reviewSkill
- profile-uiSkill
- prototypeSkill
- puppy-one-harnessSkill
- quality-contractsSkill
- release-ios-appstoreSkill
- repo-contextSkill
- repo-operationsSkill
- review-animationsSkill
- reviewer-app-testingSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Avoid overlap with backend-api-contracts and security-audit.
- Distinctive: line 51
Treat package behavior, developer docs, and setup guidance as one integrated developer surface.
- Distinctive: line 52
Keep package scripts and printed config surfaces aligned with the documented contract.
- Very specific: line 57
If the request is still broad or ambiguous, route it back to backend.
- Very specific: line 58
If the task becomes general API wire-contract work, use backend-api-contracts.
- Very specific: line 59
If the task becomes security or consent enforcement work, use security-audit.
≈ “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
Hussh MCP Developer Surface Skill
Purpose and Trigger
- Primary scope:
mcp-developer-surface - Trigger on Hussh MCP package behavior, developer API docs, MCP setup guidance, or external developer-surface changes.
- Avoid overlap with
backend-api-contractsandsecurity-audit.
Coverage and Ownership
- Role:
spoke - Owner family:
backend
Owned repo surfaces:
packages/hushh-mcpconsent-protocol/docs/mcp-setup.mdconsent-protocol/docs/reference/developer-api.md
Non-owned surfaces:
backendsecurity-auditdocs-governance
Do Use
@hushh/mcppackage changes.- Developer API docs and MCP setup contract updates.
- External developer-surface routing between package, docs, and backend behavior.
Do Not Use
- Broad backend intake where the correct spoke is still unclear.
- Generic backend runtime or route-placement work.
- Internal-only trust policy changes without a developer-surface impact.
Read First
packages/hushh-mcp/README.mdconsent-protocol/docs/mcp-setup.mdconsent-protocol/docs/reference/developer-api.md
Workflow
- Treat package behavior, developer docs, and setup guidance as one integrated developer surface.
- Keep package scripts and printed config surfaces aligned with the documented contract.
- Route consent-scope and trust-enforcement questions to
security-auditwhen those become the core concern.
Handoff Rules
- If the request is still broad or ambiguous, route it back to
backend. - If the task becomes general API wire-contract work, use
backend-api-contracts. - If the task becomes security or consent enforcement work, use
security-audit.
Required Checks
cd packages/hushh-mcp && npm run docs:check
cd packages/hushh-mcp && npm run print-configDoes 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.

