Loading...
Loading...
Found 785 Skills
Use this skill when a user asks how to generate, integrate, or implement a Word‑like document editor in React using Syncfusion. Trigger it for requests involving the Syncfusion React Document Editor, React‑based editor integration, document editing and formatting, comments and track changes, working with tables and images, managing headers and footers, applying document protection, and building end‑to‑end document workflows in React applications.
Solidity smart contract security: vulnerability prevention, secure coding patterns, gas-safe optimizations, and audit preparation. Use when writing or reviewing Solidity code for security, auditing contracts, preventing reentrancy/overflow/access-control issues, optimizing gas safely, or preparing contracts for professional audits. Keywords: solidity security, smart contract audit, reentrancy, access control, CEI pattern, front-running, slither, invariant, vulnerability, exploit, secure solidity.
Write and maintain an implementation diary capturing what changed, why, what worked, what failed (with exact errors and commands), what was tricky, and how to review and validate. Activates proactively during non-trivial implementation work (new features, bug fixes, refactors, research spikes). Does not activate for trivial tasks like one-line fixes, config tweaks, or quick questions.
Shared workflow rules for SpriteCook. Use together with spritecook-generate-sprites or spritecook-animate-assets for credits, downloads, asset manifests, safe auth handling, and recommended defaults.
Discover and understand project rules, coding standards, and architectural guidelines before starting a task. Use when you need to know the constraints, patterns, or compliance requirements for a feature, file, or technology.
Entry P1 category router for reconnaissance and methodology. Use when mapping scope, discovering assets, fingerprinting technology, building endpoint inventory, and choosing the first high-value security testing path.
Activate this when users need to understand extreme events (bubbles, crashes, mass hysteria, cults, mob behavior), diagnose systemic organizational failures, or assess the risk of multiple psychological/market/institutional forces aligning in the same direction. Typical trigger signals: the phenomenon described by the user "far exceeds what any single factor can explain"; the user attempts to explain an extreme outcome with a single cause; the user is concerned about "multiple adverse factors erupting simultaneously". Not applicable to conventional single-factor decision analysis or assessment of mild incremental changes.
Orchestrates multi-advisor council debates on high-impact architecture, technology, or product decisions. Dispatches 3-5 domain archetype subagents (pragmatic-engineer, architect-advisor, security-advocate, product-mind, devils-advocate, the-thinker) through opening statements, tensions, position evolution, and synthesis phases. Preserves dissent and delivers actionable recommendations with captured risks. Use when evaluating trade-offs, stress-testing a PRD or tech spec, resolving dilemmas with multiple viable options, or when a decision needs diverse expert perspectives. Don't use for simple yes/no questions, factual lookups, creative brainstorming without tradeoffs, or tasks where a single expert perspective suffices.
This skill should be used when the user asks to generate an image, create an AI image, produce a product image, generate a visual from a prompt, or check and continue an existing image generation task. Generates images through CreatOK's image generation API and can also recover interrupted generation flows from an existing task id.
Annie Duke's Decision Quality framework applied to a business decision. Spawns a team of specialist agents — Resulting Auditor, Calibrator, Pre-Mortem Analyst, Quit Strategist, Process Architect — who each apply a distinct lens from Duke's framework to evaluate whether a decision is sound regardless of outcome. The lead synthesizes into a stacking analysis: which biases are operating, which process flaws exist, and the honest Duke verdict. Use when the user says "duke this", "is this a good bet", "should I quit", "evaluate this decision", or faces any high-stakes choice under uncertainty and wants rigorous decision-process analysis. Works as a standalone analysis or after /office-hours.
Richard Feynman's Integrity Audit applied to any analysis, business plan, or decision. Spawns a team of specialist agents — Source Auditor, Self-Deception Hunter, Translation Tester, Cargo Cult Inspector, Confidence Inverter — who each apply a distinct lens from Feynman's framework to detect dishonesty, self-deception, and cargo cult reasoning. The lead synthesizes into a verdict: is this analysis honest, or is it fooling itself? Use when the user says "feynman this", "integrity audit", "is this honest", "am I fooling myself", "cargo cult check", or wants to stress-test any analysis, plan, or claim before trusting it. Works standalone or as a meta-audit after /munger or /thiel.
Autonomously optimize any Claude Code skill by running it repeatedly, scoring outputs against binary evals, mutating the prompt, and keeping improvements. Based on Karpathy's autoresearch methodology. Use when: optimize this skill, improve this skill, run autoresearch on, make this skill better, self-improve skill, benchmark skill, eval my skill, run evals on. Outputs: an improved SKILL.md, a results log, and a changelog of every mutation tried.