Skip to content
cccskills
FreePublished on GitHub

skill-evolution

Turn useful project experience into a reusable skill stored with the project. Identify recurring workflows or domain knowledge, follow naming and structure guidance, and decide when to add scripts or reference materials so future tasks can repeat the work.

OriginalShow the original description

Evolve new skills from project experience. Use when a repeating pattern, useful workflow, or hard-won knowledge should be captured as a reusable skill for the current project.

HKUDS/AutoSwarm2,083 stars(GitHub 2,083 + cccskills 0)

Run score Not tested

See how to install

Good for

  • Capturing a workflow that is likely to recur
  • Saving project-specific knowledge for future tasks
  • Turning a reliable tool sequence into a skill
  • Adding scripts or references to a reusable skill

Files included (1)

  • SKILL.md2.5 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Skill Evolution

Distill project experience into reusable skills that live under the current project.

Two evolution paths

  1. Automatic: The system promotes playbook skills when an employee's pattern reaches 2 project reflections with recurring behaviors, checklists, or preferences. These are saved as <employee>-<role>-<domain>-playbook and require no manual action.
  2. Agent-driven (this skill): You proactively identify valuable patterns and create skills manually. Use this when domain knowledge, workflows, or tool sequences should be preserved before the auto-promotion threshold is reached, or when the knowledge is not tied to a specific employee pattern.

When to evolve a skill (agent-driven)

  • A task required non-obvious steps that will likely recur
  • You discovered a workflow that worked well and should be preserved
  • Domain-specific knowledge was gathered that future tasks will need
  • A sequence of tool calls forms a reliable pattern worth codifying

Process

  1. Identify the pattern: What knowledge or workflow is worth preserving?
  2. Read the skill-creator skill: file_read the skill-creator/SKILL.md for format and naming guidelines
  3. Name the skill: Lowercase letters, digits, and hyphens only, under 64 characters (e.g., api-validation-workflow)
  4. Create the skill directory: Under .opc/projects/<project_id>/skills/<skill-name>/
  5. Write SKILL.md with proper frontmatter (name, description) and concise instructions
  6. Add scripts/references/assets if the skill benefits from bundled resources

Skill location

Evolved skills belong to the project that produced them:

.opc/projects/<project_id>/skills/<skill-name>/SKILL.md

Guidelines

  • Keep it concise: only include what the agent doesn't already know
  • Use concrete examples over abstract explanations
  • Include the minimal set of steps needed to reproduce the workflow
  • Add scripts/ for deterministic operations that get rewritten repeatedly
  • Add references/ for domain docs the agent should consult
  • Follow the same naming conventions as auto-promoted skills (hyphen-case)

Cross-project reuse

Other projects can reference this project's skills via file_read when the secretary recommends them. Do not duplicate skills across projects; read from the source project instead.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

clawhub

FreeSummary

Search ClawHub, a public registry for agent skills, using a natural-language query, then install a selected skill into a project or update installed skills. It also explains how to list skills already installed in that project.

  • Finding a skill for an unfamiliar task
  • Installing a selected skill in a project
  • Updating or listing project skills
HKUDS/AutoSwarm2.1KUpdated Oct 29, 2026

collaboration-playbook

FreeSummary

Set shared coordination practices for roles in an AutoSwarm company, including work-item boundaries, reviewable handoffs, peer messaging, meetings, and blocking requests. This playbook guides when to communicate and what information to leave for colleagues so work can continue across roles.

  • Preparing a reviewer-friendly handoff for a work item
  • Deciding when to message a teammate or request a response
  • Coordinating a meeting about a cross-role decision
HKUDS/AutoSwarm2.1KUpdated Oct 29, 2026

cron

FreeSummary

Use this skill to schedule recurring or one-time commands through the system crontab and `at`. It shows how to list, add, and remove jobs, with common schedules and practical notes about command paths and output logs.

  • Setting a recurring break reminder
  • Scheduling a one-time meeting reminder
  • Listing or removing scheduled jobs
HKUDS/AutoSwarm2.1KUpdated Oct 29, 2026

github

FreeSummary

Use the `gh` command-line tool to inspect GitHub issues, pull requests, and CI workflow runs. Check status and failure logs, retrieve specific repository data through the API, and filter structured JSON output for focused results.

  • Checking a pull request’s CI status
  • Finding failed steps in a workflow run
  • Listing recent repository workflow runs
HKUDS/AutoSwarm2.1KUpdated Oct 29, 2026

memory

FreeSummary

Maintain durable Markdown memory for stable preferences shared across projects and details specific to the current project. The skill guides when to update, what to exclude, and how to merge notes in the designated memory files.

  • Save a confirmed communication preference for future sessions
  • Record current project paths and coding conventions
  • Update project memory after the user confirms a lasting constraint
HKUDS/AutoSwarm2.1KUpdated Oct 29, 2026

opc-collab

FreeSummary

Coordinate work with other agents in AutoSwarm company mode. Use the `opc-collab` CLI to send messages, ask for user input, delegate work, review a manager board, respond in meetings, and propose task changes.

  • Messaging a teammate about a blocker
  • Asking the user for missing input
  • Delegating work to direct reports
HKUDS/AutoSwarm2.1KUpdated Oct 29, 2026

See all skills by HKUDS

Report a problem with this skill