function-signature-and-parameter-guidance
Design and review caller-facing names and contracts: functions, tools, commands, CLI flags, parameters, config keys, env vars, profiles, event types, and node/edge identifiers. Check names, descriptions, help, docstrings, schemas, defaults, bounds, units, errors, outputs, mutation, and whether values reach behavior. Use when asked to "name a parameter", "parameter naming", "name this tool or command", "choose a flag, option, or config key", "design an options object", "one tool or two", "bool or enum here", "name a profile, field, event, node, or edge", "make names clear and unambiguous", "check ISO, platform, or language naming", "audit CLI/MCP/JSON-Schema help", "define accepted values or defaults", "what should this return on failure", "rename this without breaking callers", "improve an error message", "why did the caller pass the wrong argument", "why did this parameter do nothing", or "red-team these descriptions". Not for local variables, general prose, README copy, release notes, or commits.
Pinned to revision 78cda181b69f, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/function-signature-and-parameter-guidance/SKILL.md
- skills/function-signature-and-parameter-guidance/references/designing-and-reviewing-signatures-and-parameters.md
- skills/function-signature-and-parameter-guidance/references/mcp-specifics.md
- skills/function-signature-and-parameter-guidance/references/sources.md
- skills/function-signature-and-parameter-guidance/scripts/check-schema-descriptions.py
- skills/function-signature-and-parameter-guidance/tests/test_check_schema_descriptions.py
Every link opens the file at its source, pinned to the revision this page describes.