---
name: update-skills
description: Verify and update agent skills so their system descriptions stay accurate as the codebase evolves
disable-model-invocation: true
title: update-skills
canonical_url: https://skilld.dev/gh/sandharbor/meadow/update-skills
last_updated: 2026-10-08T17:30:29.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install sandharbor/meadow/update-skills`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/update-skills`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/sandharbor/meadow/update-skills) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/update-skills`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/update-skills --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/update-skills --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Update Skills

Skills encode two kinds of knowledge: **why** (purpose, goals, workflow steps)
and **how** (file paths, command names, architecture details, code patterns).
The "why" is stable, but the "how" drifts as the codebase evolves. This skill
systematically verifies each skill's factual claims and updates them.

## Step 1: Enumerate all skills

List every skill directory under `.agents/skills/` (excluding this one):

```bash
ls -d .agents/skills/*/
```

Read each `SKILL.md` file to build the full list.

## Step 2: For each skill, verify factual claims

Work through the skills one at a time. For each skill:

### 2a. Identify verifiable claims

Read the skill file and extract every factual claim about the system. These
fall into several categories:

- **File paths** — e.g. `app/acceptance/e2e/tests/*.spec.ts`, `app/hosts/desktop/package.json`
- **Directory structures** — e.g. ASCII trees showing project layout
- **Command names and flags** — e.g. `./app/acceptance/e2e/_module/scripts/slowcheck`, `./app/acceptance/e2e/dev-e2e`
- **Script behavior descriptions** — e.g. "starts MinIO in Docker", "allocates free ports"
- **Code patterns** — e.g. fixture APIs like `checkpoint(message)`, function signatures
- **Architecture details** — e.g. port numbers, API routes, file formats
- **Configuration** — e.g. backing-store table names, Docker container names

### 2b. Check each claim against reality

For each claim:

1. **File/directory paths**: Use Glob to confirm they exist. Check for files
   that were added, renamed, or removed.
2. **Commands and scripts**: Read the script to confirm it still works as
   described. Check flags, arguments, and behavior.
3. **Code patterns**: Read the referenced source files to confirm APIs,
   function signatures, and usage patterns still match.
4. **Architecture details**: Read config files, server code, and test
   infrastructure to verify port numbers, route paths, table names, etc.
5. **Directory trees**: Compare the claimed tree against what actually exists
   via Glob and ls.

### 2c. Classify each finding

For each discrepancy found, classify it:

- **Stale path**: file was renamed or moved
- **Missing file**: file was deleted
- **New file**: relevant file exists but isn't mentioned
- **Changed behavior**: script or code works differently than described
- **Changed API**: function signature, route, or interface changed
- **Changed config**: port, table name, container name, etc. changed

## Step 3: Report findings before editing

Before making any changes, present a summary to the user for each skill:

> **Skill: `<name>`**
> - [list of discrepancies found, or "No issues found"]

Ask the user to confirm before proceeding with edits. This prevents
well-intentioned but unwanted changes.

## Step 4: Update the skill files

For each confirmed discrepancy:

1. **Preserve the "why"** — do not change the skill's purpose, workflow steps,
   or decision logic. Only update factual descriptions of the system.
2. **Update file paths** to reflect renames/moves.
3. **Add new files** to directory trees and key-file lists where relevant.
4. **Remove references** to deleted files.
5. **Update behavior descriptions** to match current script/code behavior.
6. **Update code examples** to match current APIs.
7. **Update config values** (ports, table names, routes) to match reality.

Use the Edit tool for surgical updates — do not rewrite entire skill files.

## Step 5: Verify the updates

After editing, re-read each modified skill file and do a quick spot-check that
the updates are accurate and that nothing was accidentally broken.

Then run:

```bash
./quickcheck
```

This confirms the skill file edits didn't break anything (skill files
themselves aren't validated by check, but this ensures you didn't accidentally
modify non-skill files).

## Step 6: Summary

Print a final summary:

- How many skills were checked
- How many had discrepancies
- What was updated (brief list per skill)
- Any claims that couldn't be verified and may need manual review
