Read-only Claude Code subagents wired for this repository. Each keeps its behaviour in a harness-agnostic system prompt (action language, model aliases not raw slugs, minimal read-only tools) so the ADR-0004 export adapter can retarget it to Codex / Cursor / other harnesses.
Use before promoting or releasing a skill/plugin, or on demand, to review the marketplace tier for cross-artifact drift — marketplace.json vs each plugin.json, metadata.json vs CHANGELOG vs skill-registry.json versions, and skills that silently duplicate an existing artifact. Complements the per-skill…
Use before a commit or push, or on demand, to scan staged, unstaged, or untracked changes for private or employer work references, non-personal identities, or leaked GitHub / Slack / Linear / GCP identifiers before they enter this public repository. Complements the deterministic scope-guard hook by catching…
Cursor rule "20-skill-authoring" from felipeblassioli/agent-skills, covering skill authoring, required files, skill.md constraints, metadata.json schema and after any skill change.
Before changing a maintained artifact, classify its type and maturity using docs/ADR/ADR-0003-artifact-maturity-model.md and docs/specs/artifact-maintenance-workflow.md.
Experimental Claude routing advice, prompt authoring and prompt review using shared model profiles. Separates placement from capability, preserves selected tiers in handoffs, and checks profile consistency. Routing quality, savings and Codex compatibility are not established.
Takes clustering and architecture check outputs and scores skill overlaps, proposing explicit actions like adding anti-triggers, renaming, or archiving.
Use when investigating a skill system, workflow framework, subagent bundle, Claude-style plugin, or mixed agentic artifact and you need cheap inventory, classification, trigger extraction, and flow evidence before synthesis.
Use when explicitly investigating a skill system, workflow framework, subagent bundle, Claude-style plugin, or mixed agentic artifact to understand its roles, trigger points, flows, and use cases.
Choose the right Cursor surface: skills for knowledge and routing, rules for persistent guidance, subagents for context isolation, hooks for enforcement, and MCP for external capabilities.
Configure MCP servers conservatively: trust the source, keep scope narrow, prefer env interpolation, and treat example config separately from live config.
Use hooks for runtime enforcement and auditing: block dangerous shell commands, protect sensitive file reads, and keep hook behavior easy to understand.
Summarizes the cursor-companion Cursor pack and how its runtime assets relate to repo-root skills. Use after installing cursor-companion or when deciding whether to use pack subagents, rules, hooks, or a separate skill from skill-registry.json.
★not rated 2 1mo agoA57 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: