upgrade
Skill4 starsChanged 7 days agoMITView on GitHub
Pull framework improvements from a newer release of the Agentic BI Team into a repo you have already configured — updating agents, skills, standards, and scripts while preserving your filled-in knowledge base and CLAUDE.md. Use when a new version ships, or when you cloned a while ago and want the latest.
- Reads credentials
32 other projects use a version of this.
Adopted by
Most recently taken up by
- Robo-Co-op/robobuilder-standardtheir own version, first seen Nov 16, 2026
- jianghailong-xy/orbittheir own version, first seen Nov 15, 2026
- Mrbaeksang/skillstheir own version, first seen Nov 8, 2026
- roedyrustam/doku-gemini-mcptheir own version, first seen Nov 8, 2026
- aminbadh/workspace-startertheir own version, first seen Nov 1, 2026
- ai-agent-lead/skillstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use new, context and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
codebycoreySkillnew
Start a new change with a proposal. Use when starting a feature, creating a proposal, or beginning planned work.
Also in 4 projects that use this
aegiswizardSkillcontext
Also in 3 projects that use this
MicrosoftSkillinit
Also in 6 projects that use this
AnthropicSkillstatus
Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.
Also in 5 projects that use this
tuistSkillmigrate
Migrates existing Xcode projects to Tuist generated workspaces with build and run validation, external dependency mapping, and migration checklists. Use when adopting Tuist for an existing app or converting a hand-edited Xcode project to generated projects.
Also in 3 projects that use this
imehrSkillfrontend
Use when building UI components, pages, or features - guides Claude through the approved frontend stack (Next.js 15, React 19, Shadcn, Tailwind) with design-first workflow for complex UIs, enforcing patterns and quality standards
Also in 3 projects that use this
Other versions32 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 32
- langwatch/langwatch★ 5ksame name
- agenticnotetaking/arscontexta★ 3.5ksame name
- heyitsnoah/claudesidian★ 2.6ksame name
- TokenRollAI/cc-plugin★ 483same name
- dcb/homeassistant-claude-kit★ 125same name
- rust-off-rails/rustoffrails★ 49same name
- rvdbreemen/adr-kit★ 13same name
- jamillazarev/multica-ops★ 11same name
- ivankuznetsov/llm-wiki★ 9same name
- jianghailong-xy/orbit★ 7same name
22 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository21 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- analyzeSkill
- build-dashboardSkill
- build-modelSkill
- build-pipelineSkill
- causal-analysisSkill
- connect-dataSkill
- define-kpisSkill
- evalSkill
- experimentSkill
- forecastSkill
- health-checkSkill
- investigate-metricSkill
- make-deliverableSkill
- powerbiSkill
- privacy-reviewSkill
- research-domainSkill
- scorecardSkill
- setup-teamSkill
- tableauSkill
- triageSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 1 is distinctive, and 4 are very specific to this project.
0
Common
Most of the 26 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 39
Read the local VERSION file.
- Very specific: line 43
If the local repo has no VERSION file, it predates 1.0.0.
- Distinctive: line 71
Deleted upstream: don't delete it locally without asking.
- Very specific: line 79
Never rewrite a knowledge file wholesale.
- Very specific: line 84
If a release adds a new knowledge file (data-quality-log.md, request-log.md, and incident-runbook.md all arrived in 1.0.0.
“Common” is measured: kept by at least 6 in 10 of the 26 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Upgrade — New Framework, Same Memory
Someone clones this kit, runs /setup-team, and spends six months accumulating metric
definitions, data quirks, decision rulings, and stakeholder preferences. Then a new
release adds an agent and fixes three skills. Re-cloning throws away the six months;
doing nothing means the improvements never land.
This skill separates the two. The repo is cleanly divided, and that division is what makes upgrading tractable:
| Files | On upgrade | |
| Framework | .claude/agents/, .claude/skills/, .claude/settings.json, standards/, scripts/, scheduling/, demo/, evals/demo/, evals/README.md, docs/, .github/, analytics.md, CONTRIBUTING.md, CHANGELOG.md, VERSION | replace with the new version, re-applying your local placeholder values |
| Yours | knowledge/* (including governance-policy.md and domains/), CLAUDE.md, START-HERE.md, analyses/, pipelines/, dashboards/, models/, experiments/, scorecards/, deliverables/, evals/local/, evals/results/, .claude/settings.local.json, .env, scripts/connections.json | never overwritten — merged by hand where a release requires it |
The complication is that framework files contain your configuration: /setup-team
replaced {{BI_TOOL}} with "Power BI" inside dashboard-developer.md. A naive copy
reverts that. Step 4 is where that's handled.
Procedure
1. Snapshot first
python scripts/setup_backup.pyNote the id. If the upgrade goes badly, --restore <id> --yes puts everything back.
Also check git status — a clean tree means git diff will show the user exactly what
the upgrade changed, which is worth a lot when reviewing.
2. Establish both versions
Read the local VERSION file. Get the new release (a git remote, a fresh clone in a temp
directory, or a downloaded archive — ask the user which they have; do not fetch anything
without saying where from).
If the local repo has no VERSION file, it predates 1.0.0. Say so — the changes are
larger, and step 6 matters more.
3. Read the changelog between the versions
CHANGELOG.md in the new release, every section between their version and the new one.
This is the whole point of the step: look specifically for anything describing a
changed layout or convention that user-filled files depend on. A new required key in
the metrics catalog, a renamed knowledge file, a changed placeholder name — those need
migration, not just a file copy.
Summarise for the user before touching anything: what's new, what changed, and specifically what will need a decision from them.
4. Update the framework files, preserving local configuration
For each framework file that differs:
- New file (an agent or skill that didn't exist): copy it in. If it contains
{{PLACEHOLDERS}}, fill them from the values already used elsewhere in the repo —python scripts/check_placeholders.py --listshows what is still unfilled, and the configured neighbours show what each value was set to. Don't re-interview the user for answers they've already given. - Changed file: diff it. Where the only differences are your filled-in placeholder values, take the new version and re-apply those values. Where the user has hand-edited the file beyond setup — a tuned agent prompt, a house rule added to a standard — stop and show them both versions. Their edit is deliberate and you must not silently discard it; ask whether to keep theirs, take the new one, or merge.
- Deleted upstream: don't delete it locally without asking. A file removed from the framework may be one they now depend on.
Hand-edited framework files are common, and they are the main reason this cannot be a script. Treat every one as a conversation.
5. Migrate user files only where the changelog requires it
Never rewrite a knowledge file wholesale. Where a release changes a required structure —
a new key in the metrics catalog, a new section in a template — add the structure and
leave the content alone, marking anything you cannot fill as > TODO (user): rather than
guessing.
If a release adds a new knowledge file (data-quality-log.md, request-log.md, and
incident-runbook.md all arrived in 1.0.0; governance-policy.md and domains/ in
1.2.0), copy the template in and let the user or /setup-team fill the standing
configuration.
Coming from before 1.2.0 — three things need a decision rather than a copy:
knowledge/governance-policy.mdis new and the guards read it. Until it is filled in, the team runs on the safe defaults (guarded, minimum group size 5) with an empty Column Registry — so nothing is classified and the query guard has nothing to act on. Fill the policy block from the privacy rules already in theirCLAUDE.mdprinciple 9 anddata-sources.md, ask the user for the enforcement level, and havegovernance-officerbuild the registry from the existing Data Dictionary..claude/settings.jsongained two hooks (the data-access guard and the audit log) and the MCP matcher on the destructive-SQL hook. If the user has edited their settings, merge thehooksblock in by hand and show them the diff; explain each hook fromdocs/governance.mdbefore enabling it. The audit log writes to.audit/, which the new.gitignoreexcludes — confirm that line landed.- Catalog entries gain optional keys —
classification,segments, andsegment_<name>. Nothing breaks without them. Addclassificationto ratified metrics (check_governance.pywarns where it is missing) and leave segments formetrics-stewardto introduce where a population filter is being hand-written.
Existing FINDINGS.md files and scorecards have no provenance footer. Leave them:
check_provenance.py reports those as warnings, not errors, and the footer applies to
work from here on.
6. Verify
python scripts/lint_repo.py
python scripts/check_placeholders.py
python scripts/check_metrics.py
python scripts/check_governance.py
python scripts/tests/run_tests.pythen /health-check. The test suite matters after an upgrade specifically: it proves
the guards still block what they should once your settings and theirs are merged.
The lint catches the most likely upgrade failure by far: a new agent or skill that landed
on disk but never got a row in CLAUDE.md's routing tables, and is therefore invisible to
the orchestrator. Then confirm the new VERSION file is in place — an upgrade that
doesn't bump the version makes the next one harder.
7. Report
What changed and what it gives them, what you preserved, what needs their decision, and the snapshot id for undo. Recommend committing the upgrade as its own commit, separate from any analysis work, so it can be reverted cleanly.
When the gap is very large
Several major versions behind, or heavily hand-edited, is sometimes better handled the
other way round: clone the new release fresh, copy knowledge/ and the work directories
across, and re-run /setup-team against the existing charter. Say so if that looks like
less work — the knowledge base is the valuable part, and it moves cleanly.
Created by Colin Beck — https://www.linkedin.com/in/beckcolin/
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

