| Name | Status | 7d | 30d | Last used | Description |
|---|---|---|---|---|---|
| acsa-stats-update | dead | 0 | 0 | — | > Update the ACSA Website Data spreadsheet with latest passenger data from the ACSA website. Use when the user says "update ACSA website data", "ACSA website da |
| agent-control-room | dead | 0 | 0 | — | Use when turning a Telegram topic into the control room for any named agent (Luci, Iris, Lucienne, etc.). Bootstraps and operates a Hermes cron watcher that man |
| agent-tool-access | dead | 0 | 0 | — | > Reference for configuring tools: frontmatter when creating or editing Claude Code subagent definitions (.claude/agents/*.md). The tools: line is the ONLY acce |
| analyze-past-papers | dead | 0 | 0 | — | Analyze a folder of past exam papers (question papers + memos + answer booklets) and produce an evidence-based exam-frequency analysis showing which sub-topics |
| annotate-this | dead | 0 | 0 | — | Add the Den Annotate click-to-comment button to an HTML page/artifact on request. Use when Elmar says "add the annotate button", "make this annotatable", "I wan |
| asana | dead | 0 | 0 | — | > General-purpose Asana integration for querying projects, tasks, attachments, and comments. Use this skill when the user says "asana", "asana project", "asana |
| auto-skill-evolver | dead | 0 | 0 | — | Reflective-Phase auto-skill creation. Triggered automatically by ~/.claude/hooks/auto-skill-evolver.sh every ~25 tool calls in main interactive sessions. Reads |
| bible-study-session | dead | 0 | 0 | — | Generate a Bible study session for Elmar's BibleVault — pericope-by-pericope, evidence-first, personal-mission framing. Reads tracker.md to pick the next [ ] pe |
| board-cycle-audit | dead | 0 | 0 | — | Cross-report inconsistency audit for FlySafair board pack cycles. Pulls all departmental reports (CEO + CFO + IT + HR + Sales + Legal + Standards + Memorandums) |
| booking-curve | dead | 0 | 0 | — | > Pull FlySafair booking curve data from the Neon PostgreSQL database and save as CSV. Use this skill whenever the user mentions "booking curve", "pull booking |
| brain | dead | 0 | 0 | — | Brain dump capture — auto-classifies natural language into tasks, projects, people, ideas, and decisions in the SecondBrain vault. Use when: /brain, brain dump, |
| browser-automation-hygiene | dead | 0 | 0 | — | > Enforce safe defaults whenever wiring, configuring, auditing, or debugging an agent browser tool (browser-harness, Playwright, chrome-devtools-MCP, browse). T |
| ccgram-messaging | dead | 0 | 0 | — | Inter-agent messaging — check inbox, send messages, discover peers, broadcast, and spawn agents. Use when idle, when you need help from another agent, or when y |
| check-annotations | dead | 0 | 0 | — | Pick up and action Den Annotate review feedback. Use when Elmar says "check annotations", "any annotations", "did I send annotations", "process my markups", "wh |
| claude-in-chrome-troubleshooting | dead | 0 | 0 | — | Diagnose and fix Claude in Chrome MCP extension connectivity issues. Use when mcp__claude-in-chrome__* tools fail, return "Browser extension is not connected", |
| communication-style | dead | 0 | 0 | — | > Elmar's email and communication style guide. Use when drafting emails as Elmar, writing on his behalf, composing replies, or asking how Elmar would phrase som |
| confluence | dead | 0 | 0 | — | > Pull, search, and sync content from Atlassian Confluence spaces. Use this skill when the user mentions Confluence, wiki, knowledge base sync, "update from Con |
| create-study-notes | dead | 0 | 0 | — | Build a research-backed study pack from a textbook + exam-frequency analysis. Produces dual output — (a) NBLM-optimised source markdown to feed into NotebookLM |
| cross-host-skill-port | dead | 0 | 0 | — | > Adapt a Claude Code skill to another provider (Codex / Kimi / Gemini / future), sync identical to all hosts (Mac, Luci, Larry), and smoke-test the harvest con |
| crypto-trade-approval | dead | 0 | 0 | — | Approve or decline pending crypto trades from Telegram. When Elmar messages with /crypto-approve, /crypto-decline, /crypto-pending, or natural language like "ap |
| docx | dead | 0 | 0 | — | Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word doc |
| downloads-triage | dead | 0 | 0 | — | Scan any folder, classify files against the file catalog, review uncertain matches with Claude's intelligence, and move files via interactive dashboard. Trigger |
| excalidraw-diagram | dead | 0 | 0 | — | Create Excalidraw diagram JSON files that make visual arguments. Use when the user wants to visualize workflows, architectures, or concepts. |
| file-catalog | dead | 0 | 0 | — | Scan, maintain, and use Elmar's cross-cloud file catalog and file map for Dropbox, Google Drive, OneDrive Personal, and OneDrive Safair. |
| file-map-update | dead | 0 | 0 | — | Keep the living file-location map current. Trigger whenever Elmar states where a file/folder/info lives ("it's in", "you'll find X at", "X lives in", "saved to" |
| file-search | dead | 0 | 0 | — | Search across all file sources (Dropbox, Google Drive, OneDrive) using the unified file catalog and Gety.ai content search. Find documents, files, and folders b |
| findash-actuals-precedence | dead | 0 | 0 | — | > Guardrail for ANY FlySafair financial output (board pack, monthly forecast, fuel/cost report, dashboard, exco numbers). Before publishing a cost/revenue/PBT f |
| flightaware-data | dead | 0 | 0 | — | > Query FlightAware flight data from the local SQL Server database (actuals and scheduled) and generate capacity reports, market share analysis, or raw data exp |
| gemini-analyze | dead | 0 | 0 | — | > Fallback document analysis using Google Gemini vision for files Claude cannot read natively. Use this skill ONLY when Claude's Read tool fails on a file — sca |
| gemini-api-dev | dead | 0 | 0 | — | Use this skill when building applications with Gemini models, Gemini API, working with multimodal content (text, images, audio, video), implementing function ca |
| gemini-interactions-api | dead | 0 | 0 | — | Use this skill when writing code that calls the Gemini API for text generation, multi-turn chat, multimodal understanding, image generation, streaming responses |
| gemini-live-api-dev | dead | 0 | 0 | — | Use this skill when building real-time, bidirectional streaming applications with the Gemini Live API. Covers WebSocket-based audio/video/text streaming, voice |
| gemini-transcribe | dead | 0 | 0 | — | > Transcribe audio files using Google Gemini with speaker diarization, multi-language support, and multiple output formats. Use when: transcribing audio, speech |
| google-drive | dead | 0 | 0 | — | > Google Drive API v3 client for file management, search, upload, download, sharing, and folder operations. Use when: accessing Google Drive files, uploading to |
| google-gemini-api | dead | 0 | 0 | — | Google Gemini API with @google/genai SDK. Use for multimodal AI, thinking mode, function calling, or encountering SDK deprecation warnings, context errors, mult |
| google-gemini-file-search | dead | 0 | 0 | — | Google Gemini File Search for managed RAG with 100+ file formats. Use for document Q&A, knowledge bases, or encountering immutability errors, quota issues, poll |
| graphify | dead | 0 | 0 | — | any input (code, docs, papers, images) - knowledge graph - clustered communities - HTML + JSON + audit report |
| guide-builder | dead | 0 | 0 | — | > Turns any source — URL, Reddit thread, blog post, YouTube video, pasted text — into an interactive step-by-step HTML implementation guide with checkboxes, pro |
| iata-fuel-update | dead | 0 | 0 | — | > Extracts the latest jet fuel price data from the IATA Fuel Price Monitor webpage and updates the Data Fuel.xlsx spreadsheet. Use this skill whenever the user |
| inbox-assist | dead | 0 | 0 | — | > Interactive email assistant that scans Gmail and MS365 Outlook, shows you a list of emails where Claude can help, and then does the full work on whichever one |
| json-canvas | dead | 0 | 0 | — | Create and edit JSON Canvas files (.canvas) with nodes, edges, groups, and connections. Use when working with .canvas files, creating visual canvases, mind maps |
| kyc-extract | dead | 0 | 0 | — | Extract KYC fields from South African identity documents (passports, ID cards, unabridged birth certificates) via Claude's native vision. Reads scan, extracts f |
| luci | dead | 0 | 0 | — | > Dispatch work to Luci — your always-on cloud server. Use this skill whenever you need to run something in the background, schedule a recurring task, check on |
| luci-notify | dead | 0 | 0 | — | How to send Telegram messages from any Luci context — scheduled tasks, worker sessions, scripts. ALWAYS route via ~/workspace/notify.py — never via plugin:teleg |
| make-com | dead | 0 | 0 | — | Make.com (Integromat) automation platform — create, edit, run, and manage scenarios via REST API. Use this skill whenever the user mentions Make.com, automation |
| mastering-github-cli | dead | 0 | 0 | — | | GitHub CLI (gh) command reference for repository search, code discovery, CI/CD monitoring, workflow authoring, and automation. Triggers on "gh" commands, "git |
| medical-research-brief | dead | 0 | 0 | — | Research drugs, treatments, supplements, or medical conditions against a family member's vault medical context (labs, conditions, current meds) and produce a st |
| meeting-notes | dead | 0 | 0 | — | Process audio recordings or existing transcripts into structured meeting notes with calendar context, email context, speaker identification, project matching, a |
| memory-manager | dead | 0 | 0 | — | > Memory retrieval discipline. Before claiming something doesn't exist in our setup, hasn't been discussed, or is unknown — check stored memory first. Triggers |
| munger | dead | 0 | 0 | — | Run a decision, proposal, or strategy through Charlie Munger's mental models — 25 cognitive biases, inversion, latticework of models, two-track analysis. Use wh |
| officecli | dead | 0 | 0 | — | Create, analyze, proofread, and modify Office documents (.docx, .xlsx, .pptx) using the officecli CLI tool. Use when the user wants to create, inspect, check fo |
| openrouter-free-model-rotator | dead | 0 | 0 | — | Use when operating the PKA script that finds, tests, ranks, and optionally applies free OpenRouter models to a Hermes Free Model Test Profile. Covers safe dry-r |
| dead | 0 | 0 | — | Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple P | |
| pka-dashboard-publish | dead | 0 | 0 | — | Register a report or dashboard HTML on the PKA dashboard (port 8787). Use when Elmar says "add it to the PKA dashboard", "put this on the dashboard", "register |
| playwright-form-reverse-engineer | dead | 0 | 0 | — | Reverse-engineer and automate any web form using Playwright when no API exists. Use for "automate this form", "build a submitter for", "I need to fill out X sit |
| pptx | dead | 0 | 0 | — | Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; rea |
| premortem | dead | 0 | 0 | — | Run a Kahneman-style pre-mortem on any plan, decision, strategy, or proposal. Trigger when the user says "premortem this", "premortem", "stress-test this plan", |
| ralph | dead | 0 | 0 | — | > Autonomous development loop (Ralph Wiggum pattern) — runs Claude Code headless in a loop against a PRD until all tasks are complete. Helps write the PRD, laun |
| regression | dead | 0 | 0 | — | > Use when fixing any bug — writes a failing regression test before touching the fix, registers the bug so Larry can monitor it nightly, and prevents silent re- |
| safair-dashboard | dead | 0 | 0 | — | > Builds and modifies the FlySafair CEO HTML dashboard — an interactive, self-contained report with charts, tables, and KPIs covering network performance, route |
| search-brain | dead | 0 | 0 | — | Search the SecondBrain via wiki-first direct read + vault.db FTS5 keyword search. GBrain retired 2026-05-01. Triggers: search brain, search secondbrain, search |
| self-improve | dead | 0 | 0 | — | > Unified self-improvement skill — scans session transcripts for unsaved learnings, corrections, friction, and repeated patterns, then proposes saves to memory, |
| skill-eval | dead | 0 | 0 | — | > Behavior eval harness for Claude Code skills. Runs scenarios against a skill, scores binary asserts + LLM rubric, tracks history. Companion to skill-creator ( |
| skill-evolver | dead | 0 | 0 | — | Automatically detects repeatable patterns in the current session and creates or improves existing skills. Use when the user says "evolve skills", "create a skil |
| skill-suggester | dead | 0 | 0 | — | UserPromptSubmit hook that scans every user prompt against active SKILL.md descriptions and surfaces up to 3 high-scoring matches as additional context. Reduces |
| skill-sync | dead | 0 | 0 | — | > Audit and maintain parity between Claude and Codex skills. Use when a user says "sync skills", "compare Claude and Codex skills", "what skills are on Claude b |
| sources-sync | dead | 0 | 0 | — | Keep arbitrary Dropbox/OneDrive folders in sync with SecondBrain as markdown. Triggers on "sync sources", "ingest folder", "add watched folder", "watch folder", |
| study-help | dead | 0 | 0 | — | Show the study tutor help menu — cheat sheet, Gemini API key setup, first-run wizards, troubleshoot, and version info. Triggers on "/study-help", "help", "what |
| study-pipeline | dead | 0 | 0 | — | End-to-end interactive orchestrator for building a complete study pack from a handbook + past papers. Asks the user step-by-step what subject, where the handboo |
| study-troubleshoot | dead | 0 | 0 | — | Bundle study tutor logs into a zip the student can send to Dad for debugging. Triggers on "/study-troubleshoot", "send debug to dad", "something broke", "help m |
| subagent-dev | dead | 0 | 0 | — | > Execute an implementation plan by dispatching fresh subagents per task with two-stage review (spec compliance → code quality). Use for 2+ independent tasks in |
| telegram-mode | dead | 0 | 0 | — | Adjust output formatting when Elmar is reading on Telegram. Activate on "I'm on telegram", "tg mode", "format for telegram", "format for tg", "phone mode", "I'm |
| test-evolver | dead | 0 | 0 | — | Test skill to verify if skill-evolver name is blocked. |
| tv-status | dead | 0 | 0 | — | Show current trading workflow state — bias age, setup details, active watches, recent trade log. Trigger when user says "status", "what's the status", "where ar |
| url-library-sync | dead | 0 | 0 | — | Scan Claude Code session transcripts for URLs Elmar analyzed, auto-research them via defuddle + LLM, create MD files in docs/url-library/, update the HTML catal |
| vertex-ai-api-dev | dead | 0 | 0 | — | Guides the usage of Gemini API on Google Cloud Vertex AI with the Gen AI SDK. Use when the user asks about using Gemini in an enterprise environment or explicit |
| video-to-document | dead | 0 | 0 | — | Convert a video of someone paging through a printed book, handbook, textbook, document, or study notes into a faithful markdown reconstruction with text AND emb |
| webscraping-api | dead | 0 | 0 | — | > Web scraping through WebScrapingAPI.com — bypasses anti-bot protection, CAPTCHAs, IP blocks. Use this skill when you need to scrape a website that blocks norm |
| wiki-ingest | dead | 0 | 0 | — | Ingest documents (PDF, DOCX, XLSX, etc.) into SecondBrain — convert to markdown via convert_to_md.py, index in vault.db, and add to LightRAG semantic index. Tri |
| wiki-lint | dead | 0 | 0 | — | Health-check both wikis for broken links, orphans, contradictions, stale content, and missing coverage. Triggers on "wiki lint", "check wiki health", "wiki heal |
| wiki-query | dead | 0 | 0 | — | Search and synthesize answers from the SecondBrain + PKA system wiki via direct file read + vault.db FTS5 keyword search. Triggers on "wiki query", "search wiki |
| xlsx | dead | 0 | 0 | — | Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xl |
| youtube-analyzer | dead | 0 | 0 | — | > Watch and analyze YouTube videos using Google Gemini's vision — see code on screen, extract steps from tutorials, summarize content, answer questions about sp |
| luci-larry-context | going-silent | 0 | 3 | 2026-05-16 | Load verified infrastructure context for PKA team — Luci (Hetzner server, Project Manager), Larry (LegalMind developer agent on Coolify), and how they connect t |
| m365 | going-silent | 0 | 2 | 2026-05-09 | > Microsoft 365 integration for Outlook email, calendar, Teams, OneDrive, and tasks. Use when: sending Outlook email, reading work email, searching Outlook, cre |
| notebooklm | going-silent | 0 | 2 | 2026-05-09 | > Google NotebookLM integration — create notebooks, add sources (YouTube URLs, web pages, local files, entire folders), generate studio artifacts (audio podcast |
| ai-backends | going-silent | 0 | 1 | 2026-05-09 | > Unified reference for ALL AI backends available in PKA — Claude, Codex, Gemini, Kimi, GLM, MiniMax. Covers CLI binaries (OAuth-based), API endpoints (key-base |
| compound | going-silent | 0 | 1 | 2026-05-12 | > Document a recently solved problem to compound team knowledge. Write a structured solution doc while context is fresh. Single-pass, lean — no subagents, no ce |
| safair-data | going-silent | 0 | 1 | 2026-05-07 | > FlySafair airline data dictionary and extraction skill. The single source of truth for all FlySafair operational, commercial, and market data — file locations |
| wiki-compiler | going-silent | 0 | 1 | 2026-05-06 | Compile SecondBrain raw notes into synthesized wiki pages. Triggers on "wiki compile", "compile wiki", "update wiki", "recompile wiki", "compile Project X", "up |
| wiki-refresh | going-silent | 0 | 1 | 2026-05-06 | > Refresh selected SecondBrain wiki pages without requiring command-line flags. Use when the user says "refresh wiki", "update wiki", "refresh the wiki for X", |
| dev-loop | active | 141 | 540 | 2026-06-01 | > Universal development skill for ALL MC tickets and code tasks. Classifies the problem into Tier 1/2/3 and runs the appropriate dev loop — from one-shot fix to |
| deep-research | active | 18 | 41 | 2026-05-31 | > Comprehensive research skill for Claude Code. Use this skill whenever the user wants to research a topic, investigate how to build something, find best practi |
| second-opinion | active | 1 | 29 | 2026-05-28 | Get a second opinion from another AI (Codex, Gemini, Kimi, Minimax, GLM, Opus) when debugging hits a wall, or run the full council for architecture reviews. Tri |
| playwright | active | 0 | 7 | 2026-05-18 | Browser automation and E2E testing with Playwright CLI or agent-browser. Auto-detects dev servers, writes clean test scripts. Test pages, fill forms, take scree |
| defuddle | active | 0 | 5 | 2026-05-21 | Extract clean markdown content from web pages using Defuddle CLI, removing clutter and navigation to save tokens. Use instead of WebFetch when the user provides |
| research-brief | active | 2 | 5 | 2026-05-31 | End-to-end research pipeline — seed sources → NotebookLM Deep Research → gap analysis → iterate → generate audio overview + slide deck + briefing report. Use wh |
| x-search | active | 0 | 5 | 2026-05-22 | > Search X (Twitter) posts and fetch single-post content using Grok (xAI) live search as primary and ScrapeCreators as fallback. Use this skill when you need to |
| home-assistant | active | 0 | 4 | 2026-05-23 | Control and configure Home Assistant devices, automations, dashboards, and config files. Use for lights, speakers, climate, switches, automations, helpers, and |
| f1-predictor-ops | active | 0 | 2 | 2026-05-22 | Operate the F1 prediction pipeline on Luci — run forecast, submit picks to Superbru, score race results, view predictions, run as-if scenarios. Triggers on "run |
| provider-switch | active | 0 | 2 | 2026-05-22 | > Switch Claude Code between Anthropic, Z.AI GLM, and MiniMax on Luci. If the user asks for Kimi, explain that Kimi Coding is a separate direct API helper, not |
| email-calendar | active | 0 | 1 | 2026-05-19 | > Email and calendar operations — reading, sending, searching, creating, updating, deleting events or emails across Outlook and Google. Use when user says "find |
| radio-show | active | 1 | 1 | 2026-05-25 | Recurring news and research audio episodes across Elmar's standing interests — aviation, SA business/macro, geopolitics, crypto, AI, markets, F1, padel. Produce |
| spotify | active | 0 | 1 | 2026-05-23 | | Spotify integration — manage playlists, search music, get recommendations, control playback, and explore listening history via natural language. Use when: "sp |
| whats-up | active | 0 | 1 | 2026-05-19 | Orchestrator continuity / status synthesis. Answers "what's up?", "status", "where are we", "what's outstanding", "what's next", "catch me up", "what are we wor |
| youtube-scraper | active | 1 | 1 | 2026-05-31 | > YouTube video search and metadata extraction using yt-dlp. Use this skill whenever the user wants to search YouTube, find videos about a topic, extract video |
| code-review | retired | 0 | 1 | 2026-05-12 | Code review practices with technical rigor and verification gates. Use for receiving feedback, requesting code-reviewer subagent reviews, or preventing false co |
| ask-questions-if-underspecified | retired | 0 | 0 | — | Clarify requirements before implementing. Use when serious doubts arise. |
| brainstorming | retired | 0 | 0 | — | You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirem |
| brand-guidelines | retired | 0 | 0 | — | Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand color |
| canvas-design | retired | 0 | 0 | — | Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, d |
| database-schema-design | retired | 0 | 0 | — | Database schema design for PostgreSQL/MySQL with normalization, relationships, constraints. Use for new databases, schema reviews, migrations, or encountering m |
| design-review | retired | 0 | 0 | — | 7-phase frontend design review with accessibility (WCAG 2.1 AA), responsive testing, visual polish. Use for PR reviews, UI audits, or encountering contrast issu |
| dispatching-parallel-agents | retired | 0 | 0 | — | Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies |
| doc-coauthoring | retired | 0 | 0 | — | Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, |
| email-to-project | retired | 0 | 0 | — | > Process Outlook emails, classify into projects, update SecondBrain project status. Triggers: email to project, process emails, classify emails, email project |
| executing-plans | retired | 0 | 0 | — | Use when you have a written implementation plan to execute in a separate session with review checkpoints |
| feature-dev | retired | 0 | 0 | — | Automate 7-phase feature development with specialized agents (code-explorer, code-architect, code-reviewer). Use for multi-file features, architectural decision |
| frontend-design | retired | 0 | 0 | — | Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applicat |
| git-cleanup | retired | 0 | 0 | — | Safely analyzes and cleans up local git branches and worktrees by categorizing them as merged, squash-merged, superseded, or active work. |
| insecure-defaults | retired | 0 | 0 | — | Detects fail-open insecure defaults (hardcoded secrets, weak auth, permissive security) that allow apps to run insecurely in production. Use when auditing secur |
| interaction-design | retired | 0 | 0 | — | Creates intuitive user experiences through feedback patterns, microinteractions, and accessible interaction design. Use when designing loading states, error han |
| internal-comms | retired | 0 | 0 | — | A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever |
| kaizen-improvement | retired | 0 | 0 | — | Transform transcript analysis findings into actionable improvements. Triggers on "generate hooks from findings", "improve agent", "fix anti-pattern", "kaizen im |
| mastering-postgresql | retired | 0 | 0 | — | PostgreSQL development for Python with full-text search (tsvector, tsquery, BM25 via pg_search), vector similarity (pgvector with HNSW/IVFFlat), JSONB and array |
| mastering-typescript | retired | 0 | 0 | — | | Master enterprise-grade TypeScript development with type-safe patterns, modern tooling, and framework integration. This skill provides comprehensive guidance |
| mcp-builder | retired | 0 | 0 | — | Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when b |
| meta-inspector | retired | 0 | 0 | — | Extract specific data points from agent output transcripts, kaizen analysis reports, and JSONL session files without loading raw data into orchestrator context. |
| monthly-audit | retired | 0 | 0 | — | Monthly deep audit — Kaizen process mining, full CLAUDE.md grade, monthly-review.md, proposal rollover. Trigger on: /monthly-audit, "run monthly audit", "do the |
| oauth-implementation | retired | 0 | 0 | — | OAuth 2.0 and OpenID Connect authentication with secure flows. Use for third-party integrations, SSO systems, token-based API access, or encountering authorizat |
| project-memory | retired | 0 | 0 | — | Maintain persistent project memory files across sessions. Use when starting a new project session, when key decisions are made, when bugs are found and fixed, o |
| radixx-api | retired | 0 | 0 | — | > FlySafair Radixx ConnectPoint API knowledge base — SOAP API for OTA integration, booking flows, departure control (Ink/RadixxGo), seat management, SSR codes, |
| receiving-code-review | retired | 0 | 0 | — | Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical |
| requesting-code-review | retired | 0 | 0 | — | Use when completing tasks, implementing major features, or before merging to verify work meets requirements |
| responsive-web-design | retired | 0 | 0 | — | Builds adaptive web interfaces using Flexbox, CSS Grid, and media queries with a mobile-first approach. Use when creating multi-device layouts, implementing fle |
| rest-api-design | retired | 0 | 0 | — | Designs RESTful APIs with proper resource naming, HTTP methods, status codes, and response formats. Use when building new APIs, establishing API conventions, or |
| review-proposals | retired | 0 | 0 | — | Review and action pending CLAUDE.md improvement proposals from weekly-improvements.md. |
| root-cause-tracing | retired | 0 | 0 | — | Systematically trace bugs backward through call stack to find original trigger. Use when errors occur deep in execution and you need to trace back to find the o |
| sequential-thinking | retired | 0 | 0 | — | Systematic step-by-step reasoning with revision and branching. Use for complex problems, multi-stage analysis, design planning, problem decomposition, or encoun |
| session-logger | retired | 0 | 0 | — | Log all session activity to a timestamped log file. Use automatically at the start of every session, and when the user says "log this session", "start logging", |
| skill-creator | retired | 0 | 0 | — | Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an |
| slack-gif-creator | retired | 0 | 0 | — | Knowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request a |
| subagent-driven-development | retired | 0 | 0 | — | Use when executing implementation plans with independent tasks in the current session |
| systematic-debugging | retired | 0 | 0 | — | Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions. Use when encountering any bug, test failu |
| tailwind-v4-shadcn | retired | 0 | 0 | — | | Production-tested setup for Tailwind CSS v4 with shadcn/ui, Vite, and React. Use when: initializing React projects with Tailwind v4, setting up shadcn/ui, imp |
| technical-specification | retired | 0 | 0 | — | Creates detailed technical specifications for software projects covering requirements, architecture, APIs, and testing strategies. Use when planning features, d |
| template-skill | retired | 0 | 0 | — | Replace with description of the skill and when Claude should use it. |
| test-driven-development | retired | 0 | 0 | — | Use when implementing any feature or bugfix, before writing implementation code |
| test-quality-analysis | retired | 0 | 0 | — | Detect test smells, overmocking, flaky tests, and coverage issues. Analyze test effectiveness, maintainability, and reliability. Use when reviewing tests or imp |
| theme-factory | retired | 0 | 0 | — | Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fo |
| transcript-analysis | retired | 0 | 0 | — | This skill should be used when analyzing Claude Code session transcripts, reviewing agent performance, finding anti-patterns or tool misuse, detecting user frus |
| using-gh-cli | retired | 0 | 0 | — | Guides usage of the GitHub CLI (gh) for interacting with GitHub repositories, PRs, issues, and API. Use when working with GitHub resources instead of WebFetch o |
| verification-before-completion | retired | 0 | 0 | — | Run verification commands and confirm output before claiming success. Use when about to claim work is complete, fixed, or passing, before committing or creating |
| vitest-testing | retired | 0 | 0 | — | Modern TypeScript/JavaScript testing with Vitest. Fast unit and integration tests, native ESM support, Vite-powered HMR, and comprehensive mocking. Use for test |
| web-artifacts-builder | retired | 0 | 0 | — | Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for |
| web-performance-audit | retired | 0 | 0 | — | Web performance audits with Core Web Vitals, bottleneck identification, optimization recommendations. Use for page load times, performance reviews, UX optimizat |
| webapp-testing | retired | 0 | 0 | — | Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing br |
| writing-plans | retired | 0 | 0 | — | Use when you have a spec or requirements for a multi-step task, before touching code |
| zod | retired | 0 | 0 | — | TypeScript-first schema validation and type inference. Use for validating API requests/responses, form data, env vars, configs, defining type-safe schemas with |
User messages containing a skill's trigger phrases where the skill was not invoked in the same session. Some are legitimate (the skill was not appropriate), but recurring near-misses are signal that the skill is "invisible".
| Skill | Phrase | Message | When |
|---|---|---|---|
| spotify | queue | # Control Room direct worker prompt — MC-4449 You are a direct external builder launched by Luci Control Room. You are **not** running via legacy `mc_pickup.py`; do not invoke `mc_pickup.py`, `ticket-pickup`, or `needs- | 2026-05-30 08:04 |
| whats-up | what's next | --- MODE SWITCH: PROGRESS SUMMARY --- ⚠️ CRITICAL TAG REQUIREMENT — READ CAREFULLY: • You MUST wrap your ENTIRE response in <summary>...</summary> tags. • Do NOT use <observation> tags. <observation> output will be DISCA | 2026-05-26 19:20 |
| whats-up | what's next | --- MODE SWITCH: PROGRESS SUMMARY --- ⚠️ CRITICAL TAG REQUIREMENT — READ CAREFULLY: • You MUST wrap your ENTIRE response in <summary>...</summary> tags. • Do NOT use <observation> tags. <observation> output will be DISCA | 2026-05-26 07:07 |
| whats-up | what's next | --- MODE SWITCH: PROGRESS SUMMARY --- ⚠️ CRITICAL TAG REQUIREMENT — READ CAREFULLY: • You MUST wrap your ENTIRE response in <summary>...</summary> tags. • Do NOT use <observation> tags. <observation> output will be DISCA | 2026-05-27 20:05 |
| whats-up | what's next | --- MODE SWITCH: PROGRESS SUMMARY --- ⚠️ CRITICAL TAG REQUIREMENT — READ CAREFULLY: • You MUST wrap your ENTIRE response in <summary>...</summary> tags. • Do NOT use <observation> tags. <observation> output will be DISCA | 2026-05-31 05:01 |
| whats-up | what's next | --- MODE SWITCH: PROGRESS SUMMARY --- ⚠️ CRITICAL TAG REQUIREMENT — READ CAREFULLY: • You MUST wrap your ENTIRE response in <summary>...</summary> tags. • Do NOT use <observation> tags. <observation> output will be DISCA | 2026-06-01 06:12 |
| whats-up | what's next | --- MODE SWITCH: PROGRESS SUMMARY --- ⚠️ CRITICAL TAG REQUIREMENT — READ CAREFULLY: • You MUST wrap your ENTIRE response in <summary>...</summary> tags. • Do NOT use <observation> tags. <observation> output will be DISCA | 2026-05-29 00:12 |
| whats-up | what's next | --- MODE SWITCH: PROGRESS SUMMARY --- ⚠️ CRITICAL TAG REQUIREMENT — READ CAREFULLY: • You MUST wrap your ENTIRE response in <summary>...</summary> tags. • Do NOT use <observation> tags. <observation> output will be DISCA | 2026-05-31 06:28 |
| whats-up | what's next | --- MODE SWITCH: PROGRESS SUMMARY --- ⚠️ CRITICAL TAG REQUIREMENT — READ CAREFULLY: • You MUST wrap your ENTIRE response in <summary>...</summary> tags. • Do NOT use <observation> tags. <observation> output will be DISCA | 2026-06-01 00:11 |
| whats-up | what's next | --- MODE SWITCH: PROGRESS SUMMARY --- ⚠️ CRITICAL TAG REQUIREMENT — READ CAREFULLY: • You MUST wrap your ENTIRE response in <summary>...</summary> tags. • Do NOT use <observation> tags. <observation> output will be DISCA | 2026-05-30 03:08 |
| whats-up | what's next | --- MODE SWITCH: PROGRESS SUMMARY --- ⚠️ CRITICAL TAG REQUIREMENT — READ CAREFULLY: • You MUST wrap your ENTIRE response in <summary>...</summary> tags. • Do NOT use <observation> tags. <observation> output will be DISCA | 2026-05-25 18:08 |
| whats-up | what's next | --- MODE SWITCH: PROGRESS SUMMARY --- ⚠️ CRITICAL TAG REQUIREMENT — READ CAREFULLY: • You MUST wrap your ENTIRE response in <summary>...</summary> tags. • Do NOT use <observation> tags. <observation> output will be DISCA | 2026-05-27 05:32 |
| whats-up | what's next | --- MODE SWITCH: PROGRESS SUMMARY --- ⚠️ CRITICAL TAG REQUIREMENT — READ CAREFULLY: • You MUST wrap your ENTIRE response in <summary>...</summary> tags. • Do NOT use <observation> tags. <observation> output will be DISCA | 2026-05-27 05:36 |
| whats-up | what's next | --- MODE SWITCH: PROGRESS SUMMARY --- ⚠️ CRITICAL TAG REQUIREMENT — READ CAREFULLY: • You MUST wrap your ENTIRE response in <summary>...</summary> tags. • Do NOT use <observation> tags. <observation> output will be DISCA | 2026-05-29 15:11 |
| whats-up | what's next | --- MODE SWITCH: PROGRESS SUMMARY --- ⚠️ CRITICAL TAG REQUIREMENT — READ CAREFULLY: • You MUST wrap your ENTIRE response in <summary>...</summary> tags. • Do NOT use <observation> tags. <observation> output will be DISCA | 2026-05-29 10:09 |
| whats-up | what's next | --- MODE SWITCH: PROGRESS SUMMARY --- ⚠️ CRITICAL TAG REQUIREMENT — READ CAREFULLY: • You MUST wrap your ENTIRE response in <summary>...</summary> tags. • Do NOT use <observation> tags. <observation> output will be DISCA | 2026-05-31 09:05 |
| whats-up | what's next | --- MODE SWITCH: PROGRESS SUMMARY --- ⚠️ CRITICAL TAG REQUIREMENT — READ CAREFULLY: • You MUST wrap your ENTIRE response in <summary>...</summary> tags. • Do NOT use <observation> tags. <observation> output will be DISCA | 2026-05-25 19:07 |
| whats-up | what's next | --- MODE SWITCH: PROGRESS SUMMARY --- ⚠️ CRITICAL TAG REQUIREMENT — READ CAREFULLY: • You MUST wrap your ENTIRE response in <summary>...</summary> tags. • Do NOT use <observation> tags. <observation> output will be DISCA | 2026-05-28 14:15 |
| whats-up | what's next | --- MODE SWITCH: PROGRESS SUMMARY --- ⚠️ CRITICAL TAG REQUIREMENT — READ CAREFULLY: • You MUST wrap your ENTIRE response in <summary>...</summary> tags. • Do NOT use <observation> tags. <observation> output will be DISCA | 2026-05-27 01:05 |
| whats-up | what's next | --- MODE SWITCH: PROGRESS SUMMARY --- ⚠️ CRITICAL TAG REQUIREMENT — READ CAREFULLY: • You MUST wrap your ENTIRE response in <summary>...</summary> tags. • Do NOT use <observation> tags. <observation> output will be DISCA | 2026-05-28 05:54 |
| whats-up | what's next | --- MODE SWITCH: PROGRESS SUMMARY --- ⚠️ CRITICAL TAG REQUIREMENT — READ CAREFULLY: • You MUST wrap your ENTIRE response in <summary>...</summary> tags. • Do NOT use <observation> tags. <observation> output will be DISCA | 2026-05-30 17:05 |
| whats-up | what's next | --- MODE SWITCH: PROGRESS SUMMARY --- ⚠️ CRITICAL TAG REQUIREMENT — READ CAREFULLY: • You MUST wrap your ENTIRE response in <summary>...</summary> tags. • Do NOT use <observation> tags. <observation> output will be DISCA | 2026-05-25 16:18 |
| whats-up | what's next | --- MODE SWITCH: PROGRESS SUMMARY --- ⚠️ CRITICAL TAG REQUIREMENT — READ CAREFULLY: • You MUST wrap your ENTIRE response in <summary>...</summary> tags. • Do NOT use <observation> tags. <observation> output will be DISCA | 2026-05-27 11:05 |
| whats-up | what's next | --- MODE SWITCH: PROGRESS SUMMARY --- ⚠️ CRITICAL TAG REQUIREMENT — READ CAREFULLY: • You MUST wrap your ENTIRE response in <summary>...</summary> tags. • Do NOT use <observation> tags. <observation> output will be DISCA | 2026-05-25 15:23 |
| whats-up | what's next | --- MODE SWITCH: PROGRESS SUMMARY --- ⚠️ CRITICAL TAG REQUIREMENT — READ CAREFULLY: • You MUST wrap your ENTIRE response in <summary>...</summary> tags. • Do NOT use <observation> tags. <observation> output will be DISCA | 2026-05-30 18:05 |
| whats-up | what's next | --- MODE SWITCH: PROGRESS SUMMARY --- ⚠️ CRITICAL TAG REQUIREMENT — READ CAREFULLY: • You MUST wrap your ENTIRE response in <summary>...</summary> tags. • Do NOT use <observation> tags. <observation> output will be DISCA | 2026-05-29 01:13 |
| whats-up | what's next | --- MODE SWITCH: PROGRESS SUMMARY --- ⚠️ CRITICAL TAG REQUIREMENT — READ CAREFULLY: • You MUST wrap your ENTIRE response in <summary>...</summary> tags. • Do NOT use <observation> tags. <observation> output will be DISCA | 2026-05-26 20:47 |
| whats-up | what's next | --- MODE SWITCH: PROGRESS SUMMARY --- ⚠️ CRITICAL TAG REQUIREMENT — READ CAREFULLY: • You MUST wrap your ENTIRE response in <summary>...</summary> tags. • Do NOT use <observation> tags. <observation> output will be DISCA | 2026-05-26 03:10 |
| whats-up | what's next | --- MODE SWITCH: PROGRESS SUMMARY --- ⚠️ CRITICAL TAG REQUIREMENT — READ CAREFULLY: • You MUST wrap your ENTIRE response in <summary>...</summary> tags. • Do NOT use <observation> tags. <observation> output will be DISCA | 2026-06-01 01:09 |
| whats-up | what's next | --- MODE SWITCH: PROGRESS SUMMARY --- ⚠️ CRITICAL TAG REQUIREMENT — READ CAREFULLY: • You MUST wrap your ENTIRE response in <summary>...</summary> tags. • Do NOT use <observation> tags. <observation> output will be DISCA | 2026-05-26 04:04 |
| whats-up | what's next | --- MODE SWITCH: PROGRESS SUMMARY --- ⚠️ CRITICAL TAG REQUIREMENT — READ CAREFULLY: • You MUST wrap your ENTIRE response in <summary>...</summary> tags. • Do NOT use <observation> tags. <observation> output will be DISCA | 2026-05-29 11:14 |
| whats-up | what's next | --- MODE SWITCH: PROGRESS SUMMARY --- ⚠️ CRITICAL TAG REQUIREMENT — READ CAREFULLY: • You MUST wrap your ENTIRE response in <summary>...</summary> tags. • Do NOT use <observation> tags. <observation> output will be DISCA | 2026-05-26 23:00 |
| whats-up | what's next | --- MODE SWITCH: PROGRESS SUMMARY --- ⚠️ CRITICAL TAG REQUIREMENT — READ CAREFULLY: • You MUST wrap your ENTIRE response in <summary>...</summary> tags. • Do NOT use <observation> tags. <observation> output will be DISCA | 2026-05-26 06:28 |
| whats-up | what's next | --- MODE SWITCH: PROGRESS SUMMARY --- ⚠️ CRITICAL TAG REQUIREMENT — READ CAREFULLY: • You MUST wrap your ENTIRE response in <summary>...</summary> tags. • Do NOT use <observation> tags. <observation> output will be DISCA | 2026-05-29 06:11 |
| whats-up | what's next | --- MODE SWITCH: PROGRESS SUMMARY --- ⚠️ CRITICAL TAG REQUIREMENT — READ CAREFULLY: • You MUST wrap your ENTIRE response in <summary>...</summary> tags. • Do NOT use <observation> tags. <observation> output will be DISCA | 2026-05-27 00:05 |
| whats-up | what's next | --- MODE SWITCH: PROGRESS SUMMARY --- ⚠️ CRITICAL TAG REQUIREMENT — READ CAREFULLY: • You MUST wrap your ENTIRE response in <summary>...</summary> tags. • Do NOT use <observation> tags. <observation> output will be DISCA | 2026-05-30 03:11 |
| whats-up | what's next | --- MODE SWITCH: PROGRESS SUMMARY --- ⚠️ CRITICAL TAG REQUIREMENT — READ CAREFULLY: • You MUST wrap your ENTIRE response in <summary>...</summary> tags. • Do NOT use <observation> tags. <observation> output will be DISCA | 2026-06-01 04:08 |
| whats-up | what's next | --- MODE SWITCH: PROGRESS SUMMARY --- ⚠️ CRITICAL TAG REQUIREMENT — READ CAREFULLY: • You MUST wrap your ENTIRE response in <summary>...</summary> tags. • Do NOT use <observation> tags. <observation> output will be DISCA | 2026-05-25 18:38 |
| whats-up | what's next | --- MODE SWITCH: PROGRESS SUMMARY --- ⚠️ CRITICAL TAG REQUIREMENT — READ CAREFULLY: • You MUST wrap your ENTIRE response in <summary>...</summary> tags. • Do NOT use <observation> tags. <observation> output will be DISCA | 2026-05-27 11:22 |
| whats-up | what's next | --- MODE SWITCH: PROGRESS SUMMARY --- ⚠️ CRITICAL TAG REQUIREMENT — READ CAREFULLY: • You MUST wrap your ENTIRE response in <summary>...</summary> tags. • Do NOT use <observation> tags. <observation> output will be DISCA | 2026-05-31 18:11 |
| whats-up | what's next | --- MODE SWITCH: PROGRESS SUMMARY --- ⚠️ CRITICAL TAG REQUIREMENT — READ CAREFULLY: • You MUST wrap your ENTIRE response in <summary>...</summary> tags. • Do NOT use <observation> tags. <observation> output will be DISCA | 2026-05-31 14:08 |
| whats-up | what's next | --- MODE SWITCH: PROGRESS SUMMARY --- ⚠️ CRITICAL TAG REQUIREMENT — READ CAREFULLY: • You MUST wrap your ENTIRE response in <summary>...</summary> tags. • Do NOT use <observation> tags. <observation> output will be DISCA | 2026-05-27 05:18 |
| whats-up | what's next | --- MODE SWITCH: PROGRESS SUMMARY --- ⚠️ CRITICAL TAG REQUIREMENT — READ CAREFULLY: • You MUST wrap your ENTIRE response in <summary>...</summary> tags. • Do NOT use <observation> tags. <observation> output will be DISCA | 2026-05-31 22:21 |
| whats-up | what's next | --- MODE SWITCH: PROGRESS SUMMARY --- ⚠️ CRITICAL TAG REQUIREMENT — READ CAREFULLY: • You MUST wrap your ENTIRE response in <summary>...</summary> tags. • Do NOT use <observation> tags. <observation> output will be DISCA | 2026-05-28 15:50 |
| whats-up | what's next | --- MODE SWITCH: PROGRESS SUMMARY --- ⚠️ CRITICAL TAG REQUIREMENT — READ CAREFULLY: • You MUST wrap your ENTIRE response in <summary>...</summary> tags. • Do NOT use <observation> tags. <observation> output will be DISCA | 2026-05-25 18:14 |
| whats-up | what's next | --- MODE SWITCH: PROGRESS SUMMARY --- ⚠️ CRITICAL TAG REQUIREMENT — READ CAREFULLY: • You MUST wrap your ENTIRE response in <summary>...</summary> tags. • Do NOT use <observation> tags. <observation> output will be DISCA | 2026-05-26 04:18 |
| whats-up | what's next | --- MODE SWITCH: PROGRESS SUMMARY --- ⚠️ CRITICAL TAG REQUIREMENT — READ CAREFULLY: • You MUST wrap your ENTIRE response in <summary>...</summary> tags. • Do NOT use <observation> tags. <observation> output will be DISCA | 2026-05-31 09:05 |
| whats-up | what's next | --- MODE SWITCH: PROGRESS SUMMARY --- ⚠️ CRITICAL TAG REQUIREMENT — READ CAREFULLY: • You MUST wrap your ENTIRE response in <summary>...</summary> tags. • Do NOT use <observation> tags. <observation> output will be DISCA | 2026-05-28 22:01 |
| whats-up | what's next | --- MODE SWITCH: PROGRESS SUMMARY --- ⚠️ CRITICAL TAG REQUIREMENT — READ CAREFULLY: • You MUST wrap your ENTIRE response in <summary>...</summary> tags. • Do NOT use <observation> tags. <observation> output will be DISCA | 2026-05-27 17:05 |
| whats-up | what's next | --- MODE SWITCH: PROGRESS SUMMARY --- ⚠️ CRITICAL TAG REQUIREMENT — READ CAREFULLY: • You MUST wrap your ENTIRE response in <summary>...</summary> tags. • Do NOT use <observation> tags. <observation> output will be DISCA | 2026-05-27 21:31 |
Source: ~/workspace/scripts/skill_audit.py · MC-797