agentleFS
DataArtDataArt/artisyn-implementation-harness/.claude/skills/evolve/SKILL.md

evolve

Skill9 starsChanged 47 days agoMITView on GitHub

Improve harness skills, agents, workflows, and conventions from observed friction or a concrete improvement request. Supports reflect, triage, validate, and adopt; use for harness improvements rather than ordinary product changes.

43 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use instinct-export, instinct-import and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • TheKREATORSSkill

    instinct-export

    Export instincts from project/global scope to a file

    Also in 4 projects that use this

  • TheKREATORSSkill

    instinct-import

    Import instincts from file or URL into project/global scope

    Also in 4 projects that use this

  • AWSSkill

    map

    Map verified service capabilities against customer-provided control framework and threat model. Produces mapping-results.json, controls-catalog.md, and framework-mapping.md. Supports pluggable frameworks: CCMv4, NIST 800-53, CIS Benchmarks, ISO 27001, etc. Split into 4 focused sub-skills for better accuracy; this skill orchestrates them.

    Also in 5 projects that use this

  • diego-tobalinaSkill

    build-fix

    Fix build and compilation errors systematically. Run when build fails.

    Also in 3 projects that use this

  • launch52-aiSkill

    skill-create

    Create and validate Claude Code skills with proper structure, checklists, and validation scripts. Use when creating a new skill, auditing existing skills, or ensuring skills meet quality standards. Generates complete skill scaffolds with SKILL.md, check scripts, guides, and templates.

    Also in 3 projects that use this

  • qtzx06Skill

    eval

    Evaluate trained YOLO model accuracy with mAP metrics and per-class error analysis. Identifies failure cases for targeted improvement. Use after training.

    Also in 5 projects that use this

  • +1 more from TheKREATORS

The file

Files
SKILL.md

Evolve

Turn observed practice into a validated, integrated harness improvement.

Route $ARGUMENTS with the stage router. Load only the current stage, its required interfaces, and relevant source files. Bare /evolve triages pending reflections; clarify the candidate when several match. Reflect is a capture-only operation. An explicit stage runs that stage only. Triage includes drafting and stops with inactive candidates by default. Validation and adoption run when requested. There is no session-continuation or automatic phase-resumption protocol.

For candidate work, apply native task tracking. Record decisions and evidence in the candidate report before a handoff. File presence alone does not prove completion.

Existing user authorization governs execution. Request acceptance of the concrete candidate before adoption unless already authorized. Preserve project-specific instructions and respect the selected provider's paths and root instruction file.

The lifecycle ends with verified local adoption.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.