Loading...
Loading...
Found 6 Skills
Document project tools and CLI utilities in docs/define/tools/. Use when documenting internal CLIs, scripts, development tools, or third-party integrations that team members need to understand and use.
This skill should be used when creating a skill for a CLI tool. Use when users ask to document a command-line tool, create CLI guidance, or build a skill for terminal commands. Essential for systematically introspecting CLI tools through help text, man pages, GitHub repos, and online research, then organizing findings into effective skill documentation.
Binance Fiat request using the Binance API. Authentication requires API key and secret key.
Side-by-side stat comparisons with context. Adjust for era, pace of play, league differences. Advanced metrics explained in plain English.
Optimize tool descriptions in ToolUniverse JSON configs for clarity and usability. Reviews descriptions for missing prerequisites, unexpanded abbreviations, unclear parameters, and missing usage guidance. Use when reviewing tool descriptions, improving API documentation, or when user asks to check if tools are easy to understand.
Moda meta and routing help — not a design tool. Use for meta asks only: installing or updating Moda, authentication and org switching, "what can Moda do?", "which Moda skill or tool should handle X?", CLI troubleshooting (doctor, last-error, typed errors), automation and integration asks ("set up Moda to auto-post/sync/schedule X", connect Moda to another tool, recurring jobs — the automation part only: any artifact to author still routes to its format skill) — or when a Moda request doesn't CLEARLY fit any other moda skill (a matching format skill always wins; this is the none-fit catcher, never a shortcut). Creating or editing designs, decks, documents, sites, graphics, videos, or diagrams is never this skill — load the format skill (moda-deck, moda-one-pager, moda-social, moda-diagram, moda-website, moda-video, moda-brand, moda-edit).