Skill Codex
Use when the user explicitly wants to discuss, brainstorm, compare options, or make a material preference decision, or when unclear intent needs guided clarification; do not use for clear execution or a single discoverable detail.
Skill Codex
Use when a failure, regression, crash, flake, or unexpected result has an unknown cause that must be diagnosed before a safe fix; do not use when the cause and narrow fix are already clear.
Skill Codex
Use when the user explicitly asks to persist until a verifiable result, fix until green, monitor through completion, or stay within a stated budget; do not infer persistence from difficulty.
Skill Codex
Use when the user asks to add or refresh concise project-local Teamwork instructions in one named project; do not use to install global tools or create workflow records.
Skill Codex
Use when the user asks for an implementation plan, task breakdown, checklist, roadmap, or handoff and the outcome and direction are already selected; do not use to choose the direction or execute changes.
Skill Codex
Use when a broad or deep external investigation needs multiple source classes, claim-level evidence synthesis, or contradiction resolution; do not use for a narrow lookup or local code inspection.
Skill Codex
Use when the user asks to review, audit, critique, or validate a stable code, document, plan, artifact, or claim; do not use to diagnose an unknown failure or create the initial candidate.
Skill Codex
Use when the user asks to inspect, install, or refresh Teamwork-owned global surfaces; do not use as a prerequisite for another skill or to migrate project documents.
JinPLu/clear-eyed-reading-skills
Skill Codex
Deeply read a research paper, review, technical blog, commentary, or other long technical work so the reader can retell, redraw, reuse, and challenge it, through a plain-language rebuild of the problem and mechanism with text diagrams and one worked example carried through every step, key equations with numbers…
JinPLu/clear-eyed-reading-skills
Skill Codex
Quickly explain a research paper, review, technical blog, commentary, or other article in plain language, covering what it actually does once names and branding are stripped away, how the method works through a text diagram and one worked example, what is really new versus earlier work, where its ability comes from…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: