SkillAgentSearch skills...

dorodango

Polishes working code through successive quality passes in fresh subagents. Use after tests pass when code needs multi-dimension refinement before release.

Install / Use

npx skills add athola/claude-night-market --skill dorodango

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

83/100

Category

Automation

Supported Platforms

Universal

Tags

Our assessment of dorodango

dorodango scores 83/100 on our quality scale, 2224th of 2,771 Automation skills we index.

Its SKILL.md is 5.0 KB long, well organised into 10 sections with 1 code example: a solid amount of guidance for an agent.

It has 338 GitHub stars, a meaningful sign that others use it.

Substance
26/30
Structure
17/20
Description
15/15
Adoption
11/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so dorodango is actively maintained.
  • Our last check on 2026-11-07 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

dorodango compared with similar skills

All 4 of these similar skills score higher than dorodango; compare them before choosing.

SkillScoreStarsUpdatedFormat
dorodango (this skill)by athola8333857d agoSKILL.md
Agent-Reachby Panniantong100113.3k12d agoCLAUDE.md
rufloby ruvnet10082.1ktodayCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10040.2k10d agoCLAUDE.md
Scraplingby D4Vinci100104.4k2d agoMCP Server

Frequently asked questions

How do I install dorodango?
Run npx skills add athola/claude-night-market --skill dorodango. The install tabs above show the steps for each supported agent.
Which AI agents does dorodango work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is dorodango safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is dorodango still maintained?
The repository was last updated about 2 months ago, so dorodango is actively maintained.

name: dorodango description: Polishes working code through successive quality passes in fresh subagents. Use after tests pass when code needs multi-dimension refinement before release. alwaysApply: false category: workflow tags:

  • polishing
  • iterative-refinement
  • code-quality
  • convergence progressive_loading: true dependencies: hub: [] modules:
    • modules/pass-definitions.md complexity: intermediate model_hint: standard estimated_tokens: 400

Dorodango Polishing Workflow

Named after the Japanese art of polishing a ball of dirt into a high-gloss sphere. Applied to code: take the initial implementation (the "mud ball") and refine it through successive quality passes until it shines.

When To Use

  • After initial implementation is complete and tests pass
  • Code works but needs refinement across multiple quality dimensions
  • Preparing code for review or release
  • Resuming a previous polishing session

When NOT To Use

  • Code does not compile or pass basic tests (fix first)
  • Single-dimension improvement needed (use the specific skill directly: pensive:code-refinement, etc.)
  • Greenfield design phase (use brainstorming instead)

Pass Sequence

Four quality dimensions, each a self-contained pass:

  1. Correctness - run tests, fix failures
  2. Clarity - code readability and structure
  3. Consistency - naming, patterns, style alignment
  4. Polish - documentation, error messages, edges

See modules/pass-definitions.md for detailed scope of each pass type.

Convergence Model

  • Each pass targets one dimension
  • A dimension converges on a record, never on the passing subagent's own count alone: correctness on the test command's exit code, clarity and consistency on the linter and formatter exit codes plus a reviewer count of 0, polish on a reviewer count of 0 from a fresh subagent that did not make the edits
  • A pass that reports issues_found: 0 without the matching exit code recorded in the state file has not converged
  • Convergence is reversible: a later pass that finds a regression in a converged dimension un-converges it, and that dimension is re-run before the run completes
  • When all 4 dimensions converge, polishing is complete
  • Maximum 10 total passes (hard limit)
  • If not converged after 10 passes, surface state to human with recommendation to split into smaller units

State Persistence

State tracked in .attune/dorodango-state.json:

{
  "target": "plugins/foo",
  "started_at": "2026-03-18T12:00:00Z",
  "pass_count": 3,
  "passes": [
    {
      "type": "correctness",
      "issues_found": 2,
      "issues_fixed": 2
    },
    {
      "type": "clarity",
      "issues_found": 5,
      "issues_fixed": 5
    },
    {
      "type": "consistency",
      "issues_found": 0
    }
  ],
  "converged_dimensions": ["consistency"],
  "converged": false
}

This file enables resume across sessions. On resume, skip converged dimensions and continue from the next unconverged dimension.

Subagent Isolation

Each pass dispatches a self-contained subagent to prevent context accumulation. The subagent receives:

  • Target directory/files
  • Pass type and scope (from pass-definitions module)
  • Previous pass results (summary only, not full context)

Subagent dispatch is optional for targets under 100 lines of code; in-session review is sufficient for small files.

Workflow

  1. Initialize state file (or load existing)
  2. Determine next unconverged dimension
  3. Dispatch subagent for that dimension
  4. Record results in state file
  5. If dimension converged (0 issues), mark it
  6. If all dimensions converged or 10 passes reached, stop
  7. Otherwise, proceed to next dimension

Cross-References

  • pensive:code-refinement - used in clarity pass
  • conserve:code-quality-principles - KISS/YAGNI/SOLID
  • imbue:latent-space-engineering - frame pass prompts with emotional framing for better results

Exit Criteria

  • [ ] .attune/dorodango-state.json exists with "converged": true and all four dimensions (correctness, clarity, consistency, polish) listed under converged_dimensions.
  • [ ] Total pass_count in the state file is <= 10; if 10 passes complete without full convergence, the skill surfaces the unconverged dimensions to the user with a recommendation to split the target into smaller units.
  • [ ] The correctness dimension converges only after all tests pass (exit code 0); a correctness pass that finds failing tests never marks the dimension as converged.
  • [ ] Clarity and consistency converge only with the linter and formatter exit codes recorded as 0 in the state file beside the reviewer's count; a 0 issues claim with no exit code does not converge a dimension.
  • [ ] A regression found in a later pass un-converges its dimension in the state file (converged_dimensions shrinks), and the dimension is re-run before converged: true.
  • [ ] Each pass is dispatched as a separate subagent for targets over 100 lines, confirmed by the state file recording individual pass results rather than a single bulk entry.

Related Skills

View on GitHub
GitHub Stars338
CategoryAutomation
Updated1mo ago
Forks35

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions