Skip to content
Skills Library
AI & agents · Building & coding

self-evolving-single-agent

/self-evolving-single-agent

Use when generating a single installable agent that should keep learning, track sources, refresh research, propose repairs, or improve itself over time without becoming a multi-agent team.

Repository
Agentlas-OS ↗
Licence
Apache-2.0
Last repository change
25.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Use when generating a single installable agent that should keep learning, track sources, refresh research, propose repairs, or improve itself over time without becoming a multi-agent team.

Original author description

Use when generating a single installable agent that should keep learning, track sources, refresh research, propose repairs, or improve itself over time without becoming a multi-agent team.

How it works

  1. Procedure
  2. Output
  3. File revision approval
Original SKILL.md headings · 44 lines, 247 words
SKILL.md preview
---
name: self-evolving-single-agent
description: "Use when generating a single installable agent that should keep learning, track sources, refresh research, propose repairs, or improve itself over time without becoming a multi-agent team."
---

# Self-Evolving Single Agent

## Procedure

1. Keep the package as one worker unless the user asks for a team.
2. Run `contracts/builder-interview-research-gate.md` before generation: ask an
   8-12 question first batch, research official sources, similar agent
   repositories or comparables, academic/professional theory, and plugin docs,
   compare tool/plugin choices, and write the domain-expert synthesis plus
   prompt-performance contract before creating the worker prompt.
3. Add memory architecture even for the single worker:
   - `.agentlas/memory-map.json`;
   - `.agentlas/vault-references.json`;
   - project memory owned by PM Soul/project owner;
   - Memory Events and Memory Tickets for durable updates.
4. If the task depends on current sources, add a research-refresh command,
   watchlist memory section, references, and optional scheduled workflow.
5. Add `docs/builder-interview.md`, `docs/research-sources.md`,
   `docs/tool-selection.md`, `docs/domain-expert-synthesis.md`,
   `docs/prompt-performance-contract.md`, and
   `.agentlas/capability-eval-plan.json` unless explicitly creating a minimal
   private scaffold.
6. Make self-evolution proposal-first: draft patches or repair kits, then wait
   for human approval before changing tools, connectors, secrets, or core
   instructions.
7. Add `.agentlas/global-commands.json` and one public global command for the
   worker across Claude Code, Codex, Antigravity, generic AGENTS.md, and
   terminal adapters.

## Output

Return `agent_package`, `skills`, `memory_contract`, `refresh_loop`,
`approval_gate`, `global_commands`, and `verification`.

## File revision approval

Private memory curation is autonomous. Every instruction, skill, tool, or manifest
change requires a real staged multi-file diff, current source evidence, and an
exact one-use owner approval receipt. Never treat a summary, low-risk label,
Curator verdict, shell flag, or legacy chip as approval. Project memory requires
a separately curated agent_repo candidate before proposal preparation. Use
revision-v1/evolution-v2 host capabilities; block activation on older hosts.

Versions

RepositoryScoreLicence
This page · agentlas-ai/Agentlas-OS90Apache-2.0
agentlas-ai/Agentlas-OS90Apache-2.0

Identical content appears in 4 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 684a216a7243 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 95evolving-ai-agents
    Provides guidance for automatically evolving and optimizing AI agents across any domain using LLM-driven evolution algorithms. Use when building self-improving agents, optimizing agent prompts and skills against benchmarks, or implementing automated agent evaluation loops.
  • 100connect-harness
    Run a coding-agent harness (Pi, Claude Code or Codex) on a running Evolving Infra stack with the launch scripts of examples/agents. Use when asked to use Evolving Infra as the model of Pi, Claude Code, Codex or another off-the-shelf agent harness. Not for changing an agent's own…
  • 100loop
    Use when the user asks to run autonomous improvement cycles, self-evolving development, compound discovery, or multi-cycle code improvement with research, build, audit, and learning phases
  • 100hyperagent
    Run a self-referential self-improving agent loop where a meta-agent iteratively modifies a task-agent's code to optimize for any measurable target. Based on Facebook Research's Hyperagents paper (arXiv:2603.19461). Use when asked to "run hyperagent", "self-improve this",…
  • 90evolving-skill-packs
    Use when evolving skill packs is required during meta work, especially when the result must be traceable, independently reviewable, and safe to hand to another agent.
  • 100evolving-memory
    Evolving memory system inspired by EvoScientist. Extends ScienceClaw's research memory with four record types (finding, ideation, strategy, pitfall) to enable learning from past research sessions. Recall relevant strategies and pitfalls before recipe execution, extract and…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.