Loading...
Loading...
Found 2,826 Skills
Facilitates structured ideation sessions using proven brainstorming techniques (SCAMPER, SWOT, 5 Whys, Mind Mapping, Six Thinking Hats, Reverse Brainstorming, Starbursting, Brainwriting). Produces a brainstorming-report.md of organized ideas and actionable insights. Operates in three intents: Create (new session), Update (add techniques or deepen coverage), Validate (confirm insights align with project goals). Use when the user says: "brainstorm", "ideate", "generate ideas", "explore options", "SCAMPER", "SWOT analysis", "mind map", "Six Thinking Hats", "5 Whys", "creative session", "what if we", "let's explore", "think through possibilities", "find alternatives", or "problem-solve". This skill PLANS only — it never writes application code or runs tests.
Create, organize, incrementally update, validate, and publish a complete application User Manual for web, mobile, API, infrastructure, architecture, and data surfaces. Use for UserManual.Init, Analyze, Update, or Release; MkDocs/Material documentation; bilingual English and Arabic manuals; audience editions; tutorials; system documentation; diagrams; and documentation coverage.
By identifying and leveraging potential differences (efficiency/scale/cognition/gravitation), choose to stand in a high-potential position to amplify the competitiveness of individuals or organizations. Applicable to scenarios such as career choice, entrepreneurial direction judgment, and industry trend analysis. Use this skill when you face decisions like "which platform/company/industry to choose" or want to understand why there is a huge gap in results despite similar efforts. Not applicable to the execution stage where you have locked onto a track and can only work hard (you should return to improving specific abilities at this time), nor to pure internal management optimization (potential is an external lever). Key trigger signals: "Why am I not succeeding despite working so hard?", "Choose industry A or B?", "Does this industry have a future?", "How to leverage momentum?"
Calculate the recommended PSU wattage for a PC build using Newegg's CPU/GPU wattage APIs plus fixed power tables for other components. Use this skill whenever users ask: "what PSU do I need?", "how many watts for my build?", "is my power supply enough?", "calculate power for my PC", or describe PC components (CPU + GPU + RAM + storage) and want to know what power supply to buy. Trigger even if the user hasn't explicitly mentioned PSU — wattage is the natural next question once someone lists their components.
Write the test first, watch it fail, then write the least code that passes. Covers where the test belongs, what makes it honest, what a passing test proves and what it does not, recovering when code was written before the test, and starting a bug fix from a red run. A test nobody watched fail proves nothing. Use when implementing a feature or a bugfix, when a test was written after the code, when a test passes the first time you run it, or when the user says "write tests for this", "add coverage", or "TDD this". Not for judging tests inside a change under review, and not for choosing a test framework.
AI Text Generation Tool: Uses large language models to generate text content based on prompts, supporting combined understanding of images/videos/text. Available models include GEM_3_FLASH (fast response) and GEM_3_1_PRO (high-quality complex analysis). Triggered when users mention phrases like "AI text generation", "AI writing", "text generation", "help me write a paragraph", "text generation", "generate text", "write with AI", "AI analyze image content", "image recognition", "video analysis".
Reviews a reverse-skill case package for scope readiness, Evidence to Finding to Path traceability, work item coverage, timeline references, and optional artifact hash integrity before report handoff.
Used for authorized security testing of desktop thick clients, covering local storage, update channels, IPC, traffic, and client-side trust boundaries.
Audit a rules document (SKILL.md, CLAUDE.md, AGENTS.md, or convention doc) and propose updates that leverage what the current Claude version knows natively. Classifies each rule as Keep / Sharpen / Add-rationale / Redundant / Stale, proposes Missing rules from the shared quality baseline, and applies all proposed changes only on one explicit confirmation. A guided --interactive mode replaces the batch confirmation with per-rule decisions.
Design, create, run, monitor, and maintain Vapi Simulations for assistants and squads. Use for simulation personalities, scenarios, structured-output success criteria, simulations, suites, chat or voice runs, tool mocks, target variables, lifecycle webhooks, regression coverage, CI quality gates, run-result analysis, and simulation API validation errors. Do not use for fixed-turn mock-conversation Evals unless the user is deciding between Evals and Simulations.
Diagnoses bias, anomalies, and strange-looking results on a specific PostHog experiment. Covers empty / 0-exposure experiments, sample ratio mismatch, identity fragmentation, multi-variant exposure, uneven-split exclusion bias, significance traps (peeking, A/A, Bayesian vs Frequentist), PostHog-vs-SQL discrepancies, and surprises after mid-run edits. Symptom-driven dispatch to the right diagnostic. TRIGGER when: user asks 'is my experiment biased?' or 'why 0 exposures?', references the bias banner, says a variant looks strange / wrong / off, sees significance flipping, notices PostHog numbers disagreeing with their SQL, sees an A/A test showing significance, or reports surprises after mid-run edits. DO NOT TRIGGER when: creating a new experiment (use creating-experiments), only configuring rollout (use configuring-experiment-rollout) or metrics (use configuring-experiment-analytics), or only asking lifecycle questions (use managing-experiment-lifecycle).
Assesses what a page's heatmap is telling you and recommends concrete changes. Pulls click / rageclick / scroll-depth data for a URL, names the hot elements by cross-referencing autocapture events on the same page, and can create a saved heatmap the user opens in PostHog, then summarizes the behavior and proposes improvements. TRIGGER when: user asks what a heatmap shows, why people aren't clicking something, where users rage-click, how far they scroll, what to change on a page based on heatmap/click data, or to 'analyze/assess/review the heatmap' for a URL. DO NOT TRIGGER when: the user only wants to create a saved heatmap screenshot with no analysis (use heatmaps-saved-create directly), or is asking about session replay in general (use investigating-replay).