Author a Code Mode Skill

Turn a mechanically valid CodeModeKit plugin into a useful domain product. The catalog explains what calls exist; infer how people should use them from repository evidence and the user, never from tool names alone.

1. Establish current truth

1. Locate plugin.json, mcp.json, src/server.mjs, package.json, and every immediate skills/*/SKILL.md.
2. Run npm run plugin:sync when the configured sources are available. If it fails, preserve the current generated files and report the connectivity or credential blocker.
3. Read references/catalog-metadata.json and search the narrowest indexed prefix or source declaration file. Use references/tools.d.ts only for cross-source work or when no narrower shard applies. Never edit generated declaration files; CodeModeKit owns them.
4. Inspect project documentation, tests, source configuration, tool descriptions, policy, and existing examples for domain evidence.
5. Read references/discovery.md and create a concise authoring brief. Ask the user only for high-impact facts that cannot be recovered locally. Do not invent organization policy, approval boundaries, or intended users.

Current truth is established when every configured source and runtime skill is accounted for, generated catalog status is known, and the brief separates evidence from unanswered consequential questions.

2. Design around jobs, not inventory

Choose the few user jobs that justify activating this skill. For each one, identify: