hushh-consent-mcp
Skill40 starsChanged 5 days agoApache-2.0View on GitHub
Use when operating the Hussh Consent MCP core lifecycle or campaign compatibility tools: search_user_scopes, request_consent, check_consent_status, get_encrypted_scoped_export, and prepare_campaign_context.
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-icon-themeSkill
- iam-consent-governanceSkill
- imagegen-frontend-mobileSkill
- imagegen-frontend-webSkill
- improve-animationsSkill
- industrial-brutalist-uiSkill
- kai-test-account-resetSkill
- less-text-karma-jiSkill
- mcp-developer-surfaceSkill
- 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
11 rules. About 0 are common, 6 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Use this when the question is about what the connector returns right now, not when changing backend consent logic.
- Very specific: line 18
Avoid overlap with backend, mcp-developer-surface, and security-audit.
- Distinctive: line 58
Verify the local host config first if the issue smells like a connector startup failure.
- Distinctive: line 59
When scope search returns no matches, check at least two environments when available before concluding it is an information issue.
- Distinctive: line 64
Default scope search should stay compact and paginated.
- Distinctive: line 65
When auditing PKM parity, compare connector output to the backend metadata route and manifest-backed domain truth for the same user before …
- Distinctive: line 67
If the connector returns empty in multiple environments, treat that as a valid empty response until proven otherwise.
- Very specific: line 71
If the request is still broad or ambiguous, route it back to backend.
- Very specific: line 72
If the task becomes package/docs evolution, hand off to mcp-developer-surface.
- Very specific: line 73
If the task becomes consent-policy or trust-boundary analysis, hand off to security-audit.
- Very specific: line 74
If the task becomes backend API contract work, hand off to backend-api-contracts.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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 Consent MCP Skill
Purpose and Trigger
- Primary scope:
hushh-consent-mcp-ops - Trigger on direct connector tasks against the Hussh Consent MCP surface:
search_user_scopesprepare_campaign_context(Hussh ADK compatibility)request_consentcheck_consent_statusget_encrypted_scoped_export
- Use this when the question is about what the connector returns right now, not when changing backend consent logic.
- Avoid overlap with
backend,mcp-developer-surface, andsecurity-audit.
Coverage and Ownership
- Role:
spoke - Owner family:
backend
Owned repo surfaces:
packages/hushh-mcpconsent-protocol/docs/mcp-setup.md.agents/skills/hushh-consent-mcp
Non-owned surfaces:
backendsecurity-auditdocs-governance
Do Use
- Verifying whether a specific user resolves to any requestable scopes.
- Comparing prod vs UAT connector behavior for the same identifier.
- Debugging connector startup/config mismatches across Codex, Claude Desktop, or other MCP hosts.
- Verifying whether a missing result is a connector/config issue versus an actual empty discovery response.
Do Not Use
- Changing consent scope semantics or IAM policy.
- Broad backend runtime work outside the MCP connector.
- UI-only consent surface work.
Read First
packages/hushh-mcp/README.mdconsent-protocol/docs/mcp-setup.mddocs/operations/coding-agent-mcp.md
Workflow
- Verify the local host config first if the issue smells like a connector startup failure.
- When scope search returns no matches, check at least two environments when available before concluding it is an information issue.
- Distinguish clearly between:
- connector failed to start
- connector connected but returned an empty scope-search result
- environment mismatch between local, UAT, and production
- Default scope search should stay compact and paginated. Deep leaf-path expansion is debug-only.
- When auditing PKM parity, compare connector output to the backend metadata route and manifest-backed domain truth for the same user before concluding discovery is wrong.
- Report only the safe structured connector result before inferring causes; never surface identifiers or tokens.
- If the connector returns empty in multiple environments, treat that as a valid empty response until proven otherwise.
Handoff Rules
- If the request is still broad or ambiguous, route it back to
backend. - If the task becomes package/docs evolution, hand off to
mcp-developer-surface. - If the task becomes consent-policy or trust-boundary analysis, hand off to
security-audit. - If the task becomes backend API contract work, hand off to
backend-api-contracts.
Required Checks
python3 .agents/skills/codex-skill-authoring/scripts/skill_lint.py
./bin/hushh agents audit
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.

