- name
SKILL.md
El archivo de la skill permanece en el repositorio del publicador.
Pega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add reactive-resume/reactive-resume --skill resume-content-guide -a cursor -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add reactive-resume/reactive-resume --skill resume-content-guide -a claude-code -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add reactive-resume/reactive-resume --skill resume-content-guide -a codex -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add reactive-resume/reactive-resume --skill resume-content-guide -a grok -yEnvía el mensaje copiado en un chat de Grok Bot. El Bot obtiene este SKILL.md de GitHub y lo añade a las skills que comparten todos tus Bots.
Install this skill: https://github.com/reactive-resume/reactive-resume/tree/HEAD/plugins/reactive-resume/skills/resume-content-guideDel publicador
Decide what goes on this person's resume, what stays off and in what order, for their target country, industry, career stage and situation. Then audit the resume they have and change it only with their approval.
This skill handles selection, placement and personal-data norms. Neighbouring jobs belong to sibling skills, which may not be installed; when one is missing, do the light version yourself and say so:
official (law, regulator, government careers service), study (field experiment or peer-reviewed research), survey (employer survey, vendor documentation, commercial study) or convention (practitioner consensus, a default the user can override). One tag per recommendation. Recipe and playbook lines without a tag are convention. The first time tags appear in a reply, add one legend line: "official = law or government guidance; study = field research; survey = employer or vendor survey; convention = common practice you can override."Decline at most once, in one sentence, without a lecture. Then help with the honest version.
Before checking rules, decide with the user the 2–3 selling points this resume must land for the target (ideally from patterns across several target postings), then check whether the top third of page one delivers them. Keep an item only when all four hold:
Keep job titles, employers, dates and education easy to find, because first-pass readers look there first (survey: a small vendor eye-tracking study, weak but consistent with recruiter accounts). The same reason makes a dated, reverse-chronological history beat a functional, skills-only layout.
If a resume is available (MCP or pasted), read it before asking anything.
Note the sections and their order, every date range, the page count and every personal-data field. Page count: with MCP, the number of entries in metadata.layout.pages (content can still overflow; confirm with the user or download_resume_pdf); without MCP, ask.
Fill in what the resume and Career data show: years of experience, gaps, current location, personal-data fields, likely target. Then ask at most two questions in one message, each with a default the user can accept by saying yes:
I'll assume you're applying in the US for entry-level backend roles; correct me if not. Also: what have you been doing since April?
Work in this order so must-fix items surface first.
hidden: true don't print, and neither do metadata.notes. They are not hidden text and need no action; skip hidden items in every check. Hidden text means text that prints but can't be seen: compare metadata.design.colors.text with background, and scan metadata.styleRules, metadata.stylesheet and description HTML for colour, size or display tricks.study). A new grad's first search is different: see the situation table.official).Lead with context, then two short lines, then one table, then the questions you need answered. Rules:
Summarise exactly what you will change ("Hide the photo and references, move Education above Experience, hide the skill-level dots; waiting on your project details") and wait for a yes.
GPA rule (convention). Include it when the application asks, for US federal jobs, for early-career finance, consulting and law, and otherwise at 3.0/4.0 or above for the first ~3 years; put it on the degree line at 3.5+. Drop it after that, except for federal and academic applications. Never round up; give the scale. No study supports a universal cut-off (fewer than 40% of US employers screen new grads by GPA, survey, NACE 2025).
Defaults when the ad is silent. More countries, legal notes and conversion recipes are in references/countries.md.
If the user names no country, ask once. If they still don't say, use US/UK-style minimal personal data and say so.
Before auditing anyone in one of these situations, read the matching playbook in references/situations.md; each has before → after examples and the questions to ask.
convention).When the user quotes another statistic, check references/evidence.md before repeating or rebutting it.
Skip this section when the Reactive Resume MCP server isn't connected.
api_career_profile gives target roles, locations and notice period; api_career_facts {applicationId: null} may already describe a gap, a move or a certification. Use them to pre-fill Step 3 and say so ("From your Career profile: backend roles in Columbus or remote"). Ask only for what's missing. Never copy a fact onto the resume without the user's approval.list_resumes; ask which one if there are several.read_resume {id}. Keep updatedAt from the structured content; it becomes expectedUpdatedAt.api_rest_check_resume {id} returns deterministic contact, date, layout, heading and font findings. Judge each against the target country before reporting it: PICTURE_PRESENT is a finding only where the country table says no photo, and a missing street address is correct in most markets. Findings in ignored were dismissed by the user; raise them again only if they are must-fix. Use Check for layout and parsing; keep content judgements your own.list_applications to find its ID, then read_application {id} for jobDescription to judge relevance. Leave keyword matching and tailoring to resume-tailor.duplicate_resume {id, name} (for example "Jane Doe — US"), then read_resume on the copy for its updatedAt. For small fixes, ask whether to patch a copy or the original. Then call apply_resume_patch {id, operations, expectedUpdatedAt}.
test operation before every index-based change, so the patch fails instead of touching the wrong item if the order has changed."hidden": true to remove.dates objects, never period text, and HTML descriptions (<ul><li><p>…</p></li></ul>), never Markdown.RESUME_VERSION_CONFLICT, read again and recompute. On 403 RESUME_LOCKED, ask before calling unlock_resume.read_resume and on the result, then summarise what changed.Common operations (the indices come from the data you just read):
[
{ "op": "replace", "path": "/picture/hidden", "value": true },
{ "op": "replace", "path": "/sections/references/hidden", "value": true },
{ "op": "replace", "path": "/metadata/design/level/type", "value": "hidden" },
{ "op": "test", "path": "/sections/experience/items/5/company", "value": "Acme Corp" },
{ "op": "replace", "path": "/sections/experience/items/5/hidden", "value": true }
]
The level/type switch hides every skill and language level indicator at once. Read references/patches.md before hiding only some levels, merging a duplicate employer into roles, reordering sections, switching to a single column (sidebar sections must move first or they vanish), converting for another country (page format, locale, date format, personal-data fields), adding a career-break entry or adding a declaration section.
Input. "Audit my resume." read_resume returns (abridged): header "Priya Raman · 42 Oak St Apt 3, Columbus OH 43210 · DOB 11 Feb 2003", photo shown; summary "Hard-working team player seeking a challenging role"; Skills "Python ●●●●○, Java ●●●○○, Teamwork, Communication"; Experience "Software Engineering Intern, Acme Corp, 05/2025–08/2025"; Education below it, "B.S. Computer Science, Ohio State University, 2022–04/2026, GPA 3.4"; no projects; Interests "Reading, travel"; References "Available upon request"; one layout page. Check reports PICTURE_PRESENT only. The agent asked: "I'll assume you're applying in the US for entry-level backend roles; correct me if not. Also: what have you been doing since April?" The user: "Yes. Just applying."
Output.
Context: US, entry-level backend roles (confirmed). Must-fix: none. First impression: Ohio State CS grad with one internship; the summary doesn't say backend. Keep: the Acme internship, clear month/year dates, one-page length.
Evidence: official = law or government guidance; study = field research; survey = employer or vendor survey; convention = common practice you can override.
Since April: a job search right after graduating needs no entry or label, and it's normal. If you start a project now, it goes under Projects with its start date once it exists.
- Which 2–3 projects show backend work best, and is there a link for each?
- Summary: hide it, or replace it with one line naming your target in your words?
After the yes: duplicate_resume, read_resume on the copy, then one apply_resume_patch that hides the picture, the summary (a replacement waits for the user's target line) and the references and interests sections; sets /metadata/design/level/type to hidden; hides the Teamwork and Communication items; removes the date-of-birth custom field (custom fields have no hidden flag, so it is removed on the copy only); rewrites basics.location to "Columbus, OH"; and moves education ahead of experience in the page layout. Skill grouping waits for the user to approve the proposed groups. Every index-based operation is guarded by a test. Nothing is added until the user supplies the facts. Then read_resume and api_rest_check_resume to verify.
Input. "Should I put my photo and date of birth on my CV for a job in Dubai?"
Output.
Both are optional in the UAE, and practice is split.
- Photo: common with local employers and regional job boards; many multinationals' application systems don't expect one, and photos invite bias in field studies (Germany, Israel). Include it for local firms if you're comfortable; leave it off for multinationals. (
convention; the bias evidence isstudy.)- Date of birth: common, but it invites age screening. Include it only if you want to (
convention).- Worth adding, your call: nationality and visa status ("UAE resident, employment visa" or "Overseas, available on 30 days' notice"), notice period, and a driving licence if you hold one.
Evidence: study = field research; convention = common practice you can override.
Which matters more for you: local companies or multinationals?
Decides what information belongs on a resume or CV, what to leave off and in what order, and audits an existing resume against those norms. Covers every section (contact details, photo, summary, exper
---name: resume-content-guidedescription: Decides what information belongs on a resume or CV, what to leave off and in what order, and audits an…---# plugins/reactive-resume/skills/resume-content-guide/SKILL.mdResumen general
Decides what information belongs on a resume or CV, what to leave off and in what order, and audits an existing resume against those norms. Covers every section (contact details, photo, summary, experience, education and GPA, skills, languages, references), candidate situations (new grad, career change, gaps, layoffs, veterans, academic, visa and more) and country and industry norms. Use when the user asks "what should I put on my resume", "what should I leave off", "should I include my photo / GPA / date of birth", "how do I show a gap", "summary or objective?", "how long should my CV be", "CV for a job in Dubai / Germany", "I'm moving to another country, what should I change", "what to put on my resume as a veteran" or "audit / review my resume". Works with pasted text or the Reactive Resume MCP server. For rewriting bullets use resume-bullet-writer; for fitting a resume to one job posting use resume-tailor; for building a new resume as JSON use resume-builder.
Preguntas frecuentes
Descarga plugins/reactive-resume/skills/resume-content-guide/SKILL.md desde el publicador, o copia la ruta y abre el repositorio. PlugMCP lista la skill y no aloja el archivo.
El publicador lo mantiene en https://github.com/reactive-resume/reactive-resume.
Claude, Cursor, Codex y Grok Build pueden leer un SKILL.md que añadas desde el repositorio del publicador. Grok Bot lo instala cuando envías en un chat el enlace a la carpeta de la skill en GitHub.
| "Under review" or "in preparation" is never listed as published |
| Volunteer | When it shows relevant skills or leadership, or fills a gap | Unrelated items on a crowded page | Religious or political organisations are an identity disclosure; ask |
| Awards | External, selective, recent ("Top 5% of 2,000 reps") | School-era awards after ~5 years, unless major | — |
| Languages | Level in plain words, plus CEFR (A1–C2) where European or international readers are likely; certificates | Overstated levels; interviewers test them | Show the level as text and hide the dots |
| Interests | Only when job-relevant or a strong conversation hook | Generic lists ("reading, travel") | Hobbies can signal class and trigger bias (study) |
| References | Australia, NZ, South African government posts: often 2 referees, with permission. UK: optional "available on request" line | US and Canada: the section and the "available on request" line | Never publish a referee's details without their consent |
api_rest_check_resumeSay yes and I'll make these changes on a copy named "Priya Raman — US entry level"; projects wait for your answers.