Prepare social publishing requests and approval artifacts through the PostPlus platform-owned social publishing workspace.

Creates detailed Standard Operating Procedures (SOPs) for business processes. Use when user needs SOPs, process documentation, operational guides, workflow documentation, or step-by-step instructions for repeatable business processes.

Decrypt SOPS-encrypted YAML files back to .env format. Finds *.enc.yaml files, decrypts, and converts YAML back to dotenv. Use when user mentions "decrypt env", "sops decrypt", "decrypt secrets", "restore env", "decrypt .env", "restore secrets", "decrypt environment files".

Encrypt .env files using SOPS + age. Converts dotenv to YAML format (avoids SOPS bug #1435), then encrypts. Auto-detects unencrypted .env files. Use when user mentions "encrypt env", "sops encrypt", "encrypt secrets", "encrypt .env", "encrypt environment", "re-encrypt", "update encrypted".

Grounds every implementation decision in official documentation. Use when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters.

Run the SPARC Specification phase — gather requirements, define acceptance criteria, identify constraints, and store the spec in memory

Establish and manage SSH connections to remote machines, including key generation, configuration, and file transfers. Use when connecting to remote servers, executing remote commands, or transferring files via SCP.

Catalog of ssmd DQ checks — what each measures, pass/fail criteria, common failure modes and fixes, fanout rules, and accountability SLOs. Use when investigating DQ failures, understanding check behavior, or adding new checks.

Create or switch to feature branches with proper naming conventions. Use when user wants to start working on a new feature, start a feature. Generates feature/branch-name patterns from descriptions, checks existence, and creates/switches accordingly.

Ticket kickoff only (setup + plan + draft PR + failing tests). Use /dev for the full autonomous pipeline. Accepts goal or Trello card. Example: /start-ticket implement rate limiting

Show active tracks, progress, current tasks, and blockers

When the user wants to create, optimize, or structure a status page. Also use when the user mentions "status page," "status.yourdomain.com," "uptime," "service health," "incident page," or "system status." For incident comms, use public-relations.

Show .things/ status - registered collections, item counts, git state, and optional tag aggregation. Use when user says 'things status', 'what do I have', 'show me my things'.

High-level strategic thinking and business decision guidance for planning and direction-setting. Use when: making strategic decisions, evaluating business options, setting direction, analyzing trade-offs, or when user mentions strategy, business planning, competitive analysis, or long-term planning.

Your product soundboard. Work through product decisions conversationally - Claude gathers context, challenges assumptions, captures decisions, and creates Linear issues.

Convert normalized timed transcript data into subtitle artifacts such as SRT and ASS. Use this when a stable normalized transcript JSON already exists and the main job is subtitle chunking, timing normalization, and export packaging.

Manage authentication and user operations in Supabase. Use for sign up, sign in, sign out, password resets, and user management.

Extract and decode Supabase-related JWTs from client-side code, cookies, and local storage patterns.

Data migration and synchronization to SurrealDB from MongoDB, PostgreSQL, MySQL, Neo4j, Kafka, and JSONL. Full and incremental CDC sync. Part of the surreal-skills collection.

Quick persona switching. Triggers: 'switch persona', 'switch to X', 'become X'. Lists personas, reads selected file, switches immediately.

Git push/pull/status for the .things/ repository. Use when user says 'sync things', 'push things', 'pull things', 'things git status'.

Consolidate multiple parallel research documents into a single unified report. Produces a self-contained document that a reader with no prior context can understand completely.

This skill should be used when debugging complex kernel issues requiring systematic investigation and documentation. Use for documenting problem analysis, root cause investigation, solution implementation, and evidence collection following Breenix's Problem→Root Cause→Solution→Evidence pattern.

Optimize resumes for software engineering, PM, and technical roles

Remove the terminator kill hooks from the current project. Strips the single-kill.sh and double-kill.sh Stop hook entries from .claude/settings.local.json (preserving other hooks), and deletes the hook scripts and config. Use when the user asks to "remove terminator", "uninstall the kill hooks", or "disable session termination".

Use ONE Bash script instead of N sequential Read calls when analyzing multiple files, auditing codebase, finding all matches, scanning dependencies, counting lines, or listing files matching a pattern. Replaces wasteful multi-Read loops with compact shell pipelines.

In a long trajectory where you're defending a path you committed to early, run a quick self-check for sunk-cost and confirmation bias before continuing — only when evidence is being explained away.

Use when a defect is selective (some endpoints/regions/users/times affected, not all) and the cause is unclear — map what IS vs IS-NOT affected; the boundary contrast points at the root cause.

Use before building when a request is vague, assumption-laden, or "obvious." Ask the clarifying questions that surface hidden requirements and false premises instead of guessing.

Patterns for creating well-researched Linear tickets with codebase context.

ODIN's compress-operations dispatcher under the Compressor/Extender/Purger role. Invoke on "tidy", "clean up", "tidy this file/memory/workspace/git/docs", or when active context (current file, diff, stack, memory directory) has structural rot to resolve before touching behavior. Detects target domain from context and routes to the sibling skill. Requires explicit target or clear active-context signal — do not invoke speculatively.

Start an issue in a new tmux window: create the worktree, launch /start-issue autonomously in that window, leave the user free in their current window. Use when user has tmux running and wants to begin issue work without context-switching their session. Triggers: 'tmux start issue #N', 'start in new window'.

Common Tokio patterns and idioms for async programming. Use when implementing worker pools, request-response patterns, pub/sub, timeouts, retries, or graceful shutdown.

Search past decisions, prior research, conversation history, monorepo docs, and fetched web pages. Use toolkit recall search to find context from previous work, and toolkit fetch to save web pages for future search.

Convert strategy docs to Python (pandas, framework-agnostic) and TradingView Pine Script v5. Use when translating strategies to code for backtesting.

Configure Turborepo for efficient monorepo builds with local and remote caching. Use when setting up Turborepo, optimizing build pipelines, or implementing distributed caching.

TypeScript strict mode with eslint and jest

TypeScript strict patterns and best practices. Trigger: When implementing or refactoring TypeScript in .ts/.tsx (types, interfaces, generics, const maps, type guards, removing any, tightening unknown).

Advanced TypeScript: generics, conditional types, mapped types, type guards, utility types, and strict type safety patterns.

TypeScript best practices, strict typing patterns, and type safety strategies. Use when implementing TypeScript code with focus on type correctness and maintainability.

Implement collection actions in Umbraco backoffice using official docs

Implement current user actions in Umbraco backoffice using official docs

Implement entity create option actions in Umbraco backoffice using official docs

Create new Umbraco backoffice extensions using the official dotnet template

Implement granular user permissions in Umbraco backoffice using official docs

Implement menu items in Umbraco backoffice using official docs

Implement modals in Umbraco backoffice using official docs

Implement package views in Umbraco backoffice using official docs

Implement preview app providers in Umbraco backoffice using official docs

Implement property actions in Umbraco backoffice using official docs

Implement property value presets in Umbraco backoffice using official docs

Implement search providers in Umbraco backoffice using official docs

Implement sections in Umbraco backoffice using official docs

Implement themes in Umbraco backoffice using official docs

Implement tree items in Umbraco backoffice using official docs

Implement Umbraco elements in Umbraco backoffice using official docs

Update an existing .claudeignore file by adding, removing, or revising entries based on current repository state.

Sync tasks and refresh memory from your current activity

Use when updating Claude Dev Kit components - checks registry for new versions, shows changelogs, updates components individually or all at once, supports rollback

Load saved Playwright storageState authentication profiles before browser automation. Activates when `.playwright/profiles.json` exists and browser work begins on authenticated pages. Trigger phrases include "use profile", "load profile", "browser as [role]", "authenticated browser", "logged in browser session".

Persona-family sub-skill for web/app user personas (Power User Pat, Average User Avery, First-Timer Fran, Non-Technical Nancy, Accessible User Ash). Router-dispatched from the user-feedback parent skill on GREENFIELD/FEATURE/WEB_APP project type. Loads only the Category 2 profile block from references/persona-library.md.

Use when researching GitHub issues, PRs, and discussions for community solutions and known gotchas - searches via WebSearch with site filters and extracts problem-solution patterns

Post notes, send encrypted messages, and interact with relays using the Nostr protocol.

Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

Use when you need to run interactive CLI tools (vim, git rebase -i, Python REPL, etc.) that require real-time input/output - provides tmux-based approach for controlling interactive sessions through detached sessions and send-keys

This skill should be used when the user asks to "check dependencies", "verify plugin requirements", "what plugins am I missing", "validate plugin dependencies", or invokes /utils:dependency-checker. Validates declared dependencies in extends-plugin.json files against installed and enabled plugins.

Validate XML workflow files for structural correctness, cross-reference integrity, and format compliance. Reports issues by severity (ERROR, WARNING, INFO).

Structure post-acquisition value creation plans with revenue, cost, and operational levers mapped to an EBITDA bridge. Includes 100-day priorities, KPI targets, and accountability frameworks. Use when planning post-close execution, preparing operating partner materials, or building a board-ready value creation roadmap. Triggers on "value creation plan", "100-day plan", "post-close plan", "EBITDA bridge", "operating plan", or "value creation levers".

Check the status of existing agreements with a vendor across all connected systems

Run VernHole on existing discovery output. Point the council at a consolidation or master plan and get fresh perspectives.

Vite configuration patterns

Send WhatsApp messages to other people or search/sync WhatsApp history via the wacli CLI (not for normal user chats).

Wardley Mapping strategic analysis—map value chains against evolution to reveal build vs buy decisions and competitive dynamics. Use for technology strategy or investment decisions.

Web scraping and data extraction from websites

Use when reading WhatsApp messages, searching conversations, sending messages, listing chats, or interacting with WhatsApp workspaces

Glide workflows (automations) - triggers, nodes, and automation patterns. Covers both client-side App Interactions and server-side workflows.

Shape a feature through collaborative R/S/fit-check dialogue before planning implementation

Launch one or more tasks in new git worktrees using workmux.

Manage Windows Terminal tabs using wt.exe. Use when the user says 'open tabs', 'new tab', 'switch tab', 'focus tab', 'move pane to tab', 'tab color', 'tab title', 'multiple tabs', 'rename tab', or any variation of wanting to manage Windows Terminal tabs.

Deep analysis workflows for World Weaver memory systems, code, and architecture

Use this skill for XCrawl map tasks, including site URL discovery, regex filtering, scope estimation, and crawl planning before full-site crawling.

Play Yoink, an onchain capture-the-flag game on Base. Yoink the flag from the current holder, check game stats and leaderboards, view player scores, and compete for the trophy. Uses Bankr for transaction execution.

Play Yoink, an onchain capture-the-flag game on Base. Yoink the flag from the current holder, check game stats and leaderboards, view player scores, and compete for the trophy. Uses Bankr for transaction execution.

Replace with when the AI should activate this skill. Be pushy — cover multiple phrasings so the AI activates for a wide range of user prompts.

Zod 4 schema validation patterns. Trigger: When using Zod for validation - breaking changes from v3.

Manage and troubleshoot PATH configuration in zsh. Use when adding tools to PATH (bun, nvm, Python venv, cargo, go), diagnosing "command not found" errors, validating PATH entries, or organizing shell configuration in .zshrc and .zshrc.local files.

This skill should be used when building automated trading systems, implementing limit orders, or adding DCA/TWAP functionality. Covers limit orders, stop losses, DCA schedules, and TWAP execution.

This skill should be used when building perpetual trading bots, implementing leverage functionality, or adding position management. Covers Avantis integration, long/short positions, and risk controls.

This skill should be used when building market data displays, implementing price feeds, or adding technical analysis. Covers prices, market caps, technical analysis, sentiment, and trending tokens.

This skill should be used when building token launch tools, implementing Clanker integration, or adding fee claiming functionality. Covers ERC20 deployment, metadata updates, and trading fees.

This skill should be used when the user asks to "file a bug", "report a bug", "log a bug", "create a bug issue", or mentions a marketplace plugin bug that should be tracked. Files bug reports as GitHub issues on cadrianmae/claude-marketplace.

Systematic commit process with pre-commit checks, atomic commits, and conventional commit messages

Validate at every layer data passes through to make bugs impossible

Validate at every layer data passes through to make bugs impossible

This skill should be used when the user requests to create a pull request from the current branch (e.g., "create PR", "draft PR", "open PR"). Provides workflow guidance for creating well-structured Draft PRs using GitHub CLI.

Operate Linux systems avoiding permission traps, silent failures, and common admin mistakes.