Loading...
Loading...
Found 50 Skills
The orchestrator's discipline - delegate the work, trust delegates to build and verify it, and be the user's one contact. Use when coordinating tickets across agents, when asked to orchestrate, or when another skill says to.
Run independent code-review agents and synthesize verified findings.
Monitor an open GitHub PR every two minutes, optionally use Copilot review, resolve feedback, and request human review only when ready for merge or blocked.
Builds bespoke motion graphics for an edit, one animated clip per beat (HyperFrames + GSAP), each designed for its line and landing on the spoken word, then lays them on the footage through the style-edit render. Picks the beats that need motion (a count, a list, a flow, a before and after, a run, a mechanism), writes a brief per clip, runs one clip-builder agent per clip at once, gates every clip (lint, layout, render, a frame-to-frame motion check, contact sheets), and falls back to the template card for a clip that fails. Use when the user says "animation", "motion graphic", "animate this", "animate the part where I say X", "make a clip for", "build the animations", or when style-edit or visual-prep reaches the beats that need motion. Not for captions or zooms (style-edit), not for real screenshots and logos alone (overlays), not for a product demo film (product-video).
Use for decomposing features into tasks and research questions.
Orchestrate bounded Codex, Claude Code, Agy, Kimi, or custom CLI workers to finish work with the least lead context and provider usage, following playbooks such as plan big, execute small. Use when the user asks to orchestrate, delegate, compare agents, conserve agent tokens or quota, recover a worker, report what an orchestration did and cost, or work without MCP or Python, when the user types /alethe or a short command such as "alethe report" or "alethe stop", and when they want it on from now on, at any point of a task and alongside other skills. Also use it proactively, without being asked, when a request is large enough to split into bounded independent units, such as a multi-file refactor, a migration, an audit or research across many files. Do not use for a small mechanical task unless explicitly requested.
Map who a person knows from one LinkedIn profile URL, when you cannot see their connection list. Derives a per-person angle set from their own work history, education and posts, fans those angles out to parallel agents, merges and scores every candidate on evidence strength, resolves each row to a real profile and current employer, and ships a spreadsheet you can slice by where each person works today (a filterable people tab plus an employer x tier pivot). Works for any function (engineering, recruiting, sales, research, exec) and any career shape. Use for "who does this person know", "find connections of this LinkedIn URL", "map this person's network", "who is in their orbit", "who do they know at a company", "infer connections from job history and post engagement", /social-connections.
Summon shadow clones: genjutsu's full-scale pipeline for a whole website or web app, from scratch or as a full redesign. Harvests the client's real material, researches in parallel, lets Impeccable lead the direction and genjutsu the motion, builds the pages with parallel agents, then loops fixes, verdicts and a cold-eyes art director until only minor issues remain, the round cap of the chosen tier is reached, or a round fixes nothing. Announces its cost first and asks twice. Web. Needs a host that can spawn subagents.
Multi-perspective academic paper review with dynamic reviewer personas. Simulates 5 independent reviewers (EIC + 3 peer reviewers + Devil's Advocate) with field-specific expertise. Supports full review, re-review (verification), quick assessment, methodology focus, Socratic guided, and calibration modes. Triggers on: review paper, peer review, manuscript review, referee report, review my paper, critique paper, simulate review, editorial review, calibrate reviewer, reviewer calibration, measure reviewer accuracy.
Batch several `/gsd-quick`-shaped tasks together — planned, dispatched, and merged as one run
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).
Plan and hand over work as the main invoker.