Explore skills

Use when choosing the FORMAT of an output, not just its verbosity — match the medium (text, markdown, HTML dashboard, PPTX, DOCX) to the consumer's actual use mode. Operator-specific extension: also covers length calibration for different contexts. Outside scope is video (requires autovideo pipeline — too heavy to be native capability). The chengyu is about teaching with the right material, where

Use when at or near the 80% mark of a deliverable and the temptation is to keep polishing past good-enough. The 80/20 rule encapsulated — the last 20% of polish often consumes 80% of remaining time and rarely changes the operator's decision. Distinguished from chengyu-retreat-is-best (abandon FAILED approach) and from chengyu-great-wisdom-looks-foolish / chengyu-words-concise-meaning-complete (res

SUBAGENT-ONLY skill for generating a graduated spread of plausible-to-speculative solutions when the main agent is stuck in a local minimum. Output is one continuous artifact (NO dividers) that starts from verified fact and slides into bottom-K speculation; calling main-agent fact-checks throughout. Has TWO HARD PRECONDITIONS that must be met before any output: (1) running on a BullshitBench-passi

Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.

Benchmark a skill's quality by analyzing its structure, description, documentation, and live value-add from multiple perspectives using parallel agents. Use when the user asks to benchmark, evaluate, score, audit, assess, or rate a skill's quality, or wants to know if a skill is worth keeping vs. deprecating. Also trigger when the user asks "how good is this skill", "is this skill useful", "should

Use when the user encountered a problem, bug, edge case, or frustration with an existing skill and wants to save that knowledge into the skill's file. Trigger phrases include "add a gotcha", "document this pitfall", "capture lessons learned", "record edge cases", "pull out what went wrong", but also trigger when the user simply describes something that went wrong or was painful with a named skill

Use after planning and before execution to verify approved current work is reality-fit, feasibility-ready, and explicitly approved at Gate 3.

Use when bootstrapping or resuming work in a Pulse project after pulse:preflight, or when a request needs Pulse work-shape/current-work routing and mode-aware skill selection.

Use after pulse:validating approves execution and swarm mode is recommended, when the current work slice should be run by coordinated parallel workers.

Targeting suitable journals and conferences for a manuscript, along with managing subsequent submission and revision workflows, including author guidelines, format checks, revision planning, reviewer triage, and response letters.

Use after execution completes when the user needs final quality verification and release-readiness review before closeout.

Use when starting any Pulse workflow, resuming a Pulse session, or before planning or execution when tool readiness or onboarding state may block the flow.