critique
Skill234 starsChanged 8 months agoMITView on GitHub
Re-critique existing resume/CV output files against a JD
79 other projects use a version of this.
Adopted by
Most recently taken up by
- Lucface/claude-skillstheir own version, first seen Nov 16, 2026
- Integralist/agent-skillstheir own version, first seen Nov 14, 2026
- theexperiencecompany/gaiatheir own version, first seen Nov 13, 2026
- bas1l/claude-skillstheir own version, first seen Nov 11, 2026
- pche-broken-artist/forge-of-thoughttheir own version, first seen Nov 10, 2026
- BSchrift/critique.nvimtheir own version, first seen Nov 8, 2026
Used with
Projects with it also use delight, teach-impeccable 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.
HK-hubSkilldelight
Add moments of joy, personality, and unexpected touches that make interfaces memorable and enjoyable to use. Elevates functional to delightful. Use when the user asks to add polish, personality, animations, micro-interactions, delight, or make an interface feel fun or memorable.
Also in 32 projects that use this
HK-hubSkillteach-impeccable
One-time setup that gathers design context for your project and saves it to your AI config file. Run once to establish persistent design guidelines.
Also in 18 projects that use this
zwy123zwySkillnormalize
将用户随意输入的提示词规范化为结构清晰、便于大模型执行的标准化提示词。适用于需要整理、统一提示词格式时调用。
Also in 18 projects that use this
owshq-mecSkilllayout
Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition.
Also in 8 projects that use this
- +8 more from HK-hub
Other versions79 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 79
- google-gemini/gemini-cli★ 109ksame name
- yournextstore/yournextstore★ 5.5ksame name
- plugin87/ux-ui-agent-skills★ 3.2ksame name
- remorses/critique★ 1.3ksame name
- educlopez/ui-craft★ 441same name
- nexmoe/DayBee★ 424same name
- nexmoe/eve★ 424same name
- Southclaws/storyden★ 351same name
- 10xChengTu/Mux0★ 337same name
- theexperiencecompany/gaia★ 327same name
69 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 repository6 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- edit-resumeSkill
- make-clSkill
- make-resumeSkill
- setup-build-kbSkill
- setup-extractSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
24 rules. 0 are common, 10 are distinctive, and 14 are very specific to this project.
0
Common
Most of the 72 edited versions we read keep these.
10
Distinctive
This author's own choices. Worth a look.
14
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
If no CL .tex provided or found in session file, critique resume/CV alone (Part 7 adjustments noted below).
- Very specific: line 23
Read config.md Provenance Flags.
- Very specific: line 24
Check config.md KB Corrections Log — do not flag corrected items as errors.
- Very specific: line 25
Use the email from config.md Personal Info — flag if a different email appears in output.
- Distinctive: line 32
If the user provides feedback, corrections, or suggestions at any point:
- Distinctive: line 34
If it changes scoring criteria or focus: adjust the critique accordingly
- Distinctive: line 35
Never restart — resume from current position
- Very specific: line 41
Read resume_builder/reference/shared_ops.md — Fresh Session Startup + Session File Derivation.
- Very specific: line 42
Read CLAUDE.md — check Active Sessions and KB Corrections.
- Very specific: line 43
Read config.md — load Provenance Flags, FIXED Sections, email.
- Very specific: line 47
If CL not DONE in session file → "CL not yet generated.
- Distinctive: line 48
If Critique: CURRENT → "Already critiqued (score X/100).
- Distinctive: line 49
If Critique: STALE → "Edits made since last critique.
- Distinctive: line 50
If Critique: PENDING → proceed
- Distinctive: line 61
If session file lacks Company Context or Critique Context: do 1-2 web searches to fill gaps
- Very specific: line 63
Read resume_builder/support/ai_fingerprint_rules.md — use Section 6 checklist in Part 7 verification
- Very specific: line 64
Read the .tex file(s) — derive paths from session file Output Files, or from $ARGUMENTS
- Very specific: line 65
Read the JD (path from $ARGUMENTS or session file)
- Very specific: line 66
Read the relevant bundle (resume_builder/bundles/bundle_[role_type].md — from session file)
- Distinctive: line 75
Use the Read tool to view the compiled PDF — check orphans, page fill, header wrapping.
- Distinctive: line 76
If compile fails: note "COMPILE FAILED — visual checks could not be verified" in Part 8.
- Very specific: line 77
If a prior critique exists (output/<FolderName>/critique_<name>.md): read it and note previous score.
- Very specific: line 104
If edits needed, tell user to run /edit-resume.
- Very specific: line 107
Verify all expected files exist in output/<FolderName>/:
“Common” is measured: kept by at least 6 in 10 of the 72 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
/critique
User input: $ARGUMENTS
Parse $ARGUMENTS:
- Session file path (e.g.,
output/Acme/session_acme_engineer.md) → read session file, derive .tex paths from Output Files - .tex file path(s) + JD source (existing format) → backward compatible
- Session name (e.g.,
acme_engineer) → find session file via derivation
If no CL .tex provided or found in session file, critique resume/CV alone (Part 7 adjustments noted below).
Safety Rules
Accuracy > Relevance > Impact > ATS > Brevity
Read config.md Provenance Flags. Verify every claim against that table.
Check config.md KB Corrections Log — do not flag corrected items as errors.
Use the email from config.md Personal Info — flag if a different email appears in output.
FIXED sections (from config.md FIXED Sections) are template-locked — do not flag for editing. Flag only VARIABLE sections.
User Input During Execution
If the user provides feedback, corrections, or suggestions at any point:
- Acknowledge the input immediately
- If it changes scoring criteria or focus: adjust the critique accordingly
- Never restart — resume from current position
Startup
Read resume_builder/reference/shared_ops.md — Fresh Session Startup + Session File Derivation.
Read CLAUDE.md — check Active Sessions and KB Corrections.
Read config.md — load Provenance Flags, FIXED Sections, email.
Find and read the session file for the .tex being critiqued (use derivation protocol from shared_ops.md).
Recovery check:
- If CL not DONE in session file → "CL not yet generated. Run
/make-clfirst." - If Critique: CURRENT → "Already critiqued (score X/100). Re-run? Waiting for confirmation."
- If Critique: STALE → "Edits made since last critique. Re-critiquing."
- If Critique: PENDING → proceed
Protocol
- Read session file — specifically note:
- Company Context → reviewer persona, "why this company"
- Framing Strategy → intentional reframing decisions (flag only execution inconsistencies, not the strategy itself)
- Cover Letter Plan → CL structure rationale
- Critique Context → reviewer persona, competitive landscape, domain vocabulary
- If session file lacks Company Context or Critique Context: do 1-2 web searches to fill gaps
- Read
resume_builder/reference/critique_framework.md - Read
resume_builder/support/ai_fingerprint_rules.md— use Section 6 checklist in Part 7 verification - Read the .tex file(s) — derive paths from session file Output Files, or from
$ARGUMENTS - Read the JD (path from
$ARGUMENTSor session file) - Read the relevant bundle (
resume_builder/bundles/bundle_[role_type].md— from session file) - Run char count:
python3 resume_builder/helpers/char_count.py -f [resume|cv] [file.tex] - Compile and visually verify:
Use the Read tool to view the compiled PDF — check orphans, page fill, header wrapping. If compile fails: note "COMPILE FAILED — visual checks could not be verified" in Part 8.pdflatex -interaction=nonstopmode -output-directory=output/<FolderName> [file.tex] - If a prior critique exists (
output/<FolderName>/critique_<name>.md): read it and note previous score. 8b. Paper Hook Verification: If the CL cites named papers, PIs, programs, or publications, web-search to verify title, journal, year, and PI affiliation. Flag factual errors as Tier 1 fixes. Run the full critique per critique_framework.md. The output MUST contain ALL 8 sections (even if the framework file has partially compacted, produce every section):
- Domain-Specialist Lens — 7 elements: (a) Reviewer persona (b) Company context (c) JD vocabulary extraction (d) Domain vocabulary map (e) Gap ranking (fatal/serious/cosmetic) (f) Methodology transfer test (g) Competitive landscape
- Five-Perspective Read-Through — ATS, Recruiter (10s), HR (30s), HM (2min), Technical (10min) — each with verdict
- Eight-Dimension Scoring — weighted table summing to 100 (ATS 15%, Summary 10%, Skills 10%, Bullets 25%, Publications 10%, Narrative 15%, Visual 5%, Credibility 10%)
- Interview Likelihood — per-reader probability + ceiling analysis
- Tiered Improvements — Tier 1 (>=1pt each), Tier 2 (0.3-0.9), Tier 3 (<0.3)
- Interview Bridge Points — 5-7 resume-to-interview talking points
- Cover Letter Critique — 6 sub-checks (6A anti-patterns, 6B tailoring, 6C context-specific, 6D ATS, 6E structural, 6F package cohesion)
- If no CL provided: Skip 6A-6E. Run 6F as resume standalone assessment — evaluate whether the resume earns an interview without a CL. Note: "Cover letter not provided — package cohesion not assessed."
- Post-Generation Verification — mechanical + content + structural checklists
- Save to
output/<FolderName>/critique_<name>.md - Update session file — Critique Summary (score, findings, tier 1 fixes), Status → Critique: CURRENT
- Update memory pointer with new score
Progress: "Reading session file for framing context..." / "Running ATS keyword scan — 16/20 match..." / "Scoring 8 dimensions..." / "Score: 87.0/100"
>>>>>> MANDATORY STOP <<<<<<
Present: score table + tier 1 actionable fixes + interview likelihood.
You MUST wait for the user's explicit text response before continuing.
If edits needed, tell user to run /edit-resume.
When user approves / says "looks good" / finalizes:
Verify all expected files exist in output/<FolderName>/:
- session file, resume/CV .tex + .pdf, CL .tex + .pdf, critique .md
- Compile artifacts (.aux, .log, .out)
Confirm to user: "Package complete in output/
<FolderName>/ — [list files]"
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.

