Loading...
Loading...
Found 3,061 Skills
Verify statistics and claims in blog posts by fetching cited source URLs and checking if the claimed data actually appears on the page. Extracts all statistical claims (numbers, percentages, named sources), fetches each cited URL via WebFetch, and scores match confidence (exact match 1.0, paraphrase 0.7-0.9, not found 0.0). Flags uncited claims as UNVERIFIED. Use when user says "fact check", "verify statistics", "check sources", "validate claims", "factcheck", "source verification".
This skill should be used when the user asks to "diagnose context problems", "fix lost-in-middle issues", "debug agent failures", "understand context poisoning", or mentions context degradation, attention patterns, context clash, context confusion, or agent performance degradation. A core context engineering skill — also activates when the user mentions "context engineering" or "context-engineering" in the context of diagnosing and mitigating context failures.
Runs the Metabase semantic checker against a tree of Representation Format YAML files to verify that all references resolve — cross-entity references (collection_id, dashboard_id, parent_id, parameter source cards, snippet references, transform tags, etc.) and references to columns inside MBQL and native queries. Use when the user asks to "semantic check", "check references", "validate queries against the schema", or diagnose a broken reference. Requires database metadata on disk (by default `.metabase/metadata.json`).
Use when an approved plan exists and needs execution, or when a hotfix/one-sentence scope needs direct TDD implementation — dispatches subagents per task, validates, reports
Implement one task or scoped change: make the change, add valuable tests, and verify it works.
Replicate and validate a GitHub issue by spinning up Archon, analyzing the issue, and systematically testing all described symptoms using browser automation. Use when: User wants to reproduce a bug, validate a GitHub issue, confirm a reported problem, or investigate whether an issue is real before working on a fix. Triggers: "replicate issue", "reproduce issue", "validate issue", "confirm bug", "test issue", "can you reproduce", "try to replicate", "verify the bug". Capability: Checks out main, pulls latest, starts Archon, reads the GitHub issue, then uses agent-browser to systematically test every symptom and produce a findings report. NOT for: Fixing issues (use /archon or /exp-piv-loop:fix-issue), general UI testing (use /validate-ui).
Continuously interview users around a plan or design until a shared understanding is reached, and address each branch of the decision tree one by one. Use this when the user wants to stress-test a plan, have their design grilled, or mentions "grill me".
Capture noteworthy review violations for the eval framework. Use when validator-run finds review failures — judges violations and saves notable ones to evals/inventory.yml.
Produces a margin-by-product table and three pricing-scenario data views so the owner can see the full financial picture before making a pricing decision. Accepts optional product name argument.
Validate n8n expression syntax and fix common errors. Use when writing n8n expressions, using {{}} syntax, accessing $json/$node variables, troubleshooting expression errors, mapping data between nodes, or referencing webhook data in workflows. Use this skill whenever configuring node fields that reference data from previous nodes — expressions are how n8n passes data between nodes, and getting the syntax wrong is the most common source of workflow errors.
Create and improve agent skills following the Agent Skills specification. Use when asked to create, write, or update skills.
Apply a structured judgment and discernment framework to any high-stakes decision, recommendation, or AI-generated output. Use this skill whenever the user wants to think more carefully before committing to something — a people decision, a strategic call, a piece of writing they're about to send, or an AI output they're not sure whether to trust. Trigger on phrases like "is this right?", "am I confident about this?", "help me think this through", "run the discernment framework", "judgment check", "calibration check", "am I being overconfident", "should I trust this output", "premortem", or any time someone is wrestling with whether their thinking is sound. Also trigger proactively when someone appears to be accepting a claim, recommendation, or AI-generated output without questioning it — especially on high-stakes topics like hiring, restructuring, or communications that will reach many people.