setup-build-kb
Skill234 starsChanged 8 months agoMITView on GitHub
Synthesize completed extractions into the knowledge base files needed for resume generation
In this repository6 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- critiqueSkill
- edit-resumeSkill
- make-clSkill
- make-resumeSkill
- setup-extractSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. About 0 are common, 11 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
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
- Distinctive: line 20
Read CLAUDE.md — check KB Corrections Log
- Distinctive: line 25
Document Preferences (bullet variant defaults)
- Very specific: line 26
Read knowledge_base/extractions/_INVENTORY.md — verify extractions exist
- Very specific: line 30
If _INVENTORY.md is empty or has no entries: "No extractions found.
- Distinctive: line 31
If fewer than 2 extractions: warn "Only [N] extraction(s) found.
- Distinctive: line 39
Goal: Create one experience file per position, containing all achievements organized for resume generation.
- Very specific: line 41
Read: All extraction files listed in _INVENTORY.md
- Distinctive: line 46
Ask the user to confirm grouping if ambiguous: "I've grouped these papers under [Position].
- Distinctive: line 83
Ask user to review: "Are the groupings correct?
- Distinctive: line 90
Goal: Create a categorized inventory of all technical skills from extractions.
- Distinctive: line 92
Read: All extraction files (Methods & Tools sections) + experience files from Phase 1
- Distinctive: line 196
Ask user: "Does this priority mapping look right for your target roles?"
- Distinctive: line 304
After all phases complete (or after the requested subset), present:
- Very specific: line 324
If all checked: "Knowledge base is ready.
- Distinctive: line 325
If gaps: "[List what's missing and which phase to re-run]"
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/setup-build-kb
User input: $ARGUMENTS
Parse $ARGUMENTS:
- Empty → full build (all phases)
- Phase number (e.g.,
3) → resume from that phase - "experience" / "bundles" / "skills" / "pubs" / "reframing" / "significance" → run only that component
- "status" → show what's built and what's missing
Startup
- Read
CLAUDE.md— check KB Corrections Log - Read
config.md— load:- Personal Info (positions, institutions, dates)
- Role Types table (defines which bundles to create)
- Provenance Flags (propagate to all KB files)
- Document Preferences (bullet variant defaults)
- Read
knowledge_base/extractions/_INVENTORY.md— verify extractions exist - Scan
resume_builder/to see what's already built
Pre-flight check:
- If
_INVENTORY.mdis empty or has no entries: "No extractions found. Run/setup-extractfirst." Stop. - If fewer than 2 extractions: warn "Only [N] extraction(s) found. KB quality improves with more papers. Continue anyway?"
Progress: "Found [N] extractions across [M] positions. Config has [K] role types defined."
Phase 1: Build Experience Files
Goal: Create one experience file per position, containing all achievements organized for resume generation.
Read: All extraction files listed in _INVENTORY.md
For each position (from config.md or inferred from extraction metadata):
- Group extractions by the position they belong to (based on dates, institution, or user clarification)
- Ask the user to confirm grouping if ambiguous: "I've grouped these papers under [Position]. Correct?"
Experience file format (resume_builder/experience/experience_<position_key>.md):
# Experience: [Position Title] — [Institution]
## [Date Range]
### Cross-Position Section
[Brief narrative connecting this position's work to the user's broader trajectory]
[CL framing content — how this position fits the career arc]
---
### Achievement [ID]: [Short Title]
**Source:** [extraction filename]
**Paper:** [citation or "internal"/"unpublished"]
**User's role:** [first author / contributing / sole developer]
**Status:** [published / under review / draft / internal]
**Context:** [1-2 sentences — what problem, why it matters]
**Bullet variants:**
- **2L:** [Full 2-line bullet text — STAR format, ~180-210 rendered characters]
- **3L:** [Full 3-line bullet text — for CV use, ~270-310 rendered characters]
- **1L:** [Condensed 1-line version — ~90-110 rendered characters, for tight budgets]
**Key skills:** [comma-separated list of skills this achievement demonstrates]
**ATS keywords:** [domain-specific terms an ATS might scan for]
**Reframing notes:** [how to emphasize different aspects for different role types]
---
[Repeat for each achievement]>>>>>> MANDATORY STOP — DO NOT PROCEED <<<<<<
Present the experience file(s) — show achievement count per position, total bullet variants. Ask user to review: "Are the groupings correct? Any achievements missing or misattributed?" You MUST wait for the user's explicit text response before continuing.
Phase 2: Build Skills Taxonomy
Goal: Create a categorized inventory of all technical skills from extractions.
Read: All extraction files (Methods & Tools sections) + experience files from Phase 1
Build resume_builder/support/skills_taxonomy.md:
# Skills Taxonomy
## Summary Stats
- Total unique skills: [N]
- Publications: [N] ([breakdown by status])
- Top methods: [ranked list]
## Categories
### [Category 1: e.g., Computational Methods]
| Skill | Proficiency | Evidence | Resume Weight |
|-------|-----------|----------|---------------|
| [skill] | [expert/proficient/familiar] | [paper IDs] | [HIGH/MED/LOW] |
### [Category 2: e.g., Programming & Software]
[same table format]
### [Category 3: e.g., Machine Learning]
[same table format]
[Continue for all categories — typically 4-7 categories]Proficiency levels:
- Expert: Multiple first-author papers, developed custom tools
- Proficient: Used extensively in published work, comfortable teaching
- Familiar: Used in one project, or contributed to someone else's implementation
Progress: "Built taxonomy — [N] skills across [M] categories"
Phase 3: Build Publication Metadata
Goal: Structured pub data for resume/CV generation.
Build resume_builder/support/pub_metadata.md:
# Publication Metadata
## Summary
- Total publications: [N]
- First-author: [N] | Co-first: [N] | Contributing: [N]
- Published: [N] | Under review: [N] | In preparation: [N]
## Publication List
### First-Author / Co-First
| # | Citation (et al. format) | Journal | Year | Status | Key Topic |
|---|-------------------------|---------|------|--------|-----------|
| 1 | [Author et al., Journal, Year] | [journal] | [year] | [status] | [topic] |
### Contributing Author
[same table format]
### Under Review / In Preparation
[same table format, with provenance notes]Progress: "Pub metadata — [N] first-author, [M] contributing, [K] under review"
Phase 4: Build Achievement Reframing Guide
Goal: Per-achievement significance lines + framing directives for each role type.
Read: Experience files + config.md Role Types
Build resume_builder/support/achievement_reframing_guide.md:
# Achievement Reframing Guide
## How to Use
For each achievement, `Significance:` provides a one-line framing cue.
The role-type table shows how to emphasize/de-emphasize for each target audience.
---
### [Achievement ID]: [Title]
**Significance:** [One sentence — why this matters broadly]
| Role Type | Emphasis | Lead Verb | Framing Angle |
|-----------|----------|-----------|---------------|
| [role 1] | HIGH | Developed | [emphasize X aspect] |
| [role 2] | MEDIUM | Applied | [bridge to Y domain] |
| [role 3] | LOW | -- | [omit or condense] |
**Overclaiming warning:** [if applicable — e.g., "Do not claim sole credit for experimental results"]
**First-pass checklist:** [ ] Verb matches author role [ ] Numbers from paper [ ] Status matches provenance
---
[Repeat for each achievement]>>>>>> MANDATORY STOP — DO NOT PROCEED <<<<<<
Present the reframing guide summary — show which achievements are HIGH for which role types. Ask user: "Does this priority mapping look right for your target roles?" You MUST wait for the user's explicit text response before continuing.
Phase 5: Build Bundles
Goal: One bundle per role type from config.md, with 5 sections each.
Read: Experience files + Skills Taxonomy + Reframing Guide + config.md Role Types
For each role type, create resume_builder/bundles/bundle_<role_type>.md:
# Bundle: [Role Type Name]
> Target employers: [from config.md]
> Tier: [from config.md]
---
## S1: Role Profile & Priority Matrix
**Positioning:** [1-2 sentences — how to position the user for this role type]
### Priority Matrix
| Priority | Achievement IDs | Rationale |
|----------|----------------|-----------|
| HIGH | [IDs] | [why these lead for this role type] |
| MEDIUM | [IDs] | [supporting evidence, bridge topics] |
| LOW | [IDs] | [omit unless budget allows or JD specifically asks] |
---
## S2: Summary Guide
**Headline pattern:** [Role-appropriate headline template]
**Building blocks:** [3-5 phrases that should appear in summaries for this role type]
**Avoid:** [terms/framings that don't fit this audience]
---
## S3: Achievement Reframing Map
[For each HIGH/MEDIUM achievement: which angle to use, which metrics to lead with]
| ID | Default Framing | This Role's Framing | Key Metric |
|----|----------------|--------------------|-----------|
| [ID] | [generic] | [role-specific angle] | [number to highlight] |
---
## S4: Skills Guide
**Bold tools (resume):** [3-5 tools to bold in Technical Skills for this role type]
**Must-include skills:** [skills that MUST appear for ATS match]
**Nice-to-have:** [skills to include if budget allows]
**Omit:** [skills irrelevant to this audience]
---
## S5: Cover Letter Guide
**Institution type:** [Industry / National Lab / Academic]
**Opening hook pattern:** [template for first paragraph opener]
**Key narrative thread:** [what story to tell across paragraphs]
**"Why them" angle:** [what to research about target employer]
**Avoid:** [CL anti-patterns for this role type]Progress: "Building bundle for [role type] — [N] HIGH priority achievements, [M] bold tools"
Phase 6: Build Significance Research Files
Goal: Field context for cover letters — NOT for resume bullets.
For each position, create resume_builder/support/significance_<position_key>.md:
# Significance Research: [Position]
> Use in cover letters and summaries — NOT in resume bullet text.
> These provide field context that demonstrates the user understands the landscape.
---
### [Achievement ID]: Field Context
**The problem:** [What challenge does this address? Industry/scientific context]
**Competing approaches:** [What else exists? What are the limitations?]
**Why this matters:** [Market size, DOE/funding priorities, industry need]
**Differentiation:** [What makes the user's approach unique or better?]
---
[Repeat for each major achievement worth cover-letter depth]
### Field Overview: [Broad Topic]
[2-3 paragraphs of field context that multiple achievements contribute to]
[Useful for cover letter opening hooks and "why this matters" framing]Progress: "Significance research — [N] achievements with field context, [M] field overviews"
Final: Status Report
After all phases complete (or after the requested subset), present:
KB Build Status
| Component | File | Status | Items |
| Experience files | experience/*.md | [DONE/MISSING] | [N achievements] |
| Skills taxonomy | support/skills_taxonomy.md | [DONE/MISSING] | [N skills] |
| Pub metadata | support/pub_metadata.md | [DONE/MISSING] | [N pubs] |
| Reframing guide | support/achievement_reframing_guide.md | [DONE/MISSING] | [N entries] |
| Bundles | bundles/bundle_*.md | [DONE/MISSING] | [N bundles] |
| Significance | support/significance_*.md | [DONE/MISSING] | [N files] |
Ready for Generation?
- At least 1 experience file with 5+ achievements
- Skills taxonomy with 20+ skills
- At least 1 bundle matching a target role type
- Pub metadata complete
- Reframing guide covers all achievements
- Significance files for cover letter depth
If all checked: "Knowledge base is ready. Save a JD to JDs/ and run /make-resume JDs/<filename>.txt"
If gaps: "[List what's missing and which phase to re-run]"
>>>>>> MANDATORY STOP <<<<<<
Present status report. Wait for user confirmation. You MUST wait for the user's explicit text response before continuing.
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.

