[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AXYBXSFZBART3FT2YKC9TB":3,"skill-same:01M7AXYBXSFZBART3FT2YKC9TB":76},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7AXYBXSFZBART3FT2YKC9TB","update-resume",null,"Review and tailor a resume, executive profile, skills section, or accomplishment bullets for a specific position using only user-provided facts and traceable supporting evidence. Use with a target posting and resume or source materials, including reviews, project summaries, promotion packets, or prior job descriptions. Do not use for interview preparation, open-ended career discovery, or primarily deciding whether an opportunity is desirable.","phively\u002Fsummerfield-ai-zoo-releases","phively","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F16806560?v=4","01M7AXXSFDX01B8YTQRHFRK3VQ","Paul Hively","01M7AXXSG36FTXYBCV2AQR6S1N",0,"MIT","https:\u002F\u002Fgithub.com\u002Fphively\u002Fsummerfield-ai-zoo-releases\u002Fblob\u002Fmain\u002Fplugins\u002Fcareer-coach\u002Fskills\u002Fupdate-resume\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: update-resume\ndescription: Review and tailor a resume, executive profile, skills section, or accomplishment bullets for a specific position using only user-provided facts and traceable supporting evidence. Use with a target posting and resume or source materials, including reviews, project summaries, promotion packets, or prior job descriptions. Do not use for interview preparation, open-ended career discovery, or primarily deciding whether an opportunity is desirable.\n---\n\n# Update Resume\n\nCreate accurate, targeted resume content without rewriting the candidate's history.\n\n## Evidence integrity\n\n- Never invent or silently strengthen employers, titles, dates, responsibilities, authority, accomplishments, outcomes, metrics, scale, technologies, certifications, education, or domain experience.\n- Classify candidate information as explicit fact, supported inference, hypothesis, or unknown.\n- Use only explicit facts as unqualified resume claims. Use a supported inference only when the evidence logically establishes the claim; otherwise require confirmation.\n- Preserve traceability from each material proposed claim to supplied evidence.\n- Report source conflicts and uncertainty rather than resolving them silently.\n- Treat a material value disputed by explicit sources as unresolved unless one source clearly supersedes or validates the other. Do not choose a value merely because one source seems newer, more formal, or more detailed; omit the disputed detail or ask for clarification.\n- Ask only questions whose answers could materially improve accuracy or relevance.\n- Consult `remember-me`, when available, only for narrow stable personal context that is not owned by Career Coach and would materially affect the work. Treat recalled context as evidence requiring the same scrutiny as supplied sources, and continue with neutral defaults if it is unavailable.\n\n## Boundaries\n\n- Do not own interview preparation. If the user wants answers, question-family mapping, rehearsal, or a preparation sheet, route that distinct outcome to `prepare-interview`.\n- Professional-development plans may inform future positioning and identify completed evidence to verify, but they do not establish current qualifications by themselves.\n- Planned or intended certifications, courses, capabilities, or experience are not completed candidate evidence. Require traceable support before presenting them as current claims.\n\n## Use shared context sources\n\nFollow [shared source discovery and authority](..\u002F..\u002Fshared\u002Fhandoff-contracts.md#shared-source-discovery) when stored context could materially affect the requested revisions. A narrow edit with sufficient supplied evidence needs no career-record search. For broader tailoring, retrieve only relevant current positioning, the tracked opportunity and its captured posting, or development context needed to identify completed evidence to verify. Retrieve history only under the shared conditions.\n\nRead [preferences and storage](..\u002F..\u002Fshared\u002Fpreferences-and-storage.md) when discretionary writing, formatting, output choices, artifact destinations, or an authorized settings change matters. Preserve exact source identities; this skill remains read-only for direction, development, and opportunity records. Those records guide emphasis and never establish candidate experience, scope, ownership, outcomes, metrics, or credentials without independently supported underlying evidence.\n\n## Workflow\n\n1. Establish the requested deliverable and preserve the existing resume's voice and factual history unless broader redesign is requested.\n2. Analyze the target posting's mandate, requirements, central responsibilities, competencies, terminology, and ambiguities.\n3. Map important requirements to candidate evidence and current resume coverage.\n4. Mine relevant sources for scope, actions, methods, outcomes, and supported scale.\n5. Prioritize strongly supported evidence that matters to the role.\n6. Draft concise, accurate, ATS-readable revisions.\n7. Verify every new or materially changed claim before presenting it as ready to use.\n\n## References\n\n- Read [evidence-standard.md](references\u002Fevidence-standard.md) whenever multiple sources, conflicts, inferred claims, missing provenance, or substantial new wording are involved.\n- Read [posting-analysis.md](references\u002Fposting-analysis.md) before a full job-to-resume comparison or when the posting is long, ambiguous, or jargon-heavy.\n- Read [resume-writing.md](references\u002Fresume-writing.md) before drafting substantial revised content or changing structure, seniority positioning, or ATS formatting.\n- Read [output-templates.md](references\u002Foutput-templates.md) when choosing a proportional deliverable, building an evidence map, or separating ready-to-use language from confirmation-required language.\n- Read the [shared records and handoff contracts](..\u002F..\u002Fshared\u002Fhandoff-contracts.md) before requesting or consuming a career-direction handoff.\n- Read [career-direction record management](..\u002F..\u002Fshared\u002Fcareer-direction-records.md) before historical retrieval, following a pointer, handling duplicate or inaccessible records, or requesting restoration or another material record change.\n- Read [opportunity record management](..\u002F..\u002Fshared\u002Fopportunity-records.md) before targeted opportunity-history retrieval or requesting an opportunity lifecycle change.\n- Read [persistent-record lifecycle and audits](..\u002F..\u002Fshared\u002Frecord-audits.md) only when a trigger is due or a requested handoff would cause structural maintenance; `update-resume` remains read-only for Career Coach memory records.\n\n## Supporting capabilities\n\n- When available, invoke `research-briefing` only when current external facts about the employer, industry, location, compensation, or labor market are requested or materially needed. If it is unavailable, label affected external claims unverified or unknown. Never use external research as evidence of the candidate's experience.\n- Invoke `documents` when creating or modifying a Word document and follow its render-and-verify workflow.\n- Do not invoke `evaluate-opportunity` unless the user also requests that distinct outcome. Invoke `career-direction` for broader discovery only when requested, or for a bounded in-place update when resume work reveals a user-confirmed, durable criterion, preference, constraint, career hypothesis, or resolved contradiction that belongs in the selected career direction record.\n- Do not update either direction record directly. Send `career-direction` the exact working and historical record identities when visible, source, interpretation, effective date if confirmed, confirmation status, and reason the information is reusable beyond this resume task.\n- Do not create or update opportunity records directly. When resume work reveals a material change to a tracked opportunity, send `evaluate-opportunity` the exact record identities and opportunity identifier when visible, source, evidence classification, proposed state, effective date if known, confirmation status, and lifecycle intent. Resume completion alone does not prove application submission or advancement.\n\n## Output\n\nMatch the response to the request. Distinguish ready-to-use wording, wording requiring confirmation, and unsupported proposals. For a full review, provide role priorities, an evidence map, recommended positioning, proposed revisions, material gaps, confirmation questions, and concise claim-verification notes. For a narrow request, return only the requested section plus necessary caveats.\n","# Update Resume\n\nCreate accurate, targeted resume content without rewriting the candidate's history.\n\n## Evidence integrity\n\n- Never invent or silently strengthen employers, titles, dates, responsibilities, authority, accomplishments, outcomes, metrics, scale, technologies, certifications, education, or domain experience.\n- Classify candidate information as explicit fact, supported inference, hypothesis, or unknown.\n- Use only explicit facts as unqualified resume claims. Use a supported inference only when the evidence logically establishes the claim; otherwise require confirmation.\n- Preserve traceability from each material proposed claim to supplied evidence.\n- Report source conflicts and uncertainty rather than resolving them silently.\n- Treat a material value disputed by explicit sources as unresolved unless one source clearly supersedes or validates the other. Do not choose a value merely because one source seems newer, more formal, or more detailed; omit the disputed detail or ask for clarification.\n- Ask only questions whose answers could materially improve accuracy or relevance.\n- Consult `remember-me`, when available, only for narrow stable personal context that is not owned by Career Coach and would materially affect the work. Treat recalled context as evidence requiring the same scrutiny as supplied sources, and continue with neutral defaults if it is unavailable.\n\n## Boundaries\n\n- Do not own interview preparation. If the user wants answers, question-family mapping, rehearsal, or a preparation sheet, route that distinct outcome to `prepare-interview`.\n- Professional-development plans may inform future positioning and identify completed evidence to verify, but they do not establish current qualifications by themselves.\n- Planned or intended certifications, courses, capabilities, or experience are not completed candidate evidence. Require traceable support before presenting them as current claims.\n\n## Use shared context sources\n\nFollow [shared source discovery and authority](..\u002F..\u002Fshared\u002Fhandoff-contracts.md#shared-source-discovery) when stored context could materially affect the requested revisions. A narrow edit with sufficient supplied evidence needs no career-record search. For broader tailoring, retrieve only relevant current positioning, the tracked opportunity and its captured posting, or development context needed to identify completed evidence to verify. Retrieve history only under the shared conditions.\n\nRead [preferences and storage](..\u002F..\u002Fshared\u002Fpreferences-and-storage.md) when discretionary writing, formatting, output choices, artifact destinations, or an authorized settings change matters. Preserve exact source identities; this skill remains read-only for direction, development, and opportunity records. Those records guide emphasis and never establish candidate experience, scope, ownership, outcomes, metrics, or credentials without independently supported underlying evidence.\n\n## Workflow\n\n1. Establish the requested deliverable and preserve the existing resume's voice and factual history unless broader redesign is requested.\n2. Analyze the target posting's mandate, requirements, central responsibilities, competencies, terminology, and ambiguities.\n3. Map important requirements to candidate evidence and current resume coverage.\n4. Mine relevant sources for scope, actions, methods, outcomes, and supported scale.\n5. Prioritize strongly supported evidence that matters to the role.\n6. Draft concise, accurate, ATS-readable revisions.\n7. Verify every new or materially changed claim before presenting it as ready to use.\n\n## References\n\n- Read [evidence-standard.md](references\u002Fevidence-standard.md) whenever multiple sources, conflicts, inferred claims, missing provenance, or substantial new wording are involved.\n- Read [posting-analysis.md](references\u002Fposting-analysis.md) before a full job-to-resume comparison or when the posting is long, ambiguous, or jargon-heavy.\n- Read [resume-writing.md](references\u002Fresume-writing.md) before drafting substantial revised content or changing structure, seniority positioning, or ATS formatting.\n- Read [output-templates.md](references\u002Foutput-templates.md) when choosing a proportional deliverable, building an evidence map, or separating ready-to-use language from confirmation-required language.\n- Read the [shared records and handoff contracts](..\u002F..\u002Fshared\u002Fhandoff-contracts.md) before requesting or consuming a career-direction handoff.\n- Read [career-direction record management](..\u002F..\u002Fshared\u002Fcareer-direction-records.md) before historical retrieval, following a pointer, handling duplicate or inaccessible records, or requesting restoration or another material record change.\n- Read [opportunity record management](..\u002F..\u002Fshared\u002Fopportunity-records.md) before targeted opportunity-history retrieval or requesting an opportunity lifecycle change.\n- Read [persistent-record lifecycle and audits](..\u002F..\u002Fshared\u002Frecord-audits.md) only when a trigger is due or a requested handoff would cause structural maintenance; `update-resume` remains read-only for Career Coach memory records.\n\n## Supporting capabilities\n\n- When available, invoke `research-briefing` only when current external facts about the employer, industry, location, compensation, or labor market are requested or materially needed. If it is unavailable, label affected external claims unverified or unknown. Never use external research as evidence of the candidate's experience.\n- Invoke `documents` when creating or modifying a Word document and follow its render-and-verify workflow.\n- Do not invoke `evaluate-opportunity` unless the user also requests that distinct outcome. Invoke `career-direction` for broader discovery only when requested, or for a bounded in-place update when resume work reveals a user-confirmed, durable criterion, preference, constraint, career hypothesis, or resolved contradiction that belongs in the selected career direction record.\n- Do not update either direction record directly. Send `career-direction` the exact working and historical record identities when visible, source, interpretation, effective date if confirmed, confirmation status, and reason the information is reusable beyond this resume task.\n- Do not create or update opportunity records directly. When resume work reveals a material change to a tracked opportunity, send `evaluate-opportunity` the exact record identities and opportunity identifier when visible, source, evidence classification, proposed state, effective date if known, confirmation status, and lifecycle intent. Resume completion alone does not prove application submission or advancement.\n\n## Output\n\nMatch the response to the request. Distinguish ready-to-use wording, wording requiring confirmation, and unsupported proposals. For a full review, provide role priorities, an evidence map, recommended positioning, proposed revisions, material gaps, confirmation questions, and concise claim-verification notes. For a narrow request, return only the requested section plus necessary caveats.\n",{"name":5,"description":7},"main","19805a1bfd4784f5a4faf7043f2016f3a466a307","plugins\u002Fcareer-coach\u002Fskills\u002Fupdate-resume","https:\u002F\u002Fgithub.com\u002Fphively\u002Fsummerfield-ai-zoo-releases","https:\u002F\u002Fgithub.com\u002Fphively","2026-11-14 06:07:47",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add phively\u002Fsummerfield-ai-zoo-releases --skill update-resume",{"tool":36,"command":37},"bunx","bunx skills add phively\u002Fsummerfield-ai-zoo-releases --skill update-resume",{"tool":39,"command":40},"pnpm","pnpm dlx skills add phively\u002Fsummerfield-ai-zoo-releases --skill update-resume","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fphively\u002Fsummerfield-ai-zoo-releases\u002Fblob\u002Fmain\u002Fplugins\u002Fcareer-coach\u002Fskills\u002Fupdate-resume\u002FSKILL.md",true,[44,50,56,60,64,68,72],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"agents\u002Fopenai.yaml","REFERENCE","参考文档",285,"https:\u002F\u002Fgithub.com\u002Fphively\u002Fsummerfield-ai-zoo-releases\u002Fblob\u002Fmain\u002Fplugins\u002Fcareer-coach\u002Fskills\u002Fupdate-resume\u002Fagents\u002Fopenai.yaml",{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"assets\u002Ficon-large.svg","ASSET","资产文件",524,"https:\u002F\u002Fgithub.com\u002Fphively\u002Fsummerfield-ai-zoo-releases\u002Fblob\u002Fmain\u002Fplugins\u002Fcareer-coach\u002Fskills\u002Fupdate-resume\u002Fassets\u002Ficon-large.svg",{"path":57,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":58,"sourceHtmlUrl":59},"assets\u002Ficon-small.svg",395,"https:\u002F\u002Fgithub.com\u002Fphively\u002Fsummerfield-ai-zoo-releases\u002Fblob\u002Fmain\u002Fplugins\u002Fcareer-coach\u002Fskills\u002Fupdate-resume\u002Fassets\u002Ficon-small.svg",{"path":61,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fevidence-standard.md",3016,"https:\u002F\u002Fgithub.com\u002Fphively\u002Fsummerfield-ai-zoo-releases\u002Fblob\u002Fmain\u002Fplugins\u002Fcareer-coach\u002Fskills\u002Fupdate-resume\u002Freferences\u002Fevidence-standard.md",{"path":65,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Foutput-templates.md",1865,"https:\u002F\u002Fgithub.com\u002Fphively\u002Fsummerfield-ai-zoo-releases\u002Fblob\u002Fmain\u002Fplugins\u002Fcareer-coach\u002Fskills\u002Fupdate-resume\u002Freferences\u002Foutput-templates.md",{"path":69,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fposting-analysis.md",1951,"https:\u002F\u002Fgithub.com\u002Fphively\u002Fsummerfield-ai-zoo-releases\u002Fblob\u002Fmain\u002Fplugins\u002Fcareer-coach\u002Fskills\u002Fupdate-resume\u002Freferences\u002Fposting-analysis.md",{"path":73,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fresume-writing.md",2427,"https:\u002F\u002Fgithub.com\u002Fphively\u002Fsummerfield-ai-zoo-releases\u002Fblob\u002Fmain\u002Fplugins\u002Fcareer-coach\u002Fskills\u002Fupdate-resume\u002Freferences\u002Fresume-writing.md",[77,84,91,98,105,112],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7BG4EDF051TPVNP0153PZG8","personal-shopper","Compare products, services, contractors, and project costs against the user's needs, scope, qualifications, fit, and current regional evidence; research official permit fees and supported reference-class forecasts; build package-aware groceries from finalized delegated meal plans. Use for direct product shopping, named-option alternatives, hardware specifications, service quotes, project estimates, shopping preferences, or delegated grocery work; do not choose or redesign recipes.","https:\u002F\u002Fgithub.com\u002Fphively\u002Fsummerfield-ai-zoo-releases\u002Fblob\u002Fmain\u002Fplugins\u002Fpersonal-shopper\u002Fskills\u002Fpersonal-shopper\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7BG45WKA01S9KZ13E4CK3N8","superb-skills","Design and evaluate reusable instructions, skills, plugins, contracts, and tests; advise on benchmark design and results. Use for instruction reliability or benchmark critique, explanation, and design. Skip one-off rewrites and ordinary use of fixed instructions.","https:\u002F\u002Fgithub.com\u002Fphively\u002Fsummerfield-ai-zoo-releases\u002Fblob\u002Fmain\u002Fplugins\u002Fdev-tools\u002Fskills\u002Fsuperb-skills\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7BG42RC65MMVV3GQP1P8Y34","coding-preferences","Apply relevant portable coding preferences to implementation, code review, explanation, and engineering prose. Use when reusable coding conventions could affect the result; do not use to manage general personal or writing preferences.","https:\u002F\u002Fgithub.com\u002Fphively\u002Fsummerfield-ai-zoo-releases\u002Fblob\u002Fmain\u002Fplugins\u002Fdev-tools\u002Fskills\u002Fcoding-preferences\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M7BG4049QZ4DZPXS8B0MS6QD","code-quality-review","Review code for correctness and material maintenance risks when requested or accepted; ordinary implementation and coding-preference work do not acquire a reviewer prerequisite.","https:\u002F\u002Fgithub.com\u002Fphively\u002Fsummerfield-ai-zoo-releases\u002Fblob\u002Fmain\u002Fplugins\u002Fdev-tools\u002Fskills\u002Fcode-quality-review\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":19},"01M7BG3YPJF6BG3XTEZRSCT7KR","fixture-simple-normalizer","Fixture target for one deterministic filename normalization.","https:\u002F\u002Fgithub.com\u002Fphively\u002Fsummerfield-ai-zoo-releases\u002Fblob\u002Fmain\u002Fplugins\u002Fdev-tools\u002Fevals\u002Ffixtures\u002Fsuperb-skills\u002Ftargets\u002Fsimple-normalizer\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":19},"01M7BG3WK5MXDR5D6H9SJ8KZAP","fixture-preference-planner","Fixture target for testing preference intake, editable project settings, task overrides, and verified operational lessons.","https:\u002F\u002Fgithub.com\u002Fphively\u002Fsummerfield-ai-zoo-releases\u002Fblob\u002Fmain\u002Fplugins\u002Fdev-tools\u002Fevals\u002Ffixtures\u002Fsuperb-skills\u002Ftargets\u002Fpreference-dependent\u002FSKILL.md",[],[]]