Loading...
Loading...
Found 6,717 Skills
Comprehensive pull request review using specialized agents
Curates insights from reflections and critiques into CLAUDE.md using Agentic Context Engineering
Ming Court Code —— Standardize Claude Code development processes using the institutional framework of the Ming Dynasty court. Three-level adaptive modes: Oral Edict (rapid execution), Court Debate (structured solution), Morning Court (multi-agent parallel processing).
Use when found gap or repetative issue, that produced by you or implemenataion agent. Esentially use it each time when you say "You absolutly right, I should have done it differently." -> need create rule for this issue so it not appears again.
Design a goal-oriented agent loop, and review it for the ways loops go wrong — spinning and burning tokens, Goodhart-gaming the verifier, or running a wrong answer to completion. Two actions: (1) WRITE a loop — gate whether to build it, define a machine-decidable goal, pick the loop type, pick a skeleton; (2) REVIEW a loop — run it past five failure modes plus decidability, boundaries, fallback, judge independence, and keep-judgment-with-the-human red lines. Use when designing an autonomous agent loop, or when you already have one and worry it will spin, cheat, or run a wrong answer to the end. Complements the mechanism-layer loop skills (autonomous-loops, continuous-agent-loop) by covering the judgment layer they don't. 中文触发：写 loop、设计 loop、做一个 loop、检查 loop 对不对、loop 体检、loop 会不会跑飞、可判定目标、五个崩法、plan build judge。English triggers: design an agent loop, write a loop, check a loop, loop review, prevent a runaway loop, goal-oriented loop, decidable goal, plan/build/judge.
The full lifecycle for agentic loops — recurring, scheduled AI agents packaged as a portable LOOP.md (the agenticloops.dev standard: a trigger + skills + a prompt in one file any harness can install and run on a schedule). Use this whenever the user wants to FIND, INSTALL, RUN, or BUILD a loop: "find a loop for X", "is there a loop that…", "install a recurring agent that does X", "run this loop", as well as "create a loop", "make an agentic loop", "write a LOOP.md", "turn this into a recurring agent", "schedule an agent", "set up a cron job for an agent", or any description of a repeating job they want an agent to do on a timer (a daily digest, a competitor watcher, a triage sweep, a report pipeline, "email me X every morning", "check Y every hour") — even if they never say the word "loop". Always search the directory first and install an existing loop when one fits; author a new LOOP.md only when nothing does. This is the loop-level analogue of skill-creator + find-skills combined. For an ad-hoc in-session multi-agent run (spawn, verify, panel, fan-out) use the `loops` skill instead; for authoring a reusable SKILL.md use skill-creator.
Spawn parallel adversarial subagents that DRIVE THE REAL SYSTEM (not reason from source) to break new code before it ships — schemas, contracts, parsers, serializers, protocols, state machines, security/redaction, freeze guards. Use as a standard step on any nontrivial feature/task once the implementation is green and BEFORE the final convergence (dootsabha) review. Each agent gets one disjoint attack surface + a "try to break X" charter; every finding is independently reproduced before it is believed, then fixed with a regression test. Trigger phrases include "adversarial review", "try to break this", "find the bugs I missed", "harden before done", "attack this schema/parser/contract", and the shux feature-protocol adversarial step.
Run bounded, evidence-driven training research through W&B Launch: assess project readiness, establish launchable code and queue capacity, smoke-test real jobs, execute serial trials, compare metrics, and persist resumable research state. Use when a coding agent is asked to autonomously test training hypotheses or tune a real W&B-tracked workload.
Use when deciding where knowledge goes or reading/writing durable docs: AGENTS.md, .context/, KB, docs/, and work directories.
Agent Session Visualization / Session Timeline: Execution maps for Cursor, Codex, Claude Code, Workbuddy, kimi-code threads (by ID or name); includes skills/tools/sub-agents, retries/forks/waits, layered internationalization + session health. Triggers (English): agent thread visualizer, agent-thread-visualizer, agent session timeline, session report, session log analyzer, agent flow visualization, execution map, conversation visualizer, subagent timeline, debug agent session, visualize the run, Cursor session, Claude Code session, Workbuddy session, kimi-code session. (Chinese): agent session visualization, session visualization, agent timeline, sub-agent visualization, session report, session analysis, execution map, agent execution flow, debug agent session, Cursor session, Claude Code session, Workbuddy session, kimi-code session. (Japanese): agent session visualization, session visualization, agent timeline, sub-agent visualization, session report, execution map, agent execution flow, Cursor session, Claude Code session, Workbuddy session, kimi-code session.
How to reach IntelliStory from any agent: the `intellistory` CLI (install, sign in, pick a project, call ANY tool with schema-checked options, upload/download media, connect Claude/Codex/Cursor/Gemini/Hermes) and the same tools over MCP. Load this first when a task mentions IntelliStory, a project code (HGRD, sq010_sh0020), shots, storyboards, looks, generation, or "put this render on the shot". Other intellistory-* skills assume this one: they name tools; this one says how to call them.
Write or refresh a "Tech debt operations" section in the project's AGENTS.md so the team shares one source of truth for debt-ops disciplines. Run ONLY when the user explicitly asks to set up, install, or initialize debt-ops disciplines — never auto-invoke. Idempotent; only the managed section changes, other sections are untouched.