[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DWP0PERRC9FZJ1GG944TAD":3,"skill-same:01M6DWP0PERRC9FZJ1GG944TAD":85},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":61,"commitSha":62,"skillDirectory":63,"forksCount":64,"repositoryHtmlUrl":65,"repositoryHomepageUrl":66,"ownerHtmlUrl":67,"ownerBlogUrl":68,"ownerDescription":69,"updatedAt":70,"install":71,"resources":84},"01M6DWP0PERRC9FZJ1GG944TAD","resume-conventions",null,"Resume and CV conventions by country: length, photo, GDPR consent, work-authorization lines, date formats. Use when adapting an application to a market.","Muvon\u002Foctomind-tap","Muvon","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F25336907?v=4","01M6DWA4KTRX4J73CW5CECKAD0","01M6DWA4QSWFGYE6WDMAMFF1WE",6,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FMuvon\u002Foctomind-tap\u002Fblob\u002Fmaster\u002Fskills\u002Fresume-conventions\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"resume","conventions","resume conventions","australia","ca","for","no external","my","formats","markets","when","use","cv","coach","do","Tools","data","de","work","localize","external tools","2026-11-10 10:12:30",false,"---\nname: resume-conventions\ntitle: \"Global Resume & CV Conventions\"\ndescription: \"Resume and CV conventions by country: length, photo, GDPR consent, work-authorization lines, date formats. Use when adapting an application to a market.\"\nlicense: Apache-2.0\ncompatibility: \"No external tools required. Markets covered: US\u002FCA, UK\u002FIE, continental Europe, AU\u002FNZ, plus photo\u002Fdata norms for DE, FR, and Asia.\"\ndomains: coach\nrules:\n  - career(resume)\n  - career(cv)\n  - career(localize-resume)\n  - match(\\b(resume|cv)\\s+(format|convention|for)\\s+.{0,20}(germany|france|uk|us|europe|canada|australia|asia)\\b)\n  - match(\\b(cv|resume)\\s+photo\\b)\n  - match(\\bGDPR\\s+.{0,15}(cv|resume|application)\\b)\n  - semantic(what resume format should I use for a job in another country)\n  - semantic(should my CV have a photo for this country)\n  - semantic(do I need a GDPR clause on my CV)\n---\n\n## Overview\n\nA job-application document that is perfect for one country can be wrong — or legally risky — in another. The word for it, the expected length, whether it carries a photo, and what personal data belongs on it all change by market. This skill encodes the 2026 conventions so an application is adapted to where it is actually being sent.\n\nDetect the target market first (from the posting's location\u002Fcompany, or ask), then apply that market's conventions. When the target is genuinely ambiguous, ask rather than guess — the wrong convention (a photo in a no-photo market, a missing consent clause in Poland, a US date order in Europe) is a real failure.\n\n## Instructions\n\n### Terminology and length\n\n| Market | Document name | Typical length |\n|---|---|---|\n| US \u002F Canada | Resume (CV = academic only) | 1–2 pages |\n| UK \u002F Ireland | CV | ~2 pages |\n| Continental Europe | CV (DE: Lebenslauf) | 1–2 pages; up to 3 for senior roles |\n| Australia \u002F NZ | Resume or CV | 2–4 pages |\n| Academic \u002F research (any country) | CV | as long as the record needs (6+ pages fine) |\n\n\"Resume\" is primarily a US\u002FCanada term; most of the world says \"CV\" for the same short professional document. Use the name the target market uses.\n\n### Photo\n\n- US, UK, Canada, Australia, Ireland: no photo. Anti-discrimination norms mean a photo can create legal risk for the employer and get the application screened out. Never include one.\n- Germany: traditionally a professional passport-style photo was expected, but since the 2006 AGG anti-discrimination law it has become increasingly optional — many current German applications omit it, and no employer may require one. So treat it as the candidate's choice: a professional photo is safe and still common, and omitting it is now fully acceptable. Note the choice; don't force either way.\n- France, Spain, much of continental Europe, and much of Asia: photo still commonly expected, though the same optional-shift is spreading.\n- When unsure, default to no photo for US\u002FUK\u002FCA\u002FAU\u002FIE (there it is a hard rule), and for photo-culture markets present it as an accepted-but-optional choice rather than a mandate; ask when it materially matters.\n\n### Personal data and consent clauses\n\n- A consent clause is not a GDPR requirement for an ordinary application: employers process applicant data on the pre-contract legal basis (GDPR Art. 6(1)(b); in Germany alongside § 26 BDSG) and must give applicants their own privacy notice.\n- Poland is the exception by custom: recruiters expect a RODO consent line at the foot of the CV, and many postings quote the exact wording to use. Add one there, and anywhere a posting asks for it. A separate opt-in sentence covers keeping the CV for future recruitment.\n- Personal data norms differ: date of birth, marital status, and nationality still appear on some German, French, and Central European CVs but are optional, and omitted (and can be discriminatory to request) in the US\u002FUK\u002FCA\u002FAU. Include only what the target market expects and the candidate consents to.\n- Work authorization: state it in one line when it is a likely knockout question (UK \"right to work\", US \"authorized to work in the US\", EU Blue Card or permit status).\n- Never add sensitive personal data the candidate did not provide.\n\n### Locale formatting\n\n- Dates: US `MM\u002FDD\u002FYYYY` or `Month YYYY`; most of the rest of the world `DD\u002FMM\u002FYYYY` or `Month YYYY`. Use the target market's order; be consistent throughout.\n- Spelling: match the market's English variant (US vs UK spelling) when the application language is English.\n- Contact: phone in the target country's international format; a city\u002Fcountry line rather than a full street address is now standard and privacy-safe.\n- Language: if the posting is in a non-English language, the application should be in that language unless the posting says otherwise — hand the localization to the localize workflow \u002F content-locale-humanize for native fluency.\n\n## Examples\n\nSame candidate, US software role: 1-page resume, no photo, no DOB, `Month YYYY` dates, US spelling, city\u002Fstate line, no GDPR clause.\n\nSame candidate, German software role: 2-page Lebenslauf\u002FCV, employment dates as `MM\u002FYYYY` (`03\u002F2021 – heute`), structured and thorough, no consent clause needed — a professional photo optional (traditional but no longer expected post-AGG). Same facts, adapted to the market.\n\nSame candidate, Polish role: 1–2 page CV in the posting's language, the RODO consent line from the posting at the foot, photo optional.\n\n## Checklist\n\n- [ ] Correct document name and length in range for the detected market.\n- [ ] Photo present or absent per the market rule, and only if the candidate chose it.\n- [ ] Consent clause present for Poland or when the posting asks; absent otherwise.\n- [ ] Dates and spelling in the local convention, consistent throughout.\n- [ ] Work authorization stated where it is a likely knockout.\n- [ ] No personal data the market discourages or the candidate did not provide.\n\n## References\n\n- GDPR Art. 6(1)(b) (pre-contract processing); Germany: Allgemeines Gleichbehandlungsgesetz (AGG, 2006) and § 26 BDSG\n- [Careers in Poland: the consent clause on a Polish CV](https:\u002F\u002Fwww.careersinpoland.com\u002Farticle\u002Fwork\u002Fthe-one-thing-you-should-never-leave-off-your-polish-cv)\n- [Europass CV](https:\u002F\u002Feuropass.europa.eu\u002Fen\u002Fcreate-europass-cv)\n","## Overview\n\nA job-application document that is perfect for one country can be wrong — or legally risky — in another. The word for it, the expected length, whether it carries a photo, and what personal data belongs on it all change by market. This skill encodes the 2026 conventions so an application is adapted to where it is actually being sent.\n\nDetect the target market first (from the posting's location\u002Fcompany, or ask), then apply that market's conventions. When the target is genuinely ambiguous, ask rather than guess — the wrong convention (a photo in a no-photo market, a missing consent clause in Poland, a US date order in Europe) is a real failure.\n\n## Instructions\n\n### Terminology and length\n\n| Market | Document name | Typical length |\n|---|---|---|\n| US \u002F Canada | Resume (CV = academic only) | 1–2 pages |\n| UK \u002F Ireland | CV | ~2 pages |\n| Continental Europe | CV (DE: Lebenslauf) | 1–2 pages; up to 3 for senior roles |\n| Australia \u002F NZ | Resume or CV | 2–4 pages |\n| Academic \u002F research (any country) | CV | as long as the record needs (6+ pages fine) |\n\n\"Resume\" is primarily a US\u002FCanada term; most of the world says \"CV\" for the same short professional document. Use the name the target market uses.\n\n### Photo\n\n- US, UK, Canada, Australia, Ireland: no photo. Anti-discrimination norms mean a photo can create legal risk for the employer and get the application screened out. Never include one.\n- Germany: traditionally a professional passport-style photo was expected, but since the 2006 AGG anti-discrimination law it has become increasingly optional — many current German applications omit it, and no employer may require one. So treat it as the candidate's choice: a professional photo is safe and still common, and omitting it is now fully acceptable. Note the choice; don't force either way.\n- France, Spain, much of continental Europe, and much of Asia: photo still commonly expected, though the same optional-shift is spreading.\n- When unsure, default to no photo for US\u002FUK\u002FCA\u002FAU\u002FIE (there it is a hard rule), and for photo-culture markets present it as an accepted-but-optional choice rather than a mandate; ask when it materially matters.\n\n### Personal data and consent clauses\n\n- A consent clause is not a GDPR requirement for an ordinary application: employers process applicant data on the pre-contract legal basis (GDPR Art. 6(1)(b); in Germany alongside § 26 BDSG) and must give applicants their own privacy notice.\n- Poland is the exception by custom: recruiters expect a RODO consent line at the foot of the CV, and many postings quote the exact wording to use. Add one there, and anywhere a posting asks for it. A separate opt-in sentence covers keeping the CV for future recruitment.\n- Personal data norms differ: date of birth, marital status, and nationality still appear on some German, French, and Central European CVs but are optional, and omitted (and can be discriminatory to request) in the US\u002FUK\u002FCA\u002FAU. Include only what the target market expects and the candidate consents to.\n- Work authorization: state it in one line when it is a likely knockout question (UK \"right to work\", US \"authorized to work in the US\", EU Blue Card or permit status).\n- Never add sensitive personal data the candidate did not provide.\n\n### Locale formatting\n\n- Dates: US `MM\u002FDD\u002FYYYY` or `Month YYYY`; most of the rest of the world `DD\u002FMM\u002FYYYY` or `Month YYYY`. Use the target market's order; be consistent throughout.\n- Spelling: match the market's English variant (US vs UK spelling) when the application language is English.\n- Contact: phone in the target country's international format; a city\u002Fcountry line rather than a full street address is now standard and privacy-safe.\n- Language: if the posting is in a non-English language, the application should be in that language unless the posting says otherwise — hand the localization to the localize workflow \u002F content-locale-humanize for native fluency.\n\n## Examples\n\nSame candidate, US software role: 1-page resume, no photo, no DOB, `Month YYYY` dates, US spelling, city\u002Fstate line, no GDPR clause.\n\nSame candidate, German software role: 2-page Lebenslauf\u002FCV, employment dates as `MM\u002FYYYY` (`03\u002F2021 – heute`), structured and thorough, no consent clause needed — a professional photo optional (traditional but no longer expected post-AGG). Same facts, adapted to the market.\n\nSame candidate, Polish role: 1–2 page CV in the posting's language, the RODO consent line from the posting at the foot, photo optional.\n\n## Checklist\n\n- [ ] Correct document name and length in range for the detected market.\n- [ ] Photo present or absent per the market rule, and only if the candidate chose it.\n- [ ] Consent clause present for Poland or when the posting asks; absent otherwise.\n- [ ] Dates and spelling in the local convention, consistent throughout.\n- [ ] Work authorization stated where it is a likely knockout.\n- [ ] No personal data the market discourages or the candidate did not provide.\n\n## References\n\n- GDPR Art. 6(1)(b) (pre-contract processing); Germany: Allgemeines Gleichbehandlungsgesetz (AGG, 2006) and § 26 BDSG\n- [Careers in Poland: the consent clause on a Polish CV](https:\u002F\u002Fwww.careersinpoland.com\u002Farticle\u002Fwork\u002Fthe-one-thing-you-should-never-leave-off-your-polish-cv)\n- [Europass CV](https:\u002F\u002Feuropass.europa.eu\u002Fen\u002Fcreate-europass-cv)\n",{"name":5,"rules":49,"title":59,"domains":36,"license":14,"description":7,"compatibility":60},[50,51,52,53,54,55,56,57,58],"career(resume)","career(cv)","career(localize-resume)","match(\\b(resume|cv)\\s+(format|convention|for)\\s+.{0,20}(germany|france|uk|us|europe|canada|australia|asia)\\b)","match(\\b(cv|resume)\\s+photo\\b)","match(\\bGDPR\\s+.{0,15}(cv|resume|application)\\b)","semantic(what resume format should I use for a job in another country)","semantic(should my CV have a photo for this country)","semantic(do I need a GDPR clause on my CV)","Global Resume & CV Conventions","No external tools required. Markets covered: US\u002FCA, UK\u002FIE, continental Europe, AU\u002FNZ, plus photo\u002Fdata norms for DE, FR, and Asia.","master","e9e4a19559669b1627b1ac5ed3f77b8e36cfad95","skills\u002Fresume-conventions",0,"https:\u002F\u002Fgithub.com\u002FMuvon\u002Foctomind-tap","https:\u002F\u002Foctomind.run\u002Ftap\u002F","https:\u002F\u002Fgithub.com\u002FMuvon","https:\u002F\u002Fmuvon.io","We bring ideas to life","2026-11-14 13:21:16",{"source":8,"skillName":5,"commands":72,"prompt":82,"zipAvailable":83},[73,76,79],{"tool":74,"command":75},"npx","npx skills add Muvon\u002Foctomind-tap --skill resume-conventions",{"tool":77,"command":78},"bunx","bunx skills add Muvon\u002Foctomind-tap --skill resume-conventions",{"tool":80,"command":81},"pnpm","pnpm dlx skills add Muvon\u002Foctomind-tap --skill resume-conventions","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMuvon\u002Foctomind-tap\u002Fblob\u002Fmaster\u002Fskills\u002Fresume-conventions\u002FSKILL.md",true,[],[86,124,151,170,194,220],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":103,"publishedAt":44},"01M70SFC5CTHRKA9B97N1ARVZ2","seo-content-refresh","Finds decaying pages, picks update, merge, redirect or remove, and briefs each refresh. Use to prioritize existing content and judge whether it helped.","https:\u002F\u002Fgithub.com\u002FMuvon\u002Foctomind-tap\u002Fblob\u002Fmaster\u002Fskills\u002Fseo-content-refresh\u002FSKILL.md",[92,97,100],{"categoryNo":93,"categoryName":94,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":98,"categoryName":99,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000035","市场营销",{"categoryNo":101,"categoryName":102,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000036","内容创作者",[104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123],"seo content refresh","seo","seo content","content refresh","refresh","content","posts","remove","web search","performance","search","traffic","access","drop","websearch","revamp","merge","diagnosis","update","decay",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":132,"publishedAt":44},"01M70SBWQCHGH7HGS51Y0GTKKW","marketing-review-program","Plans how to ask real customers for honest public reviews: site choice, invitation copy, incentive and disclosure rules. Use to start a review program.","https:\u002F\u002Fgithub.com\u002FMuvon\u002Foctomind-tap\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketing-review-program\u002FSKILL.md",[130,131],{"categoryNo":93,"categoryName":94,"taxonomyType":95,"taxonomyTypeDesc":96},{"categoryNo":98,"categoryName":99,"taxonomyType":20,"taxonomyTypeDesc":21},[133,134,135,136,137,138,112,114,139,140,141,142,143,144,145,146,147,148,149,150],"program","review","marketing review program","marketing","reviews","get","campaign","choice","how to","only","generated","ask","plan","product","generate","customer","how","request",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":157,"publishedAt":44},"01M70SBB65Z2FC71Q7DEAXGJBG","geo-source-actions","Turns AI citation findings into ranked per-source actions for Reddit threads, listicles, review sites and videos. Records only. Use after a GEO audit.","https:\u002F\u002Fgithub.com\u002FMuvon\u002Foctomind-tap\u002Fblob\u002Fmaster\u002Fskills\u002Fgeo-source-actions\u002FSKILL.md",[],[158,159,160,161,162,138,112,114,163,164,142,118,134,165,166,167,146,168,169,39],"actions","geo source actions","source","geo","sources","copilot","domains","llms","threads","youtube","audit","action",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":179,"publishedAt":44},"01M70S99D3Y6GF097GTXWBXHPW","commerce-ai-readiness","Audits product feeds, markup and live pages for AI shopping assistants, then lists exact fixes. Use to make a store catalog readable to AI shoppers.","https:\u002F\u002Fgithub.com\u002FMuvon\u002Foctomind-tap\u002Fblob\u002Fmaster\u002Fskills\u002Fcommerce-ai-readiness\u002FSKILL.md",[176],{"categoryNo":177,"categoryName":178,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000031","产品经理",[180,181,182,183,184,185,186,187,188,189,114,190,163,142,116,191,192,146,168,193],"ai readiness","commerce ai readiness","commerce","readiness","feeds","ready","show","shopping","discover","checkout","up","ecommerce","documentation","recommend",{"skillNo":195,"name":196,"nameZh":6,"description":197,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":198,"categories":199,"keywords":203,"publishedAt":44},"01M6DWSX45J42KTK6XASKJRGPA","tap-model-training","Train, evaluate and publish the octomind-embed model behind capability auto-activation. Use when capability triggers or skill semantic() phrases change.","https:\u002F\u002Fgithub.com\u002FMuvon\u002Foctomind-tap\u002Fblob\u002Fmaster\u002Fskills\u002Ftap-model-training\u002FSKILL.md",[200],{"categoryNo":201,"categoryName":202,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000023","Skill与智能体开发",[204,205,206,207,208,190,209,210,211,212,213,214,215,216,217,149,218,219,33,122],"model","training","tap","tap model training","scope","eval","uv","auto","dataset","activate","api","capabilities","publish","change","embedding","re",{"skillNo":221,"name":222,"nameZh":6,"description":223,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":224,"categories":225,"keywords":227,"publishedAt":44},"01M6DWSQB7NSW53Z86XM81R1W1","tap-deps-authoring","Write dep scripts for the octomind-tap registry: header comments, platform.sh, mcp vs dep types, npx\u002Fuvx pattern. Use when editing deps\u002F\u003Corg>\u002F\u003Ctool>.sh.","https:\u002F\u002Fgithub.com\u002FMuvon\u002Foctomind-tap\u002Fblob\u002Fmaster\u002Fskills\u002Ftap-deps-authoring\u002FSKILL.md",[226],{"categoryNo":201,"categoryName":202,"taxonomyType":95,"taxonomyTypeDesc":96},[228,206,229,230,231,232,233,234,235,236,237,238,239,240,241,242,33,243,244,28],"deps","tap deps authoring","authoring","DEP","MCP","run","scripts","pattern","install","registry","platform","repo","editing","tool","types","write","org"]