Loading...
Loading...
Found 12,021 Skills
End-to-end Swiggy ordering with Prava card-token checkout. Use when the user wants an AI agent to set up Swiggy MCP, browse/search Swiggy Food/Instamart/Dineout, choose a saved delivery address, add or review Swiggy cart items, create a Prava authorization/payment session, and complete Swiggy checkout using Prava-issued tokenized card credentials. Also use when the user asks to install or configure the Swiggy MCP plus Prava payment flow for agentic purchases.
Convert scientific papers, theses, technical reports, source code, figures, or research manuscripts into evidence-grounded Chinese invention patent drafts. Use when an AI agent must extract patentable technical contributions, map every claimed feature to source evidence, preserve core formulas as editable Office Math, generate claim-aligned flowcharts and methodology figures, compare a paper with an existing patent, audit support and consistency, or deliver separate Chinese DOCX files for claims, specification, abstract, and abstract figure.
THE workflow for picking up and carrying ONE ticket/card forward, for an autonomous worker agent or for a human doing it locally. Resolves the repo's tracker from the AFK registry (~/.claude/afk.json; GitHub Projects or Linear), picks one ticket by priority, routes by status x label (interview / human walkthrough / execute), loads LEARNINGS.md as binding constraints, implements test-first, verifies end-to-end and simplifies the diff (the /go finish), then branches to a PR for the reviewer. Use when the user says "pick up <id>", "work on issue <id>", invokes /engineer, invokes /pickup, says "pickup", or at the very start of working any card.
Groom and route tickets on ANY project board through a shared status vocabulary (from raw `Triage` to a fully spec'd `Ready for Agent` or `Ready for Human`) so engineer only ever executes work that is already specified. Tracker-agnostic (GitHub Projects, Linear, or any board via a small adapter). Use to create/triage/groom issues, prepare work for an AFK agent, or manage the pre-implementation flow. Pairs with engineer + reviewer.
Use when starting a new app or repo, or making an existing repo agent-ready (say "new app", "new repo", "create a project", "bootstrap this repo"). Sets up git, AGENTS.md + CLAUDE.md, .gitignore, and a per-repo Obsidian knowledge vault, offers the pinned default stack, accounts for deployment (preview + prod), then optionally pressure-tests scope (make-money) and locks in the domain language (grill-with-docs).
Carve guardrail-adjacent items out of scope with safe alternatives before risk-adjacent work starts, then run the safe remainder at full strength in a fresh subagent that only ever sees the carved prompt, never the risky input. Use when a task includes stealth, scraping, privacy, IP, policy, licensing, security, or other safety-adjacent material that could be silently dropped, over-elaborated, or needlessly diluted. Fires on the impulse, not only the topic: the moment you notice yourself about to hedge, soften, silently skip, or brace for a refusal, carve before you execute.
Set up automated agent-driven development with Ralph. Run AI agents in a loop to implement features from user stories, verify acceptance criteria, and log progress for the next agent.
Generate or update a README.md in French, oriented Product Owner, with Mermaid diagrams. Reviews and improves technical documentation in docs/. Also generates CLAUDE.md and AGENT.md if missing. Triggers on: create readme, update readme, generate readme, générer le readme, mettre à jour le readme, /readme.
Manages agent isolation levels and resource boundaries. Configures strict, moderate, and permissive isolation profiles. Activate on 'isolation level', 'agent isolation', 'resource boundaries', 'sandboxing', 'agent containment'. NOT for permission validation (use dag-permission-validator) or runtime enforcement (use dag-scope-enforcer).
Use when choosing which Prefactor SDK skill to load for agent instrumentation or for building a custom provider integration on top of @prefactor/core.
Workflow orchestration for complex coding tasks. Use for ANY non-trivial task (3+ steps or architectural decisions) to enforce planning, subagent strategy, self-improvement, verification, elegance, and autonomous bug fixing. Triggers: multi-step implementation, bug fixes, refactoring, architectural changes, or any task requiring structured execution.
Launch a sub-agent judge to evaluate results produced in the current conversation