Loading...
Loading...
Found 1,985 Skills
/cs:onboard — Founder interview that populates ~/.claude/company-context.md. The first command to run when starting with c-level-agents.
Create editorial-quality diagrams in HTML + SVG matching your brand — architecture, flowcharts, sequences, timelines, quadrants, and 9 more types.
What's blocking close — maintain the closing checklist with status, critical path, and days to close. Self-updating: ingests new items from diligence findings and schedule builds, tracks status, surfaces what's blocking. Use when user says "closing checklist", "what's left to close", "checklist status", "add to the checklist", or on a scheduled status pull.
Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.
This skill should be used when the user asks to "improve a skill", "make this skill better", "add features to a skill", "this skill is missing something", "upgrade my skill", "what's missing from this skill", "the skill doesn't do X", "make this more useful", or wants to improve skill effectiveness rather than structural correctness. Not for structural fixes — use repair-skill. Not for agents.
Use when reviewing how skills performed during a session, when the user wants to analyze skill invocations and identify improvements, or when the user says "skill retro", "review skills", "how did skills do", "improve this skill", or "skill retrospective".
Adaptive multi-agent framework for automated data science tasks with planning, execution, and validation
Guide for creating effective skills. Use when you want to create a new skill (or update an existing skill) that extends an agent with specialized workflows, tool integrations, or repo conventions.
Track calories with Lose It! - log food, track weight, and monitor nutrition goals
Generates professional emails from bullet points or conversation summaries. Use when you need to draft emails quickly with consistent style and tone. Supports multiple tones: formal, casual, technical Supports contexts: status updates, requests, announcements, follow-ups
This skill should be used when checking for naming conflicts between local skills (~/.claude/skills) and plugin-provided skills (~/.claude/plugins). Use to identify duplicate or similarly named skills that may cause inconsistent agent behavior.
Configure and customize skills for your workspace by asking questions and updating skill files with your preferences.