[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CQAKDXKZ5PFXZR3DC41CB3":3,"skill-same:01M7CQAKDXKZ5PFXZR3DC41CB3":43},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":28,"install":29,"resources":42},"01M7CQAKDXKZ5PFXZR3DC41CB3","repo-kit-install",null,"Use to install the repository kit named in a repos.json entry into your local clone of that repository, on a new branch, without committing.","maximk777\u002Fopencode-config","maximk777","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F205286132?v=4","01M7CQ4VVPFQ3MDCXJBFB0HPTZ","01M7CQ4VWA2GG0H2CNNREZ9AN9",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmaximk777\u002Fopencode-config\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fnormalize-team\u002F.agents\u002Fskills\u002Frepo-kit-install\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: repo-kit-install\ndescription: Use to install the repository kit named in a repos.json entry into your local clone of that repository, on a new branch, without committing.\n---\n# Install a repository kit\n\nThis skill writes into the clone `repos\u002F\u003Cname>`, never into the workspace. In the clone it writes only under `.agents\u002F`, the `.agent\u002F` links it repairs in step 13, and the one `AGENTS.md` line of step 17. It never reads `.env` files, `.local\u002Fenv` or secret values, never prints tokens, and never commits or pushes.\n\n## Words used below\n- `\u003Cws>`: the workspace root, an absolute path (the output of `pwd` in step 1).\n- `\u003Cname>`: the repository name in `repos.json`. `\u003Cclone>`: `\u003Cws>\u002Frepos\u002F\u003Cname>`.\n- `\u003Ckind>`: `kit.kind` of the entry. `\u003Ckitdir>`: `\u003Cws>\u002F.agents\u002Frepo-kits\u002F\u003Ckind>`. `\u003Cversion>`: `version` in `\u003Ckitdir>\u002Fkit.json`. This is the workspace version of the kit; the workspace's own `.agents\u002Fkit.json` is a different file.\n- `\u003Cbranch>`: `repo-kit-\u003Ckind>-\u003Cversion>`, for example `repo-kit-example-0.1.0`.\n- `\u003Cdefault>`: `default_branch` of the entry.\n- `\u003Cout>`: a temporary folder for the rendered kit, outside the clone and the workspace.\n- `\u003Cbase>`: the folder the clone's kit files are read from. It is `\u003Cclone>\u002F.agent` while `\u003Cclone>\u002F.agents` does not exist and `\u003Cclone>\u002F.agent` does; otherwise it is `\u003Cclone>\u002F.agents`. The kit path `.agents\u002F\u003Cp>` is the clone file `\u003Cbase>\u002F\u003Cp>`.\n- `\u003Csha256>`: `shasum -a 256` when `command -v shasum` prints a path, otherwise `sha256sum`.\n- States of a path: `absent`, `same`, `replaceable`, `edited`, `obsolete`, `removed-edited`, `foreign` (see `## Recipe: status`). Decisions for an `edited` path: `kit`, `local`, `raise`, exactly these words.\n\n## Stops\nEvery stop prints its message and ends the skill. Before a stop in this table the skill has written nothing into the clone and created no branch. When `\u003Cout>` already exists, run `rm -rf \u003Cout>` before stopping. Only step 16 can stop after the clone changed; it prints the commands that discard the attempt.\n\n| Stop | Message |\n|---|---|\n| S1 no digest tool | `Stop: python3, shasum and sha256sum are all missing, so file digests cannot be computed. Nothing was changed.` |\n| S2 unknown repository | `Stop: repository \u003Cname> is not in repos.json. Nothing was changed.` |\n| S3 invalid kit | `Stop: the kit of repository \u003Cname> in repos.json is invalid: \u003Creason>. Fix the entry or the kit through a workspace merge request, then run repo-kit-install again. Nothing was changed.` |\n| S4 render failed | `Stop: rendering kit \u003Ckind> for repository \u003Cname> failed: \u003Creason>. Nothing was changed.` |\n| S5 clone missing | `Stop: clone repos\u002F\u003Cname> is missing. Clone it with the repos-sync skill, then run repo-kit-install again. Nothing was changed.` |\n| S6 dirty clone | `Stop: clone repos\u002F\u003Cname> has uncommitted changes. Commit or stash them yourself, then run repo-kit-install again. Nothing was changed.` |\n| S7 not on the default branch | `Stop: clone repos\u002F\u003Cname> is on branch \u003Ccurrent>, not \u003Cdefault>. Switch it to \u003Cdefault> yourself, then run repo-kit-install again. Nothing was changed.` |\n| S8 both folders | `Stop: repos\u002F\u003Cname> has both .agent\u002F and .agents\u002F. Which one should stay? Merge them by hand in a separate merge request, then run repo-kit-install again. Nothing was changed.` |\n| S9 other kind | `Stop: repos\u002F\u003Cname>\u002F.agents\u002Fkit.json has kind \u003Cstamp kind>, but repos.json names kind \u003Ckind>. Changing the kind of a repository is the owner's decision. Nothing was changed.` |\n| S10 workspace behind | `Stop: repos\u002F\u003Cname>\u002F.agents\u002Fkit.json has version \u003Cstamp version>, newer than version \u003Cversion> of kit \u003Ckind> in this workspace. The workspace is behind: update it from its default branch, then run the skill again. Nothing was changed.` |\n| S11 branch exists | `Stop: branch \u003Cbranch> already exists in repos\u002F\u003Cname>. Finish or delete it, then run repo-kit-install again. Nothing was changed.` |\n| S12 value the recipe cannot render | `Stop: parameter \u003CNAME> of repository \u003Cname> has the value \u003Cvalue>, which the recipe without python3 cannot render. Run repo-kit-install where python3 is available. Nothing was changed.` |\n| S13 raise | `Stop: \u003Cpath> got the decision raise. Change kit \u003Ckind> in .agents\u002Frepo-kits\u002F\u003Ckind>\u002F through a workspace merge request, then run repo-kit-install again. Nothing was changed.` |\n\nS8 also asks the maintainer the question in its message and waits for the answer; the skill does not merge the folders.\n\n## Steps\n1. Go to the workspace root: the nearest directory, walking up from where you are, where `test -f .agents\u002Fkit.json` succeeds. Run `pwd`; its output is `\u003Cws>`. Use the workspace default branch after the merge request with the kit and the entry is merged. Start every command below with `cd \u003Cws> && ` or `cd \u003Cclone> && ` as shown.\n2. Find the tools. When `command -v python3` prints a path, Python is present. Otherwise, when neither `command -v shasum` nor `command -v sha256sum` prints a path, stop with S1. Without Python, follow `## Without Python` in every step that names a recipe.\n3. Ask the person for `\u003Cname>` when they did not give it. Read `\u003Cws>\u002Frepos.json` and find the entry of `repositories` whose `name` is `\u003Cname>`. With no such entry, stop with S2.\n4. Check the entry's `kit`:\n   - When the entry has no `kit`, stop with S3 and the reason `the entry has no kit`.\n   - When `test -d \u003Ckitdir>` fails, stop with S3 and the reason `kit kind \u003Ckind> is not a folder under .agents\u002Frepo-kits\u002F`.\n   - Read `\u003Ckitdir>\u002Fkit.json`. `kit.params` of the entry must have exactly the names in `params` of `kit.json`, and every value must match the whole `pattern` of its parameter. Check a pattern with Python as `repos-add` step 2 does: `PATTERN='\u003Cpattern>' VALUE='\u003Cvalue>' python3 -c 'import os, re, sys; sys.exit(0 if re.fullmatch(os.environ[\"PATTERN\"], os.environ[\"VALUE\"]) else 1)'`; exit code 0 means it matches. Without Python run `printf '%s\\n' '\u003Cvalue>' | grep -Ex -e '\u003Cpattern>'`; exit code 0 means the whole value matches. In both commands write each `'` inside the quotes as `'\\''`. `grep -E` syntax covers the patterns kits use: character classes, `.`, `*`, `+`, `?`, `{m,n}`, `|` and groups. When a pattern uses syntax `grep -E` does not support, such as `\\d`, `\\w`, `\\s`, `(?` or a lazy `*?`, compare by reading instead. A value with a line break never matches. On a missing name, an extra name or a value that does not match, stop with S3 and name the parameter in the reason.\n   - Remember `\u003Cversion>` from `version` in `\u003Ckitdir>\u002Fkit.json` and `\u003Cdefault>` from the entry.\n5. Render the kit. Run `mktemp -d`; its output is `\u003Cout>`.\n   - With Python: `cd \u003Cws> && python3 tools\u002Frepo_kit.py render \u003Cname> \u003Cout>`. When it exits 2, stop with S4 and use its error line as the reason.\n   - Without Python: apply `## Recipe: render`.\n   `\u003Cout>\u002F.agents\u002F` now holds every kit file with the placeholders replaced.\n6. Check the clone:\n   - When `test -d \u003Cclone>\u002F.git` fails, stop with S5.\n   - When `cd \u003Cclone> && git status --porcelain` prints anything, stop with S6.\n   - When `cd \u003Cclone> && git rev-parse --abbrev-ref HEAD` prints something other than `\u003Cdefault>`, stop with S7 with that output as `\u003Ccurrent>`.\n   - When both `test -d \u003Cclone>\u002F.agent` and `test -d \u003Cclone>\u002F.agents` succeed, stop with S8.\n7. Check for a stamp. When `test -f \u003Cclone>\u002F.agents\u002Fkit.json` succeeds, the repository already has a kit:\n   - Read `kind` and `version` from it (`grep -m 1 '^  \"kind\": ' \u003Cclone>\u002F.agents\u002Fkit.json` and `grep -m 1 '^  \"version\": ' \u003Cclone>\u002F.agents\u002Fkit.json`).\n   - When `kind` is not `\u003Ckind>`, stop with S9.\n   - Compare the stamp `version` with `\u003Cversion>` as three numbers, MAJOR first, then MINOR, then PATCH: `1.10.0` is newer than `1.9.0`. When the stamp version is newer, stop with S10. For example, stamp `1.2.0` and workspace kit `1.1.0` stop here.\n   - Otherwise run `rm -rf \u003Cout>` and continue with `.agents\u002Fskills\u002Frepo-kit-update\u002FSKILL.md` for the same `\u003Cname>` from its first step. Do not run the rest of this skill.\n8. When `cd \u003Cclone> && git rev-parse --verify --quiet refs\u002Fheads\u002F\u003Cbranch>` or `cd \u003Cclone> && git rev-parse --verify --quiet refs\u002Fremotes\u002Forigin\u002F\u003Cbranch>` prints anything, stop with S11.\n9. Compare the clone with the kit.\n   - With Python: `cd \u003Cws> && python3 tools\u002Frepo_kit.py status \u003Cname> repos\u002F\u003Cname>`. When it exits 2, stop with S4 and use its error line as the reason.\n   - Without Python: apply `## Recipe: status`.\n   Each output line is `\u003Cstate> \u003Cpath>`. Before the folder move the paths still read `.agents\u002F...`; the files behind them are under `\u003Cbase>`. Without a stamp only `absent`, `same`, `edited` and `foreign` occur.\n10. Collect decisions before writing anything. Show the person every `edited` path. For each path `.agents\u002F\u003Cp>`, show the difference with `diff \u003Cbase>\u002F\u003Cp> \u003Cout>\u002F.agents\u002F\u003Cp>`. When `\u003Cbase>` is `\u003Cclone>\u002F.agent`, show it with the old links normalized instead: `LC_ALL=C sed 's#\\.agent\u002F#.agents\u002F#g' \u003Cbase>\u002F\u003Cp> | diff - \u003Cout>\u002F.agents\u002F\u003Cp>`. When that `diff` prints nothing, the file differs only in `.agent\u002F` links, which step 13 repairs: tell the person so and write down `kit` for the path without asking. Otherwise ask for one decision:\n    - `kit`: the clone file is replaced by the kit file; the clone text is lost.\n    - `local`: the clone text moves to `.agents\u002Flocal\u002F\u003Cp>`, and the kit file takes its place. When `test -e \u003Cbase>\u002Flocal\u002F\u003Cp>` succeeds, that place is taken: tell the person and ask again for `kit` or `raise`.\n    - `raise`: the kit itself must change first.\n    Write the decisions down as `\u003Cdecision> \u003Cpath>`. When the person gives any other word, ask again. When there is no `edited` path, there is nothing to ask.\n11. When any path got `raise`, run `rm -rf \u003Cout>` and stop with S13, naming that path. The clone has no new branch and no changed file.\n12. Create the branch: `cd \u003Cclone> && git switch -c \u003Cbranch>`. From here on the clone changes.\n13. Move the folder and repair links, only when `\u003Cbase>` is `\u003Cclone>\u002F.agent`:\n    1. `cd \u003Cclone> && git mv .agent .agents`. From now on `\u003Cbase>` is `\u003Cclone>\u002F.agents`.\n    2. List the lines that still link to the old folder: `cd \u003Cclone> && grep -rnI --exclude-dir=.git --exclude='.env' --exclude='.env.*' '\\.agent\u002F' .`. Files named `.env` or `.env.*` are never read.\n    3. In every listed line change `.agent\u002F` to `.agents\u002F` and change nothing else in the file. Remember the listed files outside `.agents\u002F` for step 19.\n    4. Run the `grep` of sub-step 2 again; it prints nothing.\n\n    This step runs before step 14, so text that step 14 moves to `.agents\u002Flocal\u002F` under a `local` decision already has its `.agent\u002F` links repaired.\n14. Apply the decisions, for each `edited` path `.agents\u002F\u003Cp>`:\n    - `kit`: `cd \u003Cclone> && cp \u003Cout>\u002F.agents\u002F\u003Cp> .agents\u002F\u003Cp>`.\n    - `local`: `cd \u003Cclone> && mkdir -p \"$(dirname .agents\u002Flocal\u002F\u003Cp>)\" && mv .agents\u002F\u003Cp> .agents\u002Flocal\u002F\u003Cp> && cp \u003Cout>\u002F.agents\u002F\u003Cp> .agents\u002F\u003Cp>`.\n15. Copy every `absent` path `.agents\u002F\u003Cp>`: `cd \u003Cclone> && mkdir -p \"$(dirname .agents\u002F\u003Cp>)\" && cp \u003Cout>\u002F.agents\u002F\u003Cp> .agents\u002F\u003Cp>`. Leave `same` paths as they are and do not touch `foreign` paths.\n16. Write the stamp.\n    - With Python: `cd \u003Cws> && python3 tools\u002Frepo_kit.py stamp \u003Cname> repos\u002F\u003Cname>`.\n    - Without Python: apply `## Recipe: stamp`.\n    Then run step 9 again. Every kit path must now be `same`; `foreign` paths stay. When another state is left, stop: run `rm -rf \u003Cout>`, tell the person every line whose state is neither `same` nor `foreign`, and print these commands for the person to discard the attempt. Do not run them yourself:\n    ```\n    cd \u003Cclone> && git reset --hard && git clean -fd\n    cd \u003Cclone> && git switch \u003Cdefault> && git branch -d \u003Cbranch>\n    ```\n    The first line removes every uncommitted change of this attempt, staged or untracked, including the folder move. The second returns the clone to `\u003Cdefault>` and deletes `\u003Cbranch>`. Step 6 made sure the clone had no uncommitted or untracked files before, so nothing else is lost.\n17. Check the root `AGENTS.md` of the clone. The clone owns it; the kit never rewrites it.\n    - `cd \u003Cclone> && grep -n '\\.agents\u002FAGENTS\\.md' AGENTS.md` and `cd \u003Cclone> && grep -n '\\.agents\u002Flocal\u002F' AGENTS.md`. A command that prints a line means that link exists.\n    - When both print a line, change nothing.\n    - Otherwise propose one line to the person, by what is missing, and add it as the last line of `AGENTS.md` only when the person agrees. When `AGENTS.md` does not exist, propose creating it with only that line.\n      ```\n      Both missing:            Agent instructions: [.agents\u002FAGENTS.md](.agents\u002FAGENTS.md). Repository-only rules and skills: [.agents\u002Flocal\u002F](.agents\u002Flocal\u002F).\n      Only .agents\u002Flocal\u002F:     Repository-only rules and skills: [.agents\u002Flocal\u002F](.agents\u002Flocal\u002F).\n      Only .agents\u002FAGENTS.md:  Agent instructions: [.agents\u002FAGENTS.md](.agents\u002FAGENTS.md).\n      ```\n      Write only the text after the label and the spaces.\n    - When the line links to `.agents\u002Flocal\u002F` and `test -d \u003Cclone>\u002F.agents\u002Flocal` fails, run `cd \u003Cclone> && mkdir -p .agents\u002Flocal && touch .agents\u002Flocal\u002F.gitkeep` so the link resolves.\n18. List every `foreign` path from step 9. These files belong to the repository: do not move or change them. For each `.agents\u002F\u003Cp>` propose `git mv .agents\u002F\u003Cp> .agents\u002Flocal\u002F\u003Cp>` to the person as a later change of their own.\n19. Run `rm -rf \u003Cout>`. Print these commands for the person and do not run them. The repository's forge is `forge` of the entry, not the forge of this workspace:\n    ```\n    cd \u003Cclone>\n    git add -A .agents \u003Cfiles changed in step 13 outside .agents> \u003CAGENTS.md when step 17 changed it>\n    git commit -m \"chore(agents): install kit \u003Ckind> \u003Cversion>\"\n    ```\n    Then, by `forge`:\n    - `gitlab`: `git push -u origin \u003Cbranch> -o merge_request.create -o merge_request.title=\"Install kit \u003Ckind> \u003Cversion>\"`;\n    - `github`: `git push -u origin \u003Cbranch>`, then `gh pr create --fill`;\n    - `git`: `git push -u origin \u003Cbranch>`, then open the merge request by hand.\n    Tell the person to adjust the commit message to the repository's own commit rules when it has them.\n20. Report to the person: `\u003Cbranch>`; the decisions; the files copied; the files with repaired links; the `AGENTS.md` line proposed or added; the `foreign` list; the printed commands. Never commit or push yourself.\n\n## Example\nWorkspace entry `payments-worker` with kit `example` version `0.1.0` and `\"params\": {\"SERVICE\": \"payments-worker\"}`, forge `gitlab`, default branch `main`. The kit has `files\u002FAGENTS.md`, `files\u002Frules\u002Fexample.md` and `files\u002Fskills\u002Fexample\u002FSKILL.md`. The clone `repos\u002Fpayments-worker` is clean on `main` and has no `.agents\u002F`, but has `.agent\u002FAGENTS.md` equal to the rendered file, `.agent\u002Frules\u002Fexample.md` edited by hand, and `.agent\u002Fnotes.md`. Its root `AGENTS.md` says `See .agent\u002FAGENTS.md.`\n\n- Step 9 prints:\n  ```\n  same .agents\u002FAGENTS.md\n  foreign .agents\u002Fnotes.md\n  edited .agents\u002Frules\u002Fexample.md\n  absent .agents\u002Fskills\u002Fexample\u002FSKILL.md\n  ```\n- Step 10: the person decides `local .agents\u002Frules\u002Fexample.md`.\n- Steps 12 to 16: branch `repo-kit-example-0.1.0`; `git mv .agent .agents`; root `AGENTS.md` becomes `See .agents\u002FAGENTS.md.`; `.agents\u002Frules\u002Fexample.md` moves to `.agents\u002Flocal\u002Frules\u002Fexample.md` and the kit file replaces it; `.agents\u002Fskills\u002Fexample\u002FSKILL.md` is copied; the stamp is written as in `## Recipe: stamp`. Step 9 again prints `same` for the three kit paths and `foreign .agents\u002Fnotes.md`.\n- Step 17: `AGENTS.md` links to `.agents\u002FAGENTS.md` but not to `.agents\u002Flocal\u002F`; the proposed line is `Repository-only rules and skills: [.agents\u002Flocal\u002F](.agents\u002Flocal\u002F).` The folder exists after the `local` decision.\n- Step 18 proposes `git mv .agents\u002Fnotes.md .agents\u002Flocal\u002Fnotes.md`.\n- Step 19 prints `git add -A .agents AGENTS.md`, the commit command and `git push -u origin repo-kit-example-0.1.0 -o merge_request.create -o merge_request.title=\"Install kit example 0.1.0\"`.\n\n## Recipe: render\nGives exactly the files `python3 tools\u002Frepo_kit.py render \u003Cname> \u003Cout>` writes.\n\n1. Values. For every parameter in `params` of `\u003Ckitdir>\u002Fkit.json`, take its value from `kit.params` of the entry. The recipe replaces placeholders with `sed`, so it works only when no value contains `\u002F`, `&`, `\\`, `\"`, `'`, `__`, a tab, a line break or another control character. For such a value stop with S12.\n2. Placeholders. Run `cd \u003Ckitdir>\u002Ffiles && LC_ALL=C grep -rhoaE '__[A-Z][A-Z0-9_]*__' . | LC_ALL=C sort -u`. Every printed line must be `__\u003CNAME>__` for a `\u003CNAME>` in `params`. For any other line find the file with `cd \u003Ckitdir>\u002Ffiles && LC_ALL=C grep -rlaF '\u003Cline>' .` and stop with S4, reason `kit \u003Ckind>: files\u002F\u003Cfile> uses undeclared placeholder \u003CNAME>`.\n3. Files. Kit files are every file under `\u003Ckitdir>\u002Ffiles\u002F` except files inside `__pycache__` folders. File names must not contain `\"`, `\\` or control characters; otherwise stop with S12 naming the file instead of a parameter. Copy each file `files\u002F\u003Cp>` to `\u003Cout>\u002F.agents\u002F\u003Cp>`, with one `sed` expression `-e 's\u002F__\u003CNAME>__\u002F\u003Cvalue>\u002Fg'` per parameter, in the order of `params`. `LC_ALL=C` makes `sed` treat the file as bytes, so line endings, a missing last newline and any encoding stay as they are:\n   ```\n   cd \u003Ckitdir>\u002Ffiles && LC_ALL=C find . -type f ! -path '*\u002F__pycache__\u002F*' | LC_ALL=C sort | while IFS= read -r p; do p=${p#.\u002F}; mkdir -p \"\u003Cout>\u002F.agents\u002F$(dirname \"$p\")\" && LC_ALL=C sed -e 's\u002F__\u003CNAME1>__\u002F\u003Cvalue1>\u002Fg' -e 's\u002F__\u003CNAME2>__\u002F\u003Cvalue2>\u002Fg' \"$p\" > \"\u003Cout>\u002F.agents\u002F$p\"; done\n   ```\n\nExample for kit `example` with the one parameter `SERVICE` = `payments-worker`, `\u003Ckitdir>` = `\u003Cws>\u002F.agents\u002Frepo-kits\u002Fexample` and `\u003Cout>` = `\u002Ftmp\u002Ftmp.k3Jd9`:\n```\ncd \u003Cws>\u002F.agents\u002Frepo-kits\u002Fexample\u002Ffiles && LC_ALL=C grep -rhoaE '__[A-Z][A-Z0-9_]*__' . | LC_ALL=C sort -u\n```\nprints only `__SERVICE__`, which is declared. Then:\n```\ncd \u003Cws>\u002F.agents\u002Frepo-kits\u002Fexample\u002Ffiles && LC_ALL=C find . -type f ! -path '*\u002F__pycache__\u002F*' | LC_ALL=C sort | while IFS= read -r p; do p=${p#.\u002F}; mkdir -p \"\u002Ftmp\u002Ftmp.k3Jd9\u002F.agents\u002F$(dirname \"$p\")\" && LC_ALL=C sed -e 's\u002F__SERVICE__\u002Fpayments-worker\u002Fg' \"$p\" > \"\u002Ftmp\u002Ftmp.k3Jd9\u002F.agents\u002F$p\"; done\n```\nResult: `\u002Ftmp\u002Ftmp.k3Jd9\u002F.agents\u002FAGENTS.md`, `\u002Ftmp\u002Ftmp.k3Jd9\u002F.agents\u002Frules\u002Fexample.md` and `\u002Ftmp\u002Ftmp.k3Jd9\u002F.agents\u002Fskills\u002Fexample\u002FSKILL.md`. The first line of the rendered `AGENTS.md` is `# payments-worker`, and no rendered file contains `__SERVICE__`.\n\n## Recipe: status\nGives exactly the lines `python3 tools\u002Frepo_kit.py status \u003Cname> repos\u002F\u003Cname>` prints. It needs `\u003Cout>` from `## Recipe: render`. A digest is the first 64 characters of `\u003Csha256>` run on the file as standard input: `shasum -a 256 \u003C \u003Cfile> | cut -c 1-64`. The stamp `\u003Cclone>\u002F.agents\u002Fkit.json` is read as `## Recipe: stamp` writes it: one `files` entry per line, `    \"\u003Cpath>\": \"\u003Cdigest>\"`. The stamp digest of a path is `grep -F '    \"\u003Cpath>\": \"' \u003Cclone>\u002F.agents\u002Fkit.json | head -n 1 | cut -d '\"' -f 4`; it is empty when there is no stamp or no such line.\n\nFor every rendered path `.agents\u002F\u003Cp>`, the clone file `F` is `\u003Cbase>\u002F\u003Cp>`:\n- `absent`: `F` does not exist;\n- `same`: `cmp -s \u003Cout>\u002F.agents\u002F\u003Cp> F` succeeds;\n- `replaceable`: otherwise, when the stamp digest of the path is not empty and equals the digest of `F`;\n- `edited`: otherwise.\n\nFor every path `P` in the stamp's `files` that is not rendered (`test -f \u003Cout>\u002FP` fails), starts with `.agents\u002F`, has no `..` segment, and whose clone file `\u003Cbase>\u002F\u003CP without .agents\u002F>` exists:\n- `obsolete`: the stamp digest equals the digest of that file;\n- `removed-edited`: otherwise.\nA stamp path whose clone file is missing prints nothing.\n\nFor every file under `\u003Cbase>`, as the path `.agents\u002F\u003Cp>`: `foreign` when it is not rendered, not a key in the stamp's `files`, not `.agents\u002Fkit.json` and not under `.agents\u002Flocal\u002F`.\n\nSort all lines by path, byte by byte. The commands, with the three values set in the first line:\n```\nOUT=\u003Cout>; CLONE=\u003Cclone>; BASE=\u003Cbase>\nSTAMP=\"$CLONE\u002F.agents\u002Fkit.json\"\n{\n  cd \"$OUT\" && LC_ALL=C find .agents -type f | while IFS= read -r P; do\n    F=\"$BASE\u002F${P#.agents\u002F}\"\n    if [ ! -f \"$F\" ]; then echo \"absent $P\"\n    elif cmp -s \"$P\" \"$F\"; then echo \"same $P\"\n    else\n      H=$( [ -f \"$STAMP\" ] && grep -F \"    \\\"$P\\\": \\\"\" \"$STAMP\" | head -n 1 | cut -d '\"' -f 4 )\n      D=$(shasum -a 256 \u003C \"$F\" | cut -c 1-64)\n      if [ -n \"$H\" ] && [ \"$H\" = \"$D\" ]; then echo \"replaceable $P\"; else echo \"edited $P\"; fi\n    fi\n  done\n  [ -f \"$STAMP\" ] && sed -n '\u002F^  \"files\": {\u002F,\u002F^  }\u002Fp' \"$STAMP\" | grep '^    \"' | while IFS= read -r L; do\n    P=$(printf '%s\\n' \"$L\" | cut -d '\"' -f 2); H=$(printf '%s\\n' \"$L\" | cut -d '\"' -f 4)\n    case \"$P\" in .agents\u002F*) ;; *) continue ;; esac\n    case \"\u002F$P\u002F\" in *\u002F..\u002F*) continue ;; esac\n    [ -f \"$OUT\u002F$P\" ] && continue\n    F=\"$BASE\u002F${P#.agents\u002F}\"\n    [ -f \"$F\" ] || continue\n    if [ \"$(shasum -a 256 \u003C \"$F\" | cut -c 1-64)\" = \"$H\" ]; then echo \"obsolete $P\"; else echo \"removed-edited $P\"; fi\n  done\n  [ -d \"$BASE\" ] && cd \"$BASE\" && LC_ALL=C find . -type f | while IFS= read -r p; do\n    P=\".agents\u002F${p#.\u002F}\"\n    case \"$P\" in .agents\u002Fkit.json|.agents\u002Flocal\u002F*) continue ;; esac\n    [ -f \"$OUT\u002F$P\" ] && continue\n    [ -f \"$STAMP\" ] && grep -qF \"    \\\"$P\\\": \\\"\" \"$STAMP\" && continue\n    echo \"foreign $P\"\n  done\n} | LC_ALL=C sort -k 2\n```\nReplace both `shasum -a 256` with `sha256sum` when `shasum` is missing. The block runs the same in `sh`, `bash` and `zsh`.\n\nExample: the clone of `## Example` before the move, so `BASE=\u003Cws>\u002Frepos\u002Fpayments-worker\u002F.agent`, no stamp, `\u003Cout>` from `## Recipe: render`. `.agent\u002FAGENTS.md` equals the rendered file, `.agent\u002Frules\u002Fexample.md` differs, `.agent\u002Fskills\u002F` does not exist, and `.agent\u002Fnotes.md` is not a kit file. The lines are:\n```\nsame .agents\u002FAGENTS.md\nforeign .agents\u002Fnotes.md\nedited .agents\u002Frules\u002Fexample.md\nabsent .agents\u002Fskills\u002Fexample\u002FSKILL.md\n```\nWith a stamp holding the digest of the current `.agent\u002Frules\u002Fexample.md`, that line would be `replaceable .agents\u002Frules\u002Fexample.md` instead.\n\n## Recipe: stamp\nGives exactly the bytes of `\u003Cclone>\u002F.agents\u002Fkit.json` that `python3 tools\u002Frepo_kit.py stamp \u003Cname> repos\u002F\u003Cname>` writes. It needs `\u003Cout>` from `## Recipe: render`, and the value rules of that recipe hold here too.\n\nThe file has these lines, each ending with a line break, and nothing else:\n1. `{`\n2. `  \"kind\": \"\u003Ckind>\",`\n3. `  \"version\": \"\u003Cversion>\",`\n4. `  \"params\": {`\n5. one line per parameter, in the order of `params` in `\u003Ckitdir>\u002Fkit.json`: `    \"\u003CNAME>\": \"\u003Cvalue>\"`, with a comma after every line except the last;\n6. `  },`\n7. `  \"files\": {`\n8. one line per rendered file, sorted by path byte by byte: `    \".agents\u002F\u003Cp>\": \"\u003Cdigest of \u003Cout>\u002F.agents\u002F\u003Cp>>\"`, with a comma after every line except the last;\n9. `  }`\n10. `}`\n\nA kit without parameters writes the single line `  \"params\": {},` instead of lines 4 to 6; a kit without files writes `  \"files\": {}` instead of lines 7 to 9. This is how the tool prints an empty object.\n\nThe commands, with one argument per parameter line in the second `printf`. For a kit without parameters that line is `printf '%s\\n' '  \"params\": {},'` instead. The files part needs no change: it prints `  \"files\": {}` when `\u003Cout>` has no `.agents\u002F` files.\n```\nmkdir -p \u003Cclone>\u002F.agents && cd \u003Cout> && {\n  printf '%s\\n' '{' '  \"kind\": \"\u003Ckind>\",' '  \"version\": \"\u003Cversion>\",'\n  printf '%s\\n' '  \"params\": {' '    \"\u003CNAME1>\": \"\u003Cvalue1>\",' '    \"\u003CNAME2>\": \"\u003Cvalue2>\"' '  },'\n  FILES=$( [ -d .agents ] && LC_ALL=C find .agents -type f | LC_ALL=C sort | while IFS= read -r f; do printf '    \"%s\": \"%s\",\\n' \"$f\" \"$(shasum -a 256 \u003C \"$f\" | cut -c 1-64)\"; done | LC_ALL=C sed '$ s\u002F,$\u002F\u002F' )\n  if [ -n \"$FILES\" ]; then printf '%s\\n' '  \"files\": {' \"$FILES\" '  }'; else printf '%s\\n' '  \"files\": {}'; fi\n  printf '%s\\n' '}'\n} > \u003Cclone>\u002F.agents\u002Fkit.json\n```\nUse `sha256sum` instead of `shasum -a 256` when `shasum` is missing.\n\nExample for `## Example`, `\u003Cout>` = `\u002Ftmp\u002Ftmp.k3Jd9`:\n```\nmkdir -p \u003Cws>\u002Frepos\u002Fpayments-worker\u002F.agents && cd \u002Ftmp\u002Ftmp.k3Jd9 && {\n  printf '%s\\n' '{' '  \"kind\": \"example\",' '  \"version\": \"0.1.0\",'\n  printf '%s\\n' '  \"params\": {' '    \"SERVICE\": \"payments-worker\"' '  },'\n  FILES=$( [ -d .agents ] && LC_ALL=C find .agents -type f | LC_ALL=C sort | while IFS= read -r f; do printf '    \"%s\": \"%s\",\\n' \"$f\" \"$(shasum -a 256 \u003C \"$f\" | cut -c 1-64)\"; done | LC_ALL=C sed '$ s\u002F,$\u002F\u002F' )\n  if [ -n \"$FILES\" ]; then printf '%s\\n' '  \"files\": {' \"$FILES\" '  }'; else printf '%s\\n' '  \"files\": {}'; fi\n  printf '%s\\n' '}'\n} > \u003Cws>\u002Frepos\u002Fpayments-worker\u002F.agents\u002Fkit.json\n```\nThe written `repos\u002Fpayments-worker\u002F.agents\u002Fkit.json`, with a line break after the last `}`:\n```json\n{\n  \"kind\": \"example\",\n  \"version\": \"0.1.0\",\n  \"params\": {\n    \"SERVICE\": \"payments-worker\"\n  },\n  \"files\": {\n    \".agents\u002FAGENTS.md\": \"27ff1ccb6beb7cb7b873f3d9c173ff18e74fbb30572c299987bb09055b1d77b4\",\n    \".agents\u002Frules\u002Fexample.md\": \"e31c19605d14f680052c8bb7550bd2132105a0eacda42e9db2a11809743af543\",\n    \".agents\u002Fskills\u002Fexample\u002FSKILL.md\": \"777eb69778449f5ffa502dafaf1fee70914792262e0448e43a312adce57bd70b\"\n  }\n}\n```\n\n## Without Python\n1. Step 2: without `python3`, one of `shasum` or `sha256sum` must exist; with neither, stop with S1.\n2. Step 4: check each value against its `pattern` with the `grep -Ex` command of step 4, or by reading when the pattern uses syntax `grep -E` does not support; the whole value must match.\n3. Step 5: apply `## Recipe: render` instead of `tools\u002Frepo_kit.py render`.\n4. Steps 9 and 16: apply `## Recipe: status` instead of `tools\u002Frepo_kit.py status`.\n5. Step 16: apply `## Recipe: stamp` instead of `tools\u002Frepo_kit.py stamp`.\n6. The skill changes no workspace file, so there is no workspace check to run.\n","# Install a repository kit\n\nThis skill writes into the clone `repos\u002F\u003Cname>`, never into the workspace. In the clone it writes only under `.agents\u002F`, the `.agent\u002F` links it repairs in step 13, and the one `AGENTS.md` line of step 17. It never reads `.env` files, `.local\u002Fenv` or secret values, never prints tokens, and never commits or pushes.\n\n## Words used below\n- `\u003Cws>`: the workspace root, an absolute path (the output of `pwd` in step 1).\n- `\u003Cname>`: the repository name in `repos.json`. `\u003Cclone>`: `\u003Cws>\u002Frepos\u002F\u003Cname>`.\n- `\u003Ckind>`: `kit.kind` of the entry. `\u003Ckitdir>`: `\u003Cws>\u002F.agents\u002Frepo-kits\u002F\u003Ckind>`. `\u003Cversion>`: `version` in `\u003Ckitdir>\u002Fkit.json`. This is the workspace version of the kit; the workspace's own `.agents\u002Fkit.json` is a different file.\n- `\u003Cbranch>`: `repo-kit-\u003Ckind>-\u003Cversion>`, for example `repo-kit-example-0.1.0`.\n- `\u003Cdefault>`: `default_branch` of the entry.\n- `\u003Cout>`: a temporary folder for the rendered kit, outside the clone and the workspace.\n- `\u003Cbase>`: the folder the clone's kit files are read from. It is `\u003Cclone>\u002F.agent` while `\u003Cclone>\u002F.agents` does not exist and `\u003Cclone>\u002F.agent` does; otherwise it is `\u003Cclone>\u002F.agents`. The kit path `.agents\u002F\u003Cp>` is the clone file `\u003Cbase>\u002F\u003Cp>`.\n- `\u003Csha256>`: `shasum -a 256` when `command -v shasum` prints a path, otherwise `sha256sum`.\n- States of a path: `absent`, `same`, `replaceable`, `edited`, `obsolete`, `removed-edited`, `foreign` (see `## Recipe: status`). Decisions for an `edited` path: `kit`, `local`, `raise`, exactly these words.\n\n## Stops\nEvery stop prints its message and ends the skill. Before a stop in this table the skill has written nothing into the clone and created no branch. When `\u003Cout>` already exists, run `rm -rf \u003Cout>` before stopping. Only step 16 can stop after the clone changed; it prints the commands that discard the attempt.\n\n| Stop | Message |\n|---|---|\n| S1 no digest tool | `Stop: python3, shasum and sha256sum are all missing, so file digests cannot be computed. Nothing was changed.` |\n| S2 unknown repository | `Stop: repository \u003Cname> is not in repos.json. Nothing was changed.` |\n| S3 invalid kit | `Stop: the kit of repository \u003Cname> in repos.json is invalid: \u003Creason>. Fix the entry or the kit through a workspace merge request, then run repo-kit-install again. Nothing was changed.` |\n| S4 render failed | `Stop: rendering kit \u003Ckind> for repository \u003Cname> failed: \u003Creason>. Nothing was changed.` |\n| S5 clone missing | `Stop: clone repos\u002F\u003Cname> is missing. Clone it with the repos-sync skill, then run repo-kit-install again. Nothing was changed.` |\n| S6 dirty clone | `Stop: clone repos\u002F\u003Cname> has uncommitted changes. Commit or stash them yourself, then run repo-kit-install again. Nothing was changed.` |\n| S7 not on the default branch | `Stop: clone repos\u002F\u003Cname> is on branch \u003Ccurrent>, not \u003Cdefault>. Switch it to \u003Cdefault> yourself, then run repo-kit-install again. Nothing was changed.` |\n| S8 both folders | `Stop: repos\u002F\u003Cname> has both .agent\u002F and .agents\u002F. Which one should stay? Merge them by hand in a separate merge request, then run repo-kit-install again. Nothing was changed.` |\n| S9 other kind | `Stop: repos\u002F\u003Cname>\u002F.agents\u002Fkit.json has kind \u003Cstamp kind>, but repos.json names kind \u003Ckind>. Changing the kind of a repository is the owner's decision. Nothing was changed.` |\n| S10 workspace behind | `Stop: repos\u002F\u003Cname>\u002F.agents\u002Fkit.json has version \u003Cstamp version>, newer than version \u003Cversion> of kit \u003Ckind> in this workspace. The workspace is behind: update it from its default branch, then run the skill again. Nothing was changed.` |\n| S11 branch exists | `Stop: branch \u003Cbranch> already exists in repos\u002F\u003Cname>. Finish or delete it, then run repo-kit-install again. Nothing was changed.` |\n| S12 value the recipe cannot render | `Stop: parameter \u003CNAME> of repository \u003Cname> has the value \u003Cvalue>, which the recipe without python3 cannot render. Run repo-kit-install where python3 is available. Nothing was changed.` |\n| S13 raise | `Stop: \u003Cpath> got the decision raise. Change kit \u003Ckind> in .agents\u002Frepo-kits\u002F\u003Ckind>\u002F through a workspace merge request, then run repo-kit-install again. Nothing was changed.` |\n\nS8 also asks the maintainer the question in its message and waits for the answer; the skill does not merge the folders.\n\n## Steps\n1. Go to the workspace root: the nearest directory, walking up from where you are, where `test -f .agents\u002Fkit.json` succeeds. Run `pwd`; its output is `\u003Cws>`. Use the workspace default branch after the merge request with the kit and the entry is merged. Start every command below with `cd \u003Cws> && ` or `cd \u003Cclone> && ` as shown.\n2. Find the tools. When `command -v python3` prints a path, Python is present. Otherwise, when neither `command -v shasum` nor `command -v sha256sum` prints a path, stop with S1. Without Python, follow `## Without Python` in every step that names a recipe.\n3. Ask the person for `\u003Cname>` when they did not give it. Read `\u003Cws>\u002Frepos.json` and find the entry of `repositories` whose `name` is `\u003Cname>`. With no such entry, stop with S2.\n4. Check the entry's `kit`:\n   - When the entry has no `kit`, stop with S3 and the reason `the entry has no kit`.\n   - When `test -d \u003Ckitdir>` fails, stop with S3 and the reason `kit kind \u003Ckind> is not a folder under .agents\u002Frepo-kits\u002F`.\n   - Read `\u003Ckitdir>\u002Fkit.json`. `kit.params` of the entry must have exactly the names in `params` of `kit.json`, and every value must match the whole `pattern` of its parameter. Check a pattern with Python as `repos-add` step 2 does: `PATTERN='\u003Cpattern>' VALUE='\u003Cvalue>' python3 -c 'import os, re, sys; sys.exit(0 if re.fullmatch(os.environ[\"PATTERN\"], os.environ[\"VALUE\"]) else 1)'`; exit code 0 means it matches. Without Python run `printf '%s\\n' '\u003Cvalue>' | grep -Ex -e '\u003Cpattern>'`; exit code 0 means the whole value matches. In both commands write each `'` inside the quotes as `'\\''`. `grep -E` syntax covers the patterns kits use: character classes, `.`, `*`, `+`, `?`, `{m,n}`, `|` and groups. When a pattern uses syntax `grep -E` does not support, such as `\\d`, `\\w`, `\\s`, `(?` or a lazy `*?`, compare by reading instead. A value with a line break never matches. On a missing name, an extra name or a value that does not match, stop with S3 and name the parameter in the reason.\n   - Remember `\u003Cversion>` from `version` in `\u003Ckitdir>\u002Fkit.json` and `\u003Cdefault>` from the entry.\n5. Render the kit. Run `mktemp -d`; its output is `\u003Cout>`.\n   - With Python: `cd \u003Cws> && python3 tools\u002Frepo_kit.py render \u003Cname> \u003Cout>`. When it exits 2, stop with S4 and use its error line as the reason.\n   - Without Python: apply `## Recipe: render`.\n   `\u003Cout>\u002F.agents\u002F` now holds every kit file with the placeholders replaced.\n6. Check the clone:\n   - When `test -d \u003Cclone>\u002F.git` fails, stop with S5.\n   - When `cd \u003Cclone> && git status --porcelain` prints anything, stop with S6.\n   - When `cd \u003Cclone> && git rev-parse --abbrev-ref HEAD` prints something other than `\u003Cdefault>`, stop with S7 with that output as `\u003Ccurrent>`.\n   - When both `test -d \u003Cclone>\u002F.agent` and `test -d \u003Cclone>\u002F.agents` succeed, stop with S8.\n7. Check for a stamp. When `test -f \u003Cclone>\u002F.agents\u002Fkit.json` succeeds, the repository already has a kit:\n   - Read `kind` and `version` from it (`grep -m 1 '^  \"kind\": ' \u003Cclone>\u002F.agents\u002Fkit.json` and `grep -m 1 '^  \"version\": ' \u003Cclone>\u002F.agents\u002Fkit.json`).\n   - When `kind` is not `\u003Ckind>`, stop with S9.\n   - Compare the stamp `version` with `\u003Cversion>` as three numbers, MAJOR first, then MINOR, then PATCH: `1.10.0` is newer than `1.9.0`. When the stamp version is newer, stop with S10. For example, stamp `1.2.0` and workspace kit `1.1.0` stop here.\n   - Otherwise run `rm -rf \u003Cout>` and continue with `.agents\u002Fskills\u002Frepo-kit-update\u002FSKILL.md` for the same `\u003Cname>` from its first step. Do not run the rest of this skill.\n8. When `cd \u003Cclone> && git rev-parse --verify --quiet refs\u002Fheads\u002F\u003Cbranch>` or `cd \u003Cclone> && git rev-parse --verify --quiet refs\u002Fremotes\u002Forigin\u002F\u003Cbranch>` prints anything, stop with S11.\n9. Compare the clone with the kit.\n   - With Python: `cd \u003Cws> && python3 tools\u002Frepo_kit.py status \u003Cname> repos\u002F\u003Cname>`. When it exits 2, stop with S4 and use its error line as the reason.\n   - Without Python: apply `## Recipe: status`.\n   Each output line is `\u003Cstate> \u003Cpath>`. Before the folder move the paths still read `.agents\u002F...`; the files behind them are under `\u003Cbase>`. Without a stamp only `absent`, `same`, `edited` and `foreign` occur.\n10. Collect decisions before writing anything. Show the person every `edited` path. For each path `.agents\u002F\u003Cp>`, show the difference with `diff \u003Cbase>\u002F\u003Cp> \u003Cout>\u002F.agents\u002F\u003Cp>`. When `\u003Cbase>` is `\u003Cclone>\u002F.agent`, show it with the old links normalized instead: `LC_ALL=C sed 's#\\.agent\u002F#.agents\u002F#g' \u003Cbase>\u002F\u003Cp> | diff - \u003Cout>\u002F.agents\u002F\u003Cp>`. When that `diff` prints nothing, the file differs only in `.agent\u002F` links, which step 13 repairs: tell the person so and write down `kit` for the path without asking. Otherwise ask for one decision:\n    - `kit`: the clone file is replaced by the kit file; the clone text is lost.\n    - `local`: the clone text moves to `.agents\u002Flocal\u002F\u003Cp>`, and the kit file takes its place. When `test -e \u003Cbase>\u002Flocal\u002F\u003Cp>` succeeds, that place is taken: tell the person and ask again for `kit` or `raise`.\n    - `raise`: the kit itself must change first.\n    Write the decisions down as `\u003Cdecision> \u003Cpath>`. When the person gives any other word, ask again. When there is no `edited` path, there is nothing to ask.\n11. When any path got `raise`, run `rm -rf \u003Cout>` and stop with S13, naming that path. The clone has no new branch and no changed file.\n12. Create the branch: `cd \u003Cclone> && git switch -c \u003Cbranch>`. From here on the clone changes.\n13. Move the folder and repair links, only when `\u003Cbase>` is `\u003Cclone>\u002F.agent`:\n    1. `cd \u003Cclone> && git mv .agent .agents`. From now on `\u003Cbase>` is `\u003Cclone>\u002F.agents`.\n    2. List the lines that still link to the old folder: `cd \u003Cclone> && grep -rnI --exclude-dir=.git --exclude='.env' --exclude='.env.*' '\\.agent\u002F' .`. Files named `.env` or `.env.*` are never read.\n    3. In every listed line change `.agent\u002F` to `.agents\u002F` and change nothing else in the file. Remember the listed files outside `.agents\u002F` for step 19.\n    4. Run the `grep` of sub-step 2 again; it prints nothing.\n\n    This step runs before step 14, so text that step 14 moves to `.agents\u002Flocal\u002F` under a `local` decision already has its `.agent\u002F` links repaired.\n14. Apply the decisions, for each `edited` path `.agents\u002F\u003Cp>`:\n    - `kit`: `cd \u003Cclone> && cp \u003Cout>\u002F.agents\u002F\u003Cp> .agents\u002F\u003Cp>`.\n    - `local`: `cd \u003Cclone> && mkdir -p \"$(dirname .agents\u002Flocal\u002F\u003Cp>)\" && mv .agents\u002F\u003Cp> .agents\u002Flocal\u002F\u003Cp> && cp \u003Cout>\u002F.agents\u002F\u003Cp> .agents\u002F\u003Cp>`.\n15. Copy every `absent` path `.agents\u002F\u003Cp>`: `cd \u003Cclone> && mkdir -p \"$(dirname .agents\u002F\u003Cp>)\" && cp \u003Cout>\u002F.agents\u002F\u003Cp> .agents\u002F\u003Cp>`. Leave `same` paths as they are and do not touch `foreign` paths.\n16. Write the stamp.\n    - With Python: `cd \u003Cws> && python3 tools\u002Frepo_kit.py stamp \u003Cname> repos\u002F\u003Cname>`.\n    - Without Python: apply `## Recipe: stamp`.\n    Then run step 9 again. Every kit path must now be `same`; `foreign` paths stay. When another state is left, stop: run `rm -rf \u003Cout>`, tell the person every line whose state is neither `same` nor `foreign`, and print these commands for the person to discard the attempt. Do not run them yourself:\n    ```\n    cd \u003Cclone> && git reset --hard && git clean -fd\n    cd \u003Cclone> && git switch \u003Cdefault> && git branch -d \u003Cbranch>\n    ```\n    The first line removes every uncommitted change of this attempt, staged or untracked, including the folder move. The second returns the clone to `\u003Cdefault>` and deletes `\u003Cbranch>`. Step 6 made sure the clone had no uncommitted or untracked files before, so nothing else is lost.\n17. Check the root `AGENTS.md` of the clone. The clone owns it; the kit never rewrites it.\n    - `cd \u003Cclone> && grep -n '\\.agents\u002FAGENTS\\.md' AGENTS.md` and `cd \u003Cclone> && grep -n '\\.agents\u002Flocal\u002F' AGENTS.md`. A command that prints a line means that link exists.\n    - When both print a line, change nothing.\n    - Otherwise propose one line to the person, by what is missing, and add it as the last line of `AGENTS.md` only when the person agrees. When `AGENTS.md` does not exist, propose creating it with only that line.\n      ```\n      Both missing:            Agent instructions: [.agents\u002FAGENTS.md](.agents\u002FAGENTS.md). Repository-only rules and skills: [.agents\u002Flocal\u002F](.agents\u002Flocal\u002F).\n      Only .agents\u002Flocal\u002F:     Repository-only rules and skills: [.agents\u002Flocal\u002F](.agents\u002Flocal\u002F).\n      Only .agents\u002FAGENTS.md:  Agent instructions: [.agents\u002FAGENTS.md](.agents\u002FAGENTS.md).\n      ```\n      Write only the text after the label and the spaces.\n    - When the line links to `.agents\u002Flocal\u002F` and `test -d \u003Cclone>\u002F.agents\u002Flocal` fails, run `cd \u003Cclone> && mkdir -p .agents\u002Flocal && touch .agents\u002Flocal\u002F.gitkeep` so the link resolves.\n18. List every `foreign` path from step 9. These files belong to the repository: do not move or change them. For each `.agents\u002F\u003Cp>` propose `git mv .agents\u002F\u003Cp> .agents\u002Flocal\u002F\u003Cp>` to the person as a later change of their own.\n19. Run `rm -rf \u003Cout>`. Print these commands for the person and do not run them. The repository's forge is `forge` of the entry, not the forge of this workspace:\n    ```\n    cd \u003Cclone>\n    git add -A .agents \u003Cfiles changed in step 13 outside .agents> \u003CAGENTS.md when step 17 changed it>\n    git commit -m \"chore(agents): install kit \u003Ckind> \u003Cversion>\"\n    ```\n    Then, by `forge`:\n    - `gitlab`: `git push -u origin \u003Cbranch> -o merge_request.create -o merge_request.title=\"Install kit \u003Ckind> \u003Cversion>\"`;\n    - `github`: `git push -u origin \u003Cbranch>`, then `gh pr create --fill`;\n    - `git`: `git push -u origin \u003Cbranch>`, then open the merge request by hand.\n    Tell the person to adjust the commit message to the repository's own commit rules when it has them.\n20. Report to the person: `\u003Cbranch>`; the decisions; the files copied; the files with repaired links; the `AGENTS.md` line proposed or added; the `foreign` list; the printed commands. Never commit or push yourself.\n\n## Example\nWorkspace entry `payments-worker` with kit `example` version `0.1.0` and `\"params\": {\"SERVICE\": \"payments-worker\"}`, forge `gitlab`, default branch `main`. The kit has `files\u002FAGENTS.md`, `files\u002Frules\u002Fexample.md` and `files\u002Fskills\u002Fexample\u002FSKILL.md`. The clone `repos\u002Fpayments-worker` is clean on `main` and has no `.agents\u002F`, but has `.agent\u002FAGENTS.md` equal to the rendered file, `.agent\u002Frules\u002Fexample.md` edited by hand, and `.agent\u002Fnotes.md`. Its root `AGENTS.md` says `See .agent\u002FAGENTS.md.`\n\n- Step 9 prints:\n  ```\n  same .agents\u002FAGENTS.md\n  foreign .agents\u002Fnotes.md\n  edited .agents\u002Frules\u002Fexample.md\n  absent .agents\u002Fskills\u002Fexample\u002FSKILL.md\n  ```\n- Step 10: the person decides `local .agents\u002Frules\u002Fexample.md`.\n- Steps 12 to 16: branch `repo-kit-example-0.1.0`; `git mv .agent .agents`; root `AGENTS.md` becomes `See .agents\u002FAGENTS.md.`; `.agents\u002Frules\u002Fexample.md` moves to `.agents\u002Flocal\u002Frules\u002Fexample.md` and the kit file replaces it; `.agents\u002Fskills\u002Fexample\u002FSKILL.md` is copied; the stamp is written as in `## Recipe: stamp`. Step 9 again prints `same` for the three kit paths and `foreign .agents\u002Fnotes.md`.\n- Step 17: `AGENTS.md` links to `.agents\u002FAGENTS.md` but not to `.agents\u002Flocal\u002F`; the proposed line is `Repository-only rules and skills: [.agents\u002Flocal\u002F](.agents\u002Flocal\u002F).` The folder exists after the `local` decision.\n- Step 18 proposes `git mv .agents\u002Fnotes.md .agents\u002Flocal\u002Fnotes.md`.\n- Step 19 prints `git add -A .agents AGENTS.md`, the commit command and `git push -u origin repo-kit-example-0.1.0 -o merge_request.create -o merge_request.title=\"Install kit example 0.1.0\"`.\n\n## Recipe: render\nGives exactly the files `python3 tools\u002Frepo_kit.py render \u003Cname> \u003Cout>` writes.\n\n1. Values. For every parameter in `params` of `\u003Ckitdir>\u002Fkit.json`, take its value from `kit.params` of the entry. The recipe replaces placeholders with `sed`, so it works only when no value contains `\u002F`, `&`, `\\`, `\"`, `'`, `__`, a tab, a line break or another control character. For such a value stop with S12.\n2. Placeholders. Run `cd \u003Ckitdir>\u002Ffiles && LC_ALL=C grep -rhoaE '__[A-Z][A-Z0-9_]*__' . | LC_ALL=C sort -u`. Every printed line must be `__\u003CNAME>__` for a `\u003CNAME>` in `params`. For any other line find the file with `cd \u003Ckitdir>\u002Ffiles && LC_ALL=C grep -rlaF '\u003Cline>' .` and stop with S4, reason `kit \u003Ckind>: files\u002F\u003Cfile> uses undeclared placeholder \u003CNAME>`.\n3. Files. Kit files are every file under `\u003Ckitdir>\u002Ffiles\u002F` except files inside `__pycache__` folders. File names must not contain `\"`, `\\` or control characters; otherwise stop with S12 naming the file instead of a parameter. Copy each file `files\u002F\u003Cp>` to `\u003Cout>\u002F.agents\u002F\u003Cp>`, with one `sed` expression `-e 's\u002F__\u003CNAME>__\u002F\u003Cvalue>\u002Fg'` per parameter, in the order of `params`. `LC_ALL=C` makes `sed` treat the file as bytes, so line endings, a missing last newline and any encoding stay as they are:\n   ```\n   cd \u003Ckitdir>\u002Ffiles && LC_ALL=C find . -type f ! -path '*\u002F__pycache__\u002F*' | LC_ALL=C sort | while IFS= read -r p; do p=${p#.\u002F}; mkdir -p \"\u003Cout>\u002F.agents\u002F$(dirname \"$p\")\" && LC_ALL=C sed -e 's\u002F__\u003CNAME1>__\u002F\u003Cvalue1>\u002Fg' -e 's\u002F__\u003CNAME2>__\u002F\u003Cvalue2>\u002Fg' \"$p\" > \"\u003Cout>\u002F.agents\u002F$p\"; done\n   ```\n\nExample for kit `example` with the one parameter `SERVICE` = `payments-worker`, `\u003Ckitdir>` = `\u003Cws>\u002F.agents\u002Frepo-kits\u002Fexample` and `\u003Cout>` = `\u002Ftmp\u002Ftmp.k3Jd9`:\n```\ncd \u003Cws>\u002F.agents\u002Frepo-kits\u002Fexample\u002Ffiles && LC_ALL=C grep -rhoaE '__[A-Z][A-Z0-9_]*__' . | LC_ALL=C sort -u\n```\nprints only `__SERVICE__`, which is declared. Then:\n```\ncd \u003Cws>\u002F.agents\u002Frepo-kits\u002Fexample\u002Ffiles && LC_ALL=C find . -type f ! -path '*\u002F__pycache__\u002F*' | LC_ALL=C sort | while IFS= read -r p; do p=${p#.\u002F}; mkdir -p \"\u002Ftmp\u002Ftmp.k3Jd9\u002F.agents\u002F$(dirname \"$p\")\" && LC_ALL=C sed -e 's\u002F__SERVICE__\u002Fpayments-worker\u002Fg' \"$p\" > \"\u002Ftmp\u002Ftmp.k3Jd9\u002F.agents\u002F$p\"; done\n```\nResult: `\u002Ftmp\u002Ftmp.k3Jd9\u002F.agents\u002FAGENTS.md`, `\u002Ftmp\u002Ftmp.k3Jd9\u002F.agents\u002Frules\u002Fexample.md` and `\u002Ftmp\u002Ftmp.k3Jd9\u002F.agents\u002Fskills\u002Fexample\u002FSKILL.md`. The first line of the rendered `AGENTS.md` is `# payments-worker`, and no rendered file contains `__SERVICE__`.\n\n## Recipe: status\nGives exactly the lines `python3 tools\u002Frepo_kit.py status \u003Cname> repos\u002F\u003Cname>` prints. It needs `\u003Cout>` from `## Recipe: render`. A digest is the first 64 characters of `\u003Csha256>` run on the file as standard input: `shasum -a 256 \u003C \u003Cfile> | cut -c 1-64`. The stamp `\u003Cclone>\u002F.agents\u002Fkit.json` is read as `## Recipe: stamp` writes it: one `files` entry per line, `    \"\u003Cpath>\": \"\u003Cdigest>\"`. The stamp digest of a path is `grep -F '    \"\u003Cpath>\": \"' \u003Cclone>\u002F.agents\u002Fkit.json | head -n 1 | cut -d '\"' -f 4`; it is empty when there is no stamp or no such line.\n\nFor every rendered path `.agents\u002F\u003Cp>`, the clone file `F` is `\u003Cbase>\u002F\u003Cp>`:\n- `absent`: `F` does not exist;\n- `same`: `cmp -s \u003Cout>\u002F.agents\u002F\u003Cp> F` succeeds;\n- `replaceable`: otherwise, when the stamp digest of the path is not empty and equals the digest of `F`;\n- `edited`: otherwise.\n\nFor every path `P` in the stamp's `files` that is not rendered (`test -f \u003Cout>\u002FP` fails), starts with `.agents\u002F`, has no `..` segment, and whose clone file `\u003Cbase>\u002F\u003CP without .agents\u002F>` exists:\n- `obsolete`: the stamp digest equals the digest of that file;\n- `removed-edited`: otherwise.\nA stamp path whose clone file is missing prints nothing.\n\nFor every file under `\u003Cbase>`, as the path `.agents\u002F\u003Cp>`: `foreign` when it is not rendered, not a key in the stamp's `files`, not `.agents\u002Fkit.json` and not under `.agents\u002Flocal\u002F`.\n\nSort all lines by path, byte by byte. The commands, with the three values set in the first line:\n```\nOUT=\u003Cout>; CLONE=\u003Cclone>; BASE=\u003Cbase>\nSTAMP=\"$CLONE\u002F.agents\u002Fkit.json\"\n{\n  cd \"$OUT\" && LC_ALL=C find .agents -type f | while IFS= read -r P; do\n    F=\"$BASE\u002F${P#.agents\u002F}\"\n    if [ ! -f \"$F\" ]; then echo \"absent $P\"\n    elif cmp -s \"$P\" \"$F\"; then echo \"same $P\"\n    else\n      H=$( [ -f \"$STAMP\" ] && grep -F \"    \\\"$P\\\": \\\"\" \"$STAMP\" | head -n 1 | cut -d '\"' -f 4 )\n      D=$(shasum -a 256 \u003C \"$F\" | cut -c 1-64)\n      if [ -n \"$H\" ] && [ \"$H\" = \"$D\" ]; then echo \"replaceable $P\"; else echo \"edited $P\"; fi\n    fi\n  done\n  [ -f \"$STAMP\" ] && sed -n '\u002F^  \"files\": {\u002F,\u002F^  }\u002Fp' \"$STAMP\" | grep '^    \"' | while IFS= read -r L; do\n    P=$(printf '%s\\n' \"$L\" | cut -d '\"' -f 2); H=$(printf '%s\\n' \"$L\" | cut -d '\"' -f 4)\n    case \"$P\" in .agents\u002F*) ;; *) continue ;; esac\n    case \"\u002F$P\u002F\" in *\u002F..\u002F*) continue ;; esac\n    [ -f \"$OUT\u002F$P\" ] && continue\n    F=\"$BASE\u002F${P#.agents\u002F}\"\n    [ -f \"$F\" ] || continue\n    if [ \"$(shasum -a 256 \u003C \"$F\" | cut -c 1-64)\" = \"$H\" ]; then echo \"obsolete $P\"; else echo \"removed-edited $P\"; fi\n  done\n  [ -d \"$BASE\" ] && cd \"$BASE\" && LC_ALL=C find . -type f | while IFS= read -r p; do\n    P=\".agents\u002F${p#.\u002F}\"\n    case \"$P\" in .agents\u002Fkit.json|.agents\u002Flocal\u002F*) continue ;; esac\n    [ -f \"$OUT\u002F$P\" ] && continue\n    [ -f \"$STAMP\" ] && grep -qF \"    \\\"$P\\\": \\\"\" \"$STAMP\" && continue\n    echo \"foreign $P\"\n  done\n} | LC_ALL=C sort -k 2\n```\nReplace both `shasum -a 256` with `sha256sum` when `shasum` is missing. The block runs the same in `sh`, `bash` and `zsh`.\n\nExample: the clone of `## Example` before the move, so `BASE=\u003Cws>\u002Frepos\u002Fpayments-worker\u002F.agent`, no stamp, `\u003Cout>` from `## Recipe: render`. `.agent\u002FAGENTS.md` equals the rendered file, `.agent\u002Frules\u002Fexample.md` differs, `.agent\u002Fskills\u002F` does not exist, and `.agent\u002Fnotes.md` is not a kit file. The lines are:\n```\nsame .agents\u002FAGENTS.md\nforeign .agents\u002Fnotes.md\nedited .agents\u002Frules\u002Fexample.md\nabsent .agents\u002Fskills\u002Fexample\u002FSKILL.md\n```\nWith a stamp holding the digest of the current `.agent\u002Frules\u002Fexample.md`, that line would be `replaceable .agents\u002Frules\u002Fexample.md` instead.\n\n## Recipe: stamp\nGives exactly the bytes of `\u003Cclone>\u002F.agents\u002Fkit.json` that `python3 tools\u002Frepo_kit.py stamp \u003Cname> repos\u002F\u003Cname>` writes. It needs `\u003Cout>` from `## Recipe: render`, and the value rules of that recipe hold here too.\n\nThe file has these lines, each ending with a line break, and nothing else:\n1. `{`\n2. `  \"kind\": \"\u003Ckind>\",`\n3. `  \"version\": \"\u003Cversion>\",`\n4. `  \"params\": {`\n5. one line per parameter, in the order of `params` in `\u003Ckitdir>\u002Fkit.json`: `    \"\u003CNAME>\": \"\u003Cvalue>\"`, with a comma after every line except the last;\n6. `  },`\n7. `  \"files\": {`\n8. one line per rendered file, sorted by path byte by byte: `    \".agents\u002F\u003Cp>\": \"\u003Cdigest of \u003Cout>\u002F.agents\u002F\u003Cp>>\"`, with a comma after every line except the last;\n9. `  }`\n10. `}`\n\nA kit without parameters writes the single line `  \"params\": {},` instead of lines 4 to 6; a kit without files writes `  \"files\": {}` instead of lines 7 to 9. This is how the tool prints an empty object.\n\nThe commands, with one argument per parameter line in the second `printf`. For a kit without parameters that line is `printf '%s\\n' '  \"params\": {},'` instead. The files part needs no change: it prints `  \"files\": {}` when `\u003Cout>` has no `.agents\u002F` files.\n```\nmkdir -p \u003Cclone>\u002F.agents && cd \u003Cout> && {\n  printf '%s\\n' '{' '  \"kind\": \"\u003Ckind>\",' '  \"version\": \"\u003Cversion>\",'\n  printf '%s\\n' '  \"params\": {' '    \"\u003CNAME1>\": \"\u003Cvalue1>\",' '    \"\u003CNAME2>\": \"\u003Cvalue2>\"' '  },'\n  FILES=$( [ -d .agents ] && LC_ALL=C find .agents -type f | LC_ALL=C sort | while IFS= read -r f; do printf '    \"%s\": \"%s\",\\n' \"$f\" \"$(shasum -a 256 \u003C \"$f\" | cut -c 1-64)\"; done | LC_ALL=C sed '$ s\u002F,$\u002F\u002F' )\n  if [ -n \"$FILES\" ]; then printf '%s\\n' '  \"files\": {' \"$FILES\" '  }'; else printf '%s\\n' '  \"files\": {}'; fi\n  printf '%s\\n' '}'\n} > \u003Cclone>\u002F.agents\u002Fkit.json\n```\nUse `sha256sum` instead of `shasum -a 256` when `shasum` is missing.\n\nExample for `## Example`, `\u003Cout>` = `\u002Ftmp\u002Ftmp.k3Jd9`:\n```\nmkdir -p \u003Cws>\u002Frepos\u002Fpayments-worker\u002F.agents && cd \u002Ftmp\u002Ftmp.k3Jd9 && {\n  printf '%s\\n' '{' '  \"kind\": \"example\",' '  \"version\": \"0.1.0\",'\n  printf '%s\\n' '  \"params\": {' '    \"SERVICE\": \"payments-worker\"' '  },'\n  FILES=$( [ -d .agents ] && LC_ALL=C find .agents -type f | LC_ALL=C sort | while IFS= read -r f; do printf '    \"%s\": \"%s\",\\n' \"$f\" \"$(shasum -a 256 \u003C \"$f\" | cut -c 1-64)\"; done | LC_ALL=C sed '$ s\u002F,$\u002F\u002F' )\n  if [ -n \"$FILES\" ]; then printf '%s\\n' '  \"files\": {' \"$FILES\" '  }'; else printf '%s\\n' '  \"files\": {}'; fi\n  printf '%s\\n' '}'\n} > \u003Cws>\u002Frepos\u002Fpayments-worker\u002F.agents\u002Fkit.json\n```\nThe written `repos\u002Fpayments-worker\u002F.agents\u002Fkit.json`, with a line break after the last `}`:\n```json\n{\n  \"kind\": \"example\",\n  \"version\": \"0.1.0\",\n  \"params\": {\n    \"SERVICE\": \"payments-worker\"\n  },\n  \"files\": {\n    \".agents\u002FAGENTS.md\": \"27ff1ccb6beb7cb7b873f3d9c173ff18e74fbb30572c299987bb09055b1d77b4\",\n    \".agents\u002Frules\u002Fexample.md\": \"e31c19605d14f680052c8bb7550bd2132105a0eacda42e9db2a11809743af543\",\n    \".agents\u002Fskills\u002Fexample\u002FSKILL.md\": \"777eb69778449f5ffa502dafaf1fee70914792262e0448e43a312adce57bd70b\"\n  }\n}\n```\n\n## Without Python\n1. Step 2: without `python3`, one of `shasum` or `sha256sum` must exist; with neither, stop with S1.\n2. Step 4: check each value against its `pattern` with the `grep -Ex` command of step 4, or by reading when the pattern uses syntax `grep -E` does not support; the whole value must match.\n3. Step 5: apply `## Recipe: render` instead of `tools\u002Frepo_kit.py render`.\n4. Steps 9 and 16: apply `## Recipe: status` instead of `tools\u002Frepo_kit.py status`.\n5. Step 16: apply `## Recipe: stamp` instead of `tools\u002Frepo_kit.py stamp`.\n6. The skill changes no workspace file, so there is no workspace check to run.\n",{"name":5,"description":7},"main","84be7f584d7d6998f014342de57ee511e9596cd2","tests\u002Ffixtures\u002Fnormalize-team\u002F.agents\u002Fskills\u002Frepo-kit-install","https:\u002F\u002Fgithub.com\u002Fmaximk777\u002Fopencode-config","https:\u002F\u002Fgithub.com\u002Fmaximk777","2026-10-30 20:22:07",{"source":8,"skillName":5,"commands":30,"prompt":40,"zipAvailable":41},[31,34,37],{"tool":32,"command":33},"npx","npx skills add maximk777\u002Fopencode-config --skill repo-kit-install",{"tool":35,"command":36},"bunx","bunx skills add maximk777\u002Fopencode-config --skill repo-kit-install",{"tool":38,"command":39},"pnpm","pnpm dlx skills add maximk777\u002Fopencode-config --skill repo-kit-install","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmaximk777\u002Fopencode-config\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fnormalize-team\u002F.agents\u002Fskills\u002Frepo-kit-install\u002FSKILL.md",true,[],[44,51,58,65,72,79],{"skillNo":45,"name":46,"nameZh":6,"description":47,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":48,"categories":49,"keywords":50,"publishedAt":18},"01M7CQCJ5WYEQM6E1T0RDVKWAY","verify","Use when a change in __SERVICE__ must be checked before review","https:\u002F\u002Fgithub.com\u002Fmaximk777\u002Fopencode-config\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fworkspace-repo-kits\u002Fkit-1.1.0\u002Ffiles\u002Fskills\u002Fverify\u002FSKILL.md",[],[],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":18},"01M7CQCG5MCSNDNS98TGAGXP7E","work-record","Use when you finished work on a tracker task and it must be recorded in the workspace through a merge request.","https:\u002F\u002Fgithub.com\u002Fmaximk777\u002Fopencode-config\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fnormalize-team\u002F.claude\u002Fskills\u002Fwork-record\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":18},"01M7CQCDGQBT2GXCKQAC1B5R0R","task-new","Use to create one story in a stream from the stream profile's story template, link it from its scope screens and open a merge request.","https:\u002F\u002Fgithub.com\u002Fmaximk777\u002Fopencode-config\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fnormalize-team\u002F.claude\u002Fskills\u002Ftask-new\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":18},"01M7CQC93WN986EY48RFPZHZM7","task-decompose","Use to split a stream at the decomposition stage into stories - list scope screens without a story, create the accepted stories and close the stage through a merge request.","https:\u002F\u002Fgithub.com\u002Fmaximk777\u002Fopencode-config\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fnormalize-team\u002F.claude\u002Fskills\u002Ftask-decompose\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"01M7CQC5FZQWPTBK0J0FHWS513","task-context","Use to gather the context of a story key or a tracker id - its story, stream stage, scope screens, repositories, decisions, mockups and work records.","https:\u002F\u002Fgithub.com\u002Fmaximk777\u002Fopencode-config\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fnormalize-team\u002F.claude\u002Fskills\u002Ftask-context\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":18},"01M7CQC1Q2YECCM2N9TPJAAJQA","repos-sync","Use to update clones of your repositories under repos\u002F and see their branch, lag and uncommitted changes.","https:\u002F\u002Fgithub.com\u002Fmaximk777\u002Fopencode-config\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fnormalize-team\u002F.claude\u002Fskills\u002Frepos-sync\u002FSKILL.md",[],[]]