tool-surface-discipline

Solid

The small-front-door principle and what counts as a tool-surface change. Load in /feature step 3, in review, and before editing any tool name, argument, description or tier.

AI & Automation 2,680 stars 366 forks Updated today NOASSERTION

Install

View on GitHub

Quality Score: 81/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
66
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Tool-surface discipline Authority: `docs/standard/STANDARD.md` criterion 4; CLAUDE.md "Tool-description quality", "Codex tool-surface benchmark", "Tier-switch pricing"; `tests/test_schema_budget.py`, `tests/test_counter_surface_stability.py`, `tests/test_description_smells.py`; `scripts/surface_diff.py`. The principle in three sentences: the published `counter` surface is byte-pinned and a reworded description is a full-rate cache write for every user; `core_compact` has a hard token ceiling the tree sits within a few tokens of; a new tool is paid for on every request by every user whether or not they call it. A surface change is ANY of: a tool added, removed or renamed; an argument added, removed or retyped; a description reworded; a tier or profile membership moved; a Counter front-door change; an always-visible control added. `scripts/surface_diff.py` sees names only (`docs/workflows/FINDINGS.md` W-1); descriptions are diffed from `_build_tools_list()` dumps. Every surface change carries: README tool reference, CLAUDE.md Key Files (invariant) or KEY-FILES.md (description), CHANGELOG naming the tool, and `benchmarks/schema_baseline.json` regenerated with the token delta stated (DoD 4). The `schema.core_compact_ceiling` verdict decides whether a description may grow; the answer is usually to trim.

Details

Author
jgravelle
Repository
jgravelle/jcodemunch-mcp
Created
7 months ago
Last Updated
today
Language
Python
License
NOASSERTION

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

forge

Designs Claude Code harness artifacts. One triage ladder picks the right surface (skill, hook, path-scoped rule, CLAUDE.md or AGENTS.md entry, workflow script, subagent, MCP); the stance holds the bar every artifact must clear (a gradeable objective, a gap between the model's default and what the owner wants, and a nameable attention shift; the gap is a new idea or source worth operationalizing, a miscommunication to prevent, or an observed failure); per-surface mechanics live in references. Use for creating, reviewing, or refactoring any of these, for distilling articles or docs into one, for skills that under- or over-trigger, hooks that don't fire or fire too often, bloated CLAUDE.mds, and for deciding which surface a behavior belongs on. Triggers on any work on a skill, hook, rule, CLAUDE.md, AGENTS.md, or workflow orchestration script, including debugging triggering or firing semantics and packaging a /command or plugin.

3 Updated 1 months ago
claudialnathan
AI & Automation Listed

aitk-tooling

Tooling stacks, golden configs, seeds, references, and manifests. Use for stack creation, manifest authoring, or config sync.

2 Updated 2 days ago
erclx
AI & Automation Listed

mcp-tool-surface-review

Review an existing MCP server's tool surface for safety and clarity. Use when auditing tools/list output, third-party MCP installs, or Chinese "审查 MCP 工具", "MCP 安全面", "tools/list 审计". Does NOT teach how to scaffold a new MCP server (use official mcp-builder).

1 Updated 1 months ago
Wanbinyu