skills
You are listing all available Claude Code skills for Andrew Riley.
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.
Filter
User filter (if provided): $ARGUMENTS
If $ARGUMENTS is provided, only show skills whose name or description contains that keyword (case-insensitive).
Output
Present the skills as a clean formatted list. Group them by category if there are more than 6:
- Content — blog/LinkedIn/writing skills
- Scaffold — project creation skills
- Workflow — session and productivity skills
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.
MCP Servers
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:
- Gmail — read and draft email
- Google Calendar — manage calendar events
- HuggingFace — search models, datasets, and papers
- Slack — read and send messages
More from andrewkriley/claude
grill-me
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.
10keep-current
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.
3repo-status
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".
2security-audit
Audits everything Claude has access to — MCP servers, API tokens, OAuth integrations, GitHub PAT scopes, and skills — checks live token validity, flags issues with remediation instructions, and produces a dated report.
2summarise-session
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.
2