Results for “try-on”

Run multiple AI agents against a product, SDK, or docs site to score setup friction, speed, efficiency, error recovery, and doc quality from a minimal prompt.

Runs commands, inspects git state, debugs CI failures, and makes narrow fixes with exact proof of what was executed and verified.

Evidence-first repo execution workflow for ECC. Use when the user wants a command run, a repo checked, a CI failure debugged, or a narrow fix pushed with exact proof of what was executed and verified.

Organizes email triage, drafting, replying, and sending with verification that messages landed in the Sent folder.

Executes terminal commands, inspects git state, debugs CI or builds, and makes narrow fixes with exact proof of what was executed and verified.

Rereads code, specs, plans, reviews, or skill edits with fresh eyes to catch blunders, oversights, and omissions before closure, reporting concrete evidence-backed findings.

Organizes email triage, drafting, sending, and verification workflows with evidence-first reporting for mailbox operations.

Look up and apply the cooked, indexed proof playbook built from proof-material. Use when the user is proving a theorem, planning a proof, seeking reusable proof moves by task shape, assumptions, tags, desired move, or material source ID, or adapting cooked local moves and macro strategies with public source attribution.

Evidence-first mailbox triage, drafting, send verification, and sent-mail-safe follow-up workflow for ECC. Use when the user wants to organize email, draft or send through the real mail surface, or prove what landed in Sent.

Evidence-first mailbox triage, drafting, send verification, and sent-mail-safe follow-up workflow for ECC. Use when the user wants to organize email, draft or send through the real mail surface, or prove what landed in Sent.

Refines an existing skill in place with minimal diffs, using evidence from usage and session mining to improve triggers, workflow, metadata, and resources.