agentsclimarketplace

Claude complex tasks

Skill echohello-dev/skillet/skills/claude-complex-tasks

CLI to pull Agent Skills anywhere, anytime

Install
npx -y skills add echohello-dev/skillet --skill claude-complex-tasks

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Guide Claude on complex, multi-step tasks by enforcing structured discovery, scoped planning, and verification before delivery.

SKILL.md

1.8 KB, 355 tokens by cl100k_base, as published. Nobody here has run it

Claude Complex Tasks

Use this skill when the task is complex, multi-step, or ambiguous and needs careful planning, validation, or staged delivery.

When to Use

  • The request spans multiple subsystems or files.
  • The outcome depends on external constraints (CI, build, integrations).
  • The task is risky, irreversible, or requires high accuracy.

Approach

  1. Clarify scope

    • Restate the goal in one sentence.
    • List assumptions and missing inputs.
    • Ask only one focused question if blocked.

  2. Plan the work

    • Break into 3-7 steps with clear outcomes.
    • Identify dependencies (tools, files, environment).
    • Decide what can be done in parallel.

  3. Gather context

    • Locate relevant files and read them first.
    • Verify conventions and existing patterns.
    • Identify edge cases and constraints.

  4. Execute in stages

    • Make smallest safe change to prove direction.
    • Iterate with tests or quick checks.
    • Keep changes scoped to the request.

  5. Verify

    • Run requested tests or minimal validation.
    • Confirm behavior against acceptance criteria.
    • Note any remaining risks.

  6. Close the loop

    • Ensure PR and issue linkage is explicit when applicable.
    • Merge only after required checks pass.
    • Confirm outcomes are reflected in docs/status where needed.

  7. Report

    • Summarize what changed and where.
    • Call out any decisions or tradeoffs.
    • Suggest next steps if needed.

Output Expectations

  • Prefer concise, structured updates.
  • Avoid long dumps of code; reference files instead.
  • Keep decisions explicit and traceable.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 327,069. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.