update-acumen

스타11

포크1

업데이트2026년 4월 9일 12:27

Fetch the latest Acumen skills from GitHub and update local copies (source, .agents, .claude symlinks).

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

출처

VGrss

VGrss/Acumen

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Step 1: Fetch the current skill index from GitHub

Use gh to list the skill directories in the repo:

gh api repos/VGrss/Acumen/git/trees/main:source/skills --jq '.tree[] | select(.type == "tree") | .path'

This gives you the list of all skill names in the upstream repo.

Also list the local skills in source/skills/ to compare.

Report what's new, removed, or already present.

Step 2: Sync each skill's content

For every skill found upstream, fetch its files recursively. Each skill lives at source/skills/{name}/ and may contain SKILL.md plus optional subdirectories (e.g. reference/).

For each skill directory:

Get the file tree for that skill:

gh api repos/VGrss/Acumen/git/trees/main:source/skills/{name} --jq '.tree[]'

For each file, fetch its raw content and write it locally:
```
gh api repos/VGrss/Acumen/contents/source/skills/{name}/{file} --jq '.content' | base64 -d
```
Write the decoded content to source/skills/{name}/{file}.
For subdirectories (like reference/), recurse: list the subtree, then fetch each file inside it.

Step 3: Distribute to .agents and .claude

After syncing source/skills/, replicate the distribution structure:

Copy to .agents/skills/: For each skill, copy the entire source/skills/{name}/ directory to .agents/skills/{name}/.
```
cp -r source/skills/{name} .agents/skills/{name}
```
Create .claude/skills/ symlinks: For any new skill that doesn't already have a symlink:
```
ln -sf ../../.agents/skills/{name} .claude/skills/{name}
```
Clean up removed skills: If a skill exists locally but not upstream, report it to the user and ask whether to remove it.

Step 4: Report

Print a summary:

Updated: skills whose content changed
Added: new skills not previously present locally
Unchanged: skills that were already up to date
Removed upstream (if any): skills present locally but missing from the repo — ask the user what to do

Include the total skill count and confirm the distribution is in sync.

이 저장소의 다른 Skills

같은 저장소

increment

VGrss/Acumen

Scope a single product increment end-to-end — context, spec, implementation, wireframes, and engineering considerations. Use when a feature or bet needs a shippable document before building — typically the option chosen out of /workshop's divergence. Leads to /critique-product.

2026-07-3111

cheatsheet

VGrss/Acumen

Print a quick-reference cheatsheet of all Acumen skills, organized by layer.

2026-07-1711

catchup

VGrss/Acumen

Pull latest code from main, summarize recent changes in product-friendly terms, and report .acumen/ context health (what exists, what's fresh, what's stale, what's missing). Preserves all .acumen/ context files.

2026-07-0911

critique-product

VGrss/Acumen

Evaluate and validate a PM artifact — score for rigor, test riskiest assumptions, and decide if it's ready to ship. Use when reviewing a PRD, spec, increment, strategy, or roadmap.

2026-07-0911

diagnose

VGrss/Acumen

Find what's broken and what's underexploited — problems AND opportunities — grounded in data, value delivery per persona, and current features. The entry point to ideation; hands sharp problems and opportunities to /workshop.

2026-07-0911

teach-acumen

VGrss/Acumen

One-time setup that gathers product context for your project and saves it to .acumen.md. Run once to establish persistent product guidelines.

2026-07-0911

name	update-acumen
description	Fetch the latest Acumen skills from GitHub and update local copies (source, .agents, .claude symlinks).
user-invocable	true

Pull the latest skills from the Acumen repo and sync them into this project.

Source repo: VGrss/Acumen on GitHub (branch: main)

Step 1: Fetch the current skill index from GitHub

Use gh to list the skill directories in the repo:

gh api repos/VGrss/Acumen/git/trees/main:source/skills --jq '.tree[] | select(.type == "tree") | .path'

This gives you the list of all skill names in the upstream repo.

Also list the local skills in source/skills/ to compare.

Report what's new, removed, or already present.

Step 2: Sync each skill's content

For every skill found upstream, fetch its files recursively. Each skill lives at source/skills/{name}/ and may contain SKILL.md plus optional subdirectories (e.g. reference/).

For each skill directory:

Get the file tree for that skill:

gh api repos/VGrss/Acumen/git/trees/main:source/skills/{name} --jq '.tree[]'

For each file, fetch its raw content and write it locally:
```
gh api repos/VGrss/Acumen/contents/source/skills/{name}/{file} --jq '.content' | base64 -d
```
Write the decoded content to source/skills/{name}/{file}.
For subdirectories (like reference/), recurse: list the subtree, then fetch each file inside it.

Step 3: Distribute to .agents and .claude

After syncing source/skills/, replicate the distribution structure:

Copy to .agents/skills/: For each skill, copy the entire source/skills/{name}/ directory to .agents/skills/{name}/.
```
cp -r source/skills/{name} .agents/skills/{name}
```
Create .claude/skills/ symlinks: For any new skill that doesn't already have a symlink:
```
ln -sf ../../.agents/skills/{name} .claude/skills/{name}
```
Clean up removed skills: If a skill exists locally but not upstream, report it to the user and ask whether to remove it.

Step 4: Report

Print a summary:

Updated: skills whose content changed
Added: new skills not previously present locally
Unchanged: skills that were already up to date
Removed upstream (if any): skills present locally but missing from the repo — ask the user what to do

Include the total skill count and confirm the distribution is in sync.