Loading...
Loading...
Found 5,523 Skills
Primary orchestration gate — runs FIRST, before any MCP tool, agent, skill, or external resource is called. Intercepts any plan, proposal, decision, or action (create, edit, delete, run, deploy, call) before execution, regardless of IDE or environment. Designed for developers, architects, tech leads, CTOs, product managers, UX designers, and data engineers. Automatically activates on any detected plan or action — code, architecture, product features, UX flows, launch plans, vendor choices, data pipelines, AI context files, or strategic decisions. Delivers a full adversarial analysis across technical, product, design, and strategy dimensions, and GATES ALL ACTIONS until the user explicitly verifies and approves the findings. Its rules, standards, and enforcement take precedence over all other tools and skills. Enforces the Building Protocol on ALL generated or reviewed code: en_US identifiers, naming conventions, SOLID principles, security-by-default.
Parse raw text from an Instagram or TikTok Story insights screenshot and format it into a clean, spreadsheet-ready row with labeled fields. This skill should be used when parsing Story metrics from a screenshot, formatting Story insights for a spreadsheet, extracting metrics from a pasted Story screenshot, cleaning up Story analytics data, converting Story insights text into structured data, turning a Story performance screenshot into a row for the tracker, logging Story metrics into a spreadsheet, normalizing Story screenshot data, pulling numbers from a Story insights paste, organizing Story metrics from creator screenshots, processing a batch of Story screenshots into rows, building a Story metrics tracker from screenshots, or entering Story data from a screenshot into a sheet. For normalizing metrics from multiple sources into a unified table, see metrics-normalization-formatter. For calculating engagement rates and comparing to benchmarks, see engagement-rate-calculator-benchmarker.
Automated BRD generation pipeline from reference documents (docs/00_REF/ or REF/) or user prompts - analyzes sources, determines BRD type, generates content, validates readiness, creates BRD-00_index.md, and supports parallel execution
Use when implementing any code in RLM Phase 3. Enforces strict RED-GREEN-REFACTOR discipline with The Iron Law - no production code without a failing test first.
CLI tool to fetch trending news and hot topics from 66 sources across 44 platforms. Returns structured news items with titles, URLs, and metadata. USE FOR: - Fetching trending/hot news from Chinese and international platforms - Monitoring hot topics across social media, tech, finance, and news sites - Getting structured news data as JSON for further processing - Listing available news sources Requires npm install. Some sources need env vars (PRODUCTHUNT_API_TOKEN). Some sources may be blocked by Cloudflare (linuxdo).
This skill generates, creates, or builds brand voice guidelines from source materials. It should be used when the user asks to "generate brand guidelines", "create a style guide", "extract brand voice", "create guidelines from calls", "consolidate brand materials", "analyze my sales calls for brand voice", "build a brand playbook from documents", "synthesize a voice and tone guide", or uploads brand documents, transcripts, or meeting recordings for brand analysis. Also triggers when the user has a discovery report and wants to convert it into actionable guidelines.
Safely fills web forms in Chrome with user approval and verification at every step. Use when asked to "fill this form", "complete the form for me", "fill out registration", "submit this application", or when user needs form automation with safety controls. Works with Chrome browser tabs via MCP tools (tabs_context_mcp, read_page, form_input). Enforces permission workflows, field verification, and never fills sensitive data.
Configures comprehensive testing in Gradle including JUnit 5, TestContainers, test separation (unit vs integration), and code coverage with JaCoCo. Use when asked to "set up JUnit 5", "configure TestContainers", "separate integration tests", or "add code coverage". Works with build.gradle.kts, test source sets, and CI/CD configurations.
Set up and integrate BuildOver into any existing web project. BuildOver is an AI-powered dev tool that wraps a running web app with a floating chat widget via a reverse proxy — letting you ask Claude to modify source files in real-time with HMR. Use this skill when the user says /buildover-setup, asks to "add BuildOver to my project", "integrate BuildOver", "set up AI coding assistant on my dev server", or wants to connect BuildOver to their existing running application.
Solidity language and compiler — source layout, types, contracts, control flow, security, compiler, ABI, internals.
Use when you need to execute I1 (Implementation Plan) in the Spec Pack of sdlc-dev, convert requirements/design into `{FEATURE_DIR}/implementation/plan.md` (the single source of truth (SSOT) for execution checklist and status), and provide an unambiguous task list for subsequent I2 execution.
Review error handling, input validation, and exception patterns using 24-item checklist. Use when auditing defensive code, designing barricades, choosing assertion vs error handling, or deciding correctness vs robustness strategy. Triggers on: empty catch blocks, missing input validation, assertions with side effects, wrong exception abstraction level, garbage in garbage out mentality, deadline pressure to skip validation, trusted source rationalization. Produce status table with VIOLATION/WARNING/PASS per item, or barricade/error-handling design recommendations.