Menu
Lists all available Claude Code skills with descriptions and usage hints. Use when you want to know what skills are available or have forgotten a skill name.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Interview the user relentlessly about a plan, idea, or project until a shared understanding is reached. Walks down each branch of the design tree, resolving dependencies between decisions one-by-one. Use when starting something new or when a plan needs rigorous thinking-through.
Draft and publish a LinkedIn post on behalf of the user. Use when the user wants to share something on LinkedIn — a project, an insight, a win, a lesson learned, or a reaction to something in the industry.
Summarises the current working session — what was worked on, what was achieved, what remains, and any blockers. Use at the end of a session or when handing off work.
Sends a short session update message to a Webex room. Searches for the room by name, confirms with the user, then posts a concise paragraph summarising what was worked on. Use at the end of a coding session to share progress with a team or channel.
Audits README.md, CLAUDE.md, and PROFILE.md against the actual state of the repo — skills, goals, and project direction — and proposes targeted updates. Also infers PROFILE.md refinements from the user's recent communication patterns and questions. Run periodically to keep docs in sync with the project.
Checks the sync status of a git repository — local vs remote branches, commits ahead/behind, open PRs, and working tree state. Works across any project. Use when the user asks "what's the status of the repo", "are local and remote in sync", "check the branches", or "what's the state of dev and main".
| name | skills |
| description | Lists all available Claude Code skills with descriptions and usage hints. Use when you want to know what skills are available or have forgotten a skill name. |
| argument-hint | [{"optional":"filter keyword"}] |
You are listing all available Claude Code skills.
Use the Glob tool to find all SKILL.md files under ~/.claude/skills/, then Read each one to extract the name:, description:, and argument-hint: frontmatter fields.
User filter (if provided): $ARGUMENTS
If $ARGUMENTS is provided, only show skills whose name or description contains that keyword (case-insensitive).
Present the skills as a clean formatted list. Group them by category if there are more than 6:
For each skill show:
/name — description
Usage: /name argument-hint (only if argument-hint is present)
If $ARGUMENTS was provided and no skills match, say so and suggest the closest match.
After listing skills, read ~/.claude/settings.json and extract the mcpServers keys. Present a second section titled MCP Servers with two sub-groups:
Local (synced via ~/dev/claude)
For each key in mcpServers, show:
**name** — brief purpose inferred from the server name
Cloud-managed (via claude.ai) Always show these as a fixed list — they are authenticated via claude.ai OAuth and are not in settings.json: