New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Analyze Task

by yusifeng in yusifeng/formax

A skill your agent uses when a Formax repository task is non-trivial and you should analyze goals, non-goals, boundaries, data/type/interface impact, contract impact, test strategy, and whether an…

MITAuto-check passedTesting & QA

Install Analyze Task

skills CLI
$ npx skills add yusifeng/formax --skill analyze-task -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install yusifeng/formax analyze-task --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/yusifeng/formax.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/analyze-task .claude/skills/analyze-task && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
analyze-task
GitHub stars
195
Token cost
~1.2k tokens
SKILL.md length
571 words
Files
1
Skills in repo
21
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when a Formax repository task is non-trivial and you should analyze goals, non-goals, boundaries, data/type/interface impact, contract impact, test strategy, and whether an…

  • Works in 5 steps: Prioritize structure before UI → Prefer explicit boundaries → Use subagents selectively → …
  • A Formax repository task is non-trivial and you should analyze goals
  • SKILL.md covers Purpose, Core rules, Required output and Section guidance, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Analyze Task is an agent skill from yusifeng/formax. Use when a Formax repository task is non-trivial and you should analyze goals, non-goals, boundaries, data/type/interface impact, contract impact, test strategy, and whether an xhigh subagent is actually needed before writing a todo or code.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering Test strategy and Subagents. The repository describes itself as: Terminal-first AI assistant for software engineering tasks (inspired by Claude Code v2.0.67). The licence is MIT.

When your agent uses it

  • A Formax repository task is non-trivial and you should analyze goals
  • Data/type/interface impact
  • Contract impact
  • Whether an xhigh subagent is actually needed before writing a todo

Example prompts

  • “/analyze-task”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Prioritize structure before UI
  2. Prefer explicit boundaries
  3. Use subagents selectively
  4. Do not create a canonical doc yet unless the concept is already clearly stable and long-lived
  5. Every analysis should end with an alignment state

What it can do on your machine

Read from SKILL.md and the folder at commit 1b0c3f3. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Analyze Task loads about 1.2k tokens when it runs. Until then it costs about 64 tokens; SKILL.md has 571 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~64
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from yusifeng/formax at commit 1b0c3f3, republished under its MIT licence (© yusifeng). 571 words, ~1,194 tokens.

Download SKILL.mdSave it as .claude/skills/analyze-task/SKILL.md (or your agent's skills folder).
name
analyze-task
description
Use when a Formax repository task is non-trivial and you should analyze goals, non-goals, boundaries, data/type/interface impact, contract impact, test strategy, and whether an xhigh subagent is actually needed before writing a todo or code.

Analyze Task

Use this skill before coding for non-trivial repository work:

  • new features
  • cross-layer changes
  • architecture or model changes
  • complex bugs
  • tasks that likely need multiple commits / reviews / loops

Do not use it for tiny local edits that can be implemented and verified immediately.

Purpose

Produce a short Analysis Brief that makes the task discussable and executable.

This skill is for:

  • clarifying the goal
  • defining non-goals
  • identifying what must be decided before coding
  • deciding whether a subagent is justified
  • preparing the task for a scope-alignment discussion
  • setting up the handoff to write-task-todo only after alignment

This skill is not for writing code and not for writing docs/todolist.md.

Core rules

  1. Prioritize structure before UI

    • think about canonical docs/contracts, data model, types, interfaces, repo/service/runtime boundaries before UI details

  2. Prefer explicit boundaries

    • say what is in scope and what is not
    • surface ambiguity instead of silently choosing

  3. Use subagents selectively

    • default is local analysis
    • use an xhigh explorer subagent only when the task is cross-layer, ambiguous, high-risk, or likely to benefit from an independent architectural read
    • if you use a subagent, give it a narrow question; do not outsource the entire solution

  4. Do not create a canonical doc yet unless the concept is already clearly stable and long-lived

    • early definitions belong in analysis/todo first

  5. Every analysis should end with an alignment state:

    • ready for alignment discussion
    • ready for write-task-todo after confirmation
    • or blocked on a single clarification

Required output

Produce a brief with these sections:

md
## Analysis Brief

### Goal

### Product Boundary

### Scope

### Non-goals

### Canonical-Doc Impact

### Data / Type / Interface First

### Layer Impact

### Risks / Ambiguities

### Need Subagent?

### Test Strategy

### Alignment Questions

### Ready for Todo?

Section guidance

Goal
  • one concise sentence
Product Boundary
  • say whether the center of gravity is product, platform, or both
Scope
  • list what this task must accomplish
Non-goals
  • list what this task must not expand into
Canonical-Doc Impact
  • identify whether an existing canonical doc already governs this area
  • in Formax, prefer checking docs/contracts/*, docs/frontend/*, docs/environment-variables.md, CODEMAP.md, and package-local README deep dives
  • if yes, say which doc(s) govern the area
  • if not, say whether this task is likely to need a new canonical doc later
Data / Type / Interface First
  • identify the definitions that should be settled before implementation
  • examples:
    • payload shape
    • DTOs
    • repo interfaces
    • service boundaries
    • route contracts
    • surface/view state
Show full SKILL.md (216 more words)Show less
Layer Impact
  • name affected layers as applicable:
    • core
    • contracts
    • db
    • app
    • routes
    • schema
    • repo
    • service
    • runtime
    • ui
Risks / Ambiguities
  • call out the likely failure modes or places where the task could go structurally wrong
  • in Formax, explicitly consider parity drift, transcript/reset semantics, prompt/tool exposure drift, and thread/runtime state ownership when relevant
Need Subagent?
  • answer yes or no
  • if yes, explain exactly what question the subagent should investigate
Test Strategy
  • identify what should be framed by tests first
  • prefer focused tests over blanket integration-first thinking
  • match Formax's repo guidance: targeted tests first, no coverage runs, protect user-visible behavior and runtime semantics
Alignment Questions
  • list the decisions or tradeoffs that should be explicitly confirmed before writing docs/todolist.md
  • if there are no meaningful open questions, say so directly
Ready for Todo?
  • answer whether the task should proceed into write-task-todo
  • default to no if important scope, boundary, or semantics questions are still open

Handoff rule

Do not treat this skill as an automatic handoff to write-task-todo.

The normal sequence is:

  1. produce the Analysis Brief
  2. discuss and align the analysis with the user
  3. only then hand off to write-task-todo

If the task is non-trivial and the analysis is already aligned, hand off to write-task-todo.

If the task is trivial, explicitly say that a structured todo is not needed.

© yusifeng, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .codex/skills/analyze-task of yusifeng/formax.

Open the folder on GitHubat commit 1b0c3f3

Compare with similar skills

Analyze Task next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Analyze Task compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Analyze Task this skillyusifeng/formax195—~1.2kAutomated safety check: PassMIT
Output Plan Workflowgrowthxai/output440—~2.1kAutomated safety check: PassApache-2.0
Libreqos Review Subagents WorkflowLibreQoE/LibreQoS718—~1.2kAutomated safety check: PassGPL-2.0
Testing Skills With Subagentsed3dai/ed3d-plugins2502 repos~3.5kAutomated safety check: PassNone
StandardsItamarZand88/CLI-Anything-WEB231—~4.2kAutomated safety check: PassMIT
Dev ReviewFHIR/fhir-codegen154—~5kAutomated safety check: PassMIT

Similar skills

  • Output Plan Workflow

    growthxai/output

    A skill your agent uses when the user asks to create, build, generate, scaffold, or plan a new workflow.

    440 GitHub stars~2.1k tokensUpdated yesterday
    Testing & QAAuto-check passed

  • Libreqos Review Subagents Workflow

    LibreQoE/LibreQoS

    Project workflow for invoking the local review sub-agents Thomas, Helen, Beck, Jonas, The Reaper, and Heckler during LibreQoS coding sessions.

    718 GitHub stars~1.2k tokensUpdated 3 days ago
    Testing & QAAuto-check passed

  • Testing Skills With Subagents

    ed3dai/ed3d-plugins

    A skill your agent uses when creating or editing skills, before deployment, to verify they work under pressure and resist rationalization - applies RED-GREEN-REFACTOR cycle to process documentation…

    250 GitHub starsUsed in 2 repos~3.5k tokens
    Testing & QAAuto-check passed

  • Standards

    ItamarZand88/CLI-Anything-WEB

    Runs Phase 4 review/publish/verify for a cli-web- CLI: implementation review by 3 parallel agents, the tiered quality checklist (Tier 1 critical fail-fast, then comprehensive), pip install + smoke…

    231 GitHub stars~4.2k tokensUpdated 6 days ago
    Testing & QAAuto-check passed

  • Dev Review

    FHIR/fhir-codegen

    Performs a two-track code-quality and QA review in the roles of a staff-level Engineering Lead and QA Lead, then synthesizes both critiques into a single analysis.md.

    154 GitHub stars~5k tokensUpdated 1 mo ago
    Testing & QAAuto-check passed

  • Next QA Idea

    breaking-brake/cc-wf-studio

    Runs one unattended ideation pass of a QA loop: finds the highest-value untested behavior and files a single locked qa issue describing the test to write, with no code.

    5.4k GitHub stars~1.7k tokensUpdated yesterday
    Testing & QAAuto-check passed

More from yusifeng/formax

All 21 skills in this repo

  • Formax Repomix Handoff Workflow

    yusifeng/formax

    A skill your agent uses when preparing a Formax code handoff: selecting files, generating repomix bundles, and writing a high-quality prompt for WebGPT or another coding agent with clear constraints…

    195 GitHub stars~1.2k tokensUpdated 2 mo ago
    Auto-check passed

  • Formax Skill Capture

    yusifeng/formax

    A skill your agent uses when we want to turn a just-finished Formax workflow (e.g.

    195 GitHub stars~530 tokensUpdated 2 mo ago
    Auto-check passed

  • Formax Dev Loop Workflow

    yusifeng/formax

    A skill your agent uses when working on Formax code changes and you need a disciplined dev loop: keep a single mainline task, avoid scope drift, run only targeted tests (no coverage), avoid partial…

    195 GitHub stars~686 tokensUpdated 2 mo ago
    Auto-check passed

  • Formax Tool UI Blocks Workflow

    yusifeng/formax

    Implement or refactor Formax tool transcript UI using the Tool UI Blocks (C-lite) pattern (ToolUiBlocks renderer + blocks presenters) to avoid touching many tool presenter files; use when adjusting…

    195 GitHub stars~1.3k tokensUpdated 2 mo ago
    Auto-check passed

  • Formax Semantics Parity Workflow

    yusifeng/formax

    A skill your agent uses when implementing or modifying behavior that must stay consistent across TUI and Web (mode/input/tool/replay/order).

    195 GitHub stars~1.1k tokensUpdated 2 mo ago
    Auto-check passed

  • Formax System Prompt Workflow

    yusifeng/formax

    A skill your agent uses when designing, refactoring, or debugging Formax system prompt assembly, system-reminder injection, or skills/deferred-tool prompt exposure semantics; mandatory for any…

    195 GitHub stars~1k tokensUpdated 2 mo ago
    Auto-check passed

Categories

Questions about Analyze Task

What does Analyze Task do?

A skill your agent uses when a Formax repository task is non-trivial and you should analyze goals, non-goals, boundaries, data/type/interface impact, contract impact, test strategy, and whether an…. Analyze Task is an agent skill from yusifeng/formax. Use when a Formax repository task is non-trivial and you should analyze goals, non-goals, boundaries, data/type/interface impact, contract impact, test strategy, and whether an xhigh subagent is actually needed before writing a todo or code.

When should I use Analyze Task?

Analyze Task fits situations like: A Formax repository task is non-trivial and you should analyze goals; data/type/interface impact; contract impact; whether an xhigh subagent is actually needed before writing a todo.

How do I install Analyze Task in Claude Code?

Run `npx skills add yusifeng/formax --skill analyze-task -a claude-code`. Or copy the skill folder (.codex/skills/analyze-task in yusifeng/formax) into .claude/skills/analyze-task in your project. Claude Code loads it when a task matches its description.

How do I install Analyze Task in Codex?

Run `npx skills add yusifeng/formax --skill analyze-task -a codex`. Or copy the skill folder (.codex/skills/analyze-task in yusifeng/formax) into .agents/skills/analyze-task in your project. Codex loads it when a task matches its description.

Can I use Analyze Task in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add yusifeng/formax --skill analyze-task -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/analyze-task, .gemini/skills/analyze-task, .github/skills/analyze-task and .opencode/skills/analyze-task in your project.

What does Analyze Task need to run?

SKILL.md names no scripts, command-line tools or credentials: Analyze Task is instructions for the agent only.

Does Analyze Task access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Analyze Task safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Analyze Task use?

Analyze Task is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Analyze Task use?

About 1.2k tokens (SKILL.md is roughly 4.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Analyze Task?

Skills that share tags, products or a category with Analyze Task: Output Plan Workflow (growthxai/output, 440 stars), Libreqos Review Subagents Workflow (LibreQoE/LibreQoS, 718 stars), Testing Skills With Subagents (ed3dai/ed3d-plugins, 250 stars) and Standards (ItamarZand88/CLI-Anything-WEB, 231 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Analyze Task?

yusifeng (a GitHub user) maintains it in yusifeng/formax, which has 195 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on July 24, 2026.

Source: yusifeng/formax on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.