[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6RVEDKQK4JECTCTDMAWHFM6":3,"skill-same:01M6RVEDKQK4JECTCTDMAWHFM6":75},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":13,"repositoryHtmlUrl":59,"repositoryHomepageUrl":6,"ownerHtmlUrl":60,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":61,"install":62,"resources":74},"01M6RVEDKQK4JECTCTDMAWHFM6","jpa-patterns",null,"JPA\u002FHibernate patterns for entity design, relationships, query optimization, transactions, auditing, indexing, pagination, and pooling in Spring Boot.","sakamoto-family-smile\u002Fagent_monorepo","sakamoto-family-smile","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F132812403?v=4","01M6RTAT3H8PMWX5SJ65KP3VYF","01M6RTAV321WB5RAHCWTZMX5CV",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fecc\u002Fjpa-patterns\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"patterns","jpa","jpa patterns","Optimization","transactions","spring","query optimization","hibernate","pagination","design","query","relationships","indexing","spring boot","entity","for","pooling","boot","2026-11-10 10:12:30",false,"---\nname: blog-localize\ndescription: Cultural adaptation for translated content. Run AFTER blog-translate completes. Adjusts brand examples, CTAs, legal references, and formality for the target market (German, French, Japanese, Spanish, etc.). Deep cultural adaptation of translated blog posts. Goes beyond translation to swap brand examples, adapt CTAs, substitute legal references, localize statistic sources where possible, and adjust formality (Sie\u002Fdu, tu\u002Fvous, formal\u002Finformal). Built-in profiles for DACH, Francophone, Hispanic, and Japanese markets, plus a custom-locale template. Makes content feel locally authored, not translated. Use when user says \"localize blog\", \"blog localize\", \"cultural adaptation\", \"adapt for Germany\", \"adapt for France\", \"lokalisieren\", \"localiser\", \"adaptar\".\nuser_invocable: true\nargument-hint: \"\u003Cfile> --locale \u003Clocale-code>\"\nlicense: MIT\ncompatibility: Standalone within claude-blog. Invoked by blog-multilingual.\nmetadata:\n  author: AgriciDaniel\n  version: \"1.9.1\"\n  category: blog\n---\n\n# Blog Localize, Cultural Deep-Adaptation\n\nTakes a translated blog post and performs cultural adaptation so the result\nfeels like it was written for the target market, not translated into it.\nThis is the layer above `blog-translate`: it replaces examples, adjusts\ntone, swaps references, and localizes the entire reading experience.\n\n> Adapted from `claude-blog-multilingual` by Chris Mueller (Pro Hub Challenge,\n> March 2026). Original: https:\u002F\u002Fgithub.com\u002FChriss54\u002Fmultilingual-int\n\n## Key References\n\n- `..\u002Fblog-translate\u002Freferences\u002Fcultural-adaptation.md`, the shared cultural\n  profiles file with substitution tables for DACH, Francophone, Hispanic,\n  Japanese, and a custom template. Do not duplicate this file.\n\n## When to Use\n\n- Right after `blog-translate` produces a base translation.\n- When existing translated content reads like \"translated from English\".\n- When targeting a specific market, not just a language.\n- When content needs local statistics, examples, and brand references.\n\n## Workflow\n\n### Phase 1: Locale Understanding\n\n1. Parse the locale code. Accept full codes (`de-DE`, `fr-CA`, `es-MX`,\n   `pt-BR`, `zh-TW`) or plain language codes (`de`, `fr`).\n2. Load the cultural profile from\n   `..\u002Fblog-translate\u002Freferences\u002Fcultural-adaptation.md`.\n   - If the locale has a profile, use it.\n   - If not, follow the \"Custom-locale template\" section in that reference\n     to build a minimal profile inline.\n3. Read the translated post and identify adaptation targets.\n\n### Phase 2: Cultural Audit\n\nScan for elements that signal foreign origin:\n\n| Element | What to look for |\n|---------|------------------|\n| Brand examples | US or UK brands with no relevance locally |\n| Statistics sources | US-only studies and surveys |\n| CTAs | American-style aggressive calls-to-action |\n| Idioms | Literally translated English expressions |\n| Legal references | Foreign laws (CCPA, FTC) where local law applies (DSGVO, RGPD) |\n| Cultural references | Foreign holidays, events, customs |\n| Currency and pricing | USD without conversion or context |\n| Tone | Too casual or too formal for the target market |\n| Address form | Inconsistent Sie\u002Fdu, tu\u002Fvous, formal\u002Finformal |\n\nOutput an audit report listing every target with severity (critical,\nrecommended, optional).\n\n### Phase 3: Adaptation\n\n#### 3a. Example Substitution\n\nSwap foreign examples for local equivalents:\n\n- Use WebSearch to find local case studies, brands, or scenarios.\n- Replace inline, preserving the same argument and structure.\n- If no local equivalent exists, keep the original but add local context\n  (\"In the German market, the equivalent dynamic is X\").\n\n#### 3b. Statistics Localization\n\n- Search for equivalent local statistics (`[topic] statistik [country] 2025\n  2026`).\n- If local data exists, swap the source and the figure together. Keep one\n  named source per claim.\n- If not, keep the original stat but mark its geographic scope (\"In the\n  US, ...\").\n- Never strip source attribution.\n\n#### 3c. CTA Adaptation\n\nRewrite calls-to-action per the cultural profile:\n\n- Adjust aggressiveness level (DACH and JA prefer informational, US prefers\n  imperative).\n- Use culturally appropriate action verbs.\n- Adapt urgency framing.\n\n#### 3d. Tone Calibration\n\n- Match formality per profile (DACH defaults to Sie for B2B, du for B2C\n  lifestyle; FR defaults to vous; JA shifts register sharply by audience).\n- Ensure consistent formal or informal address throughout the entire\n  document.\n- Match local content-style conventions.\n\n#### 3e. Legal and Regulatory Context\n\n- Replace references to foreign laws with local equivalents (CCPA becomes\n  DSGVO in DE, RGPD in FR, LGPD in BR).\n- Add local compliance notes where they help the reader.\n- Remove irrelevant foreign regulatory references.\n\n#### 3f. Brand Example Swaps (Quick Map)\n\nProfiles in `..\u002Fblog-translate\u002Freferences\u002Fcultural-adaptation.md` provide\nsubstitution tables. Common examples:\n\n| Source (US) | DACH | FR | ES (Spain) | LATAM | JA |\n|-------------|------|----|----|-------|----|\n| Walmart | MediaMarkt | Carrefour | El Corte Ingles | Walmart MX | Aeon |\n| Target | Saturn | Auchan | Hipercor | Liverpool | Ito-Yokado |\n| FTC | Bundeskartellamt | DGCCRF | CNMC | Profeco (MX) | JFTC |\n| CCPA | DSGVO | RGPD | RGPD | LGPD (BR) | APPI |\n\n### Phase 4: Quality Verification\n\n- All critical adaptation targets addressed.\n- Tone is consistent throughout.\n- No remaining foreign-origin markers.\n- Statistics have valid sources (original or localized).\n- CTAs match cultural expectations.\n- Formal or informal address is consistent end to end.\n- Content still supports the same argument as the original.\n- SEO elements remain optimized (keywords, meta, headings).\n- Word count is within the expected ratio for the language pair.\n\n### Phase 5: Save and Report\n\n1. Save the localized version. Default: overwrite the translated file.\n   Optional: save as `{slug}-localized.{ext}` if the user wants to keep the\n   pre-localization version.\n\n2. Present the summary:\n\n   ```\n   ## Localization complete: [Title]\n\n   ### Target locale: [locale-code] ([locale-name])\n\n   ### Adaptations made\n   | Type | Count | Examples |\n   |------|-------|----------|\n   | Brand examples | [N] | Walmart -> MediaMarkt |\n   | Statistics | [N] | US survey -> DACH survey |\n   | CTAs | [N] | \"Buy now\" -> \"Jetzt entdecken\" |\n   | Tone adjustments | [N] | Casual -> Sie |\n   | Legal references | [N] | CCPA -> DSGVO |\n   | Cultural references | [N] | Thanksgiving -> Weihnachtsgeschaeft |\n\n   ### Cultural fit score\n   - Naturalness: [1-10]\n   - Market relevance: [1-10]\n   - Tone match: [1-10]\n   - Overall: [N]\u002F30\n\n   ### Remaining recommendations\n   - [Optional adaptations not applied]\n   ```\n\n## Error Handling\n\n| Scenario | Action |\n|----------|--------|\n| No cultural profile for the locale | Build a minimal profile from the custom-locale template, proceed |\n| File is not in the expected language | Warn the user, offer to translate first |\n| No local statistics available | Keep the original stat with a geographic-scope note |\n| Locale code ambiguous (e.g., `pt`) | Ask: \"Did you mean `pt-BR` (Brazil) or `pt-PT` (Portugal)?\" |\n\n## Cross-References\n\n- Pre-step (translation): `\u002Fblog translate \u003Cfile> --to \u003Ccode>`\n- QA across language versions: `\u002Fblog locale-audit \u003Cdirectory>`\n- One-command pipeline: `\u002Fblog multilingual \u003Ctopic> --languages \u003Ccodes>`\n","# Blog Localize, Cultural Deep-Adaptation\n\nTakes a translated blog post and performs cultural adaptation so the result\nfeels like it was written for the target market, not translated into it.\nThis is the layer above `blog-translate`: it replaces examples, adjusts\ntone, swaps references, and localizes the entire reading experience.\n\n> Adapted from `claude-blog-multilingual` by Chris Mueller (Pro Hub Challenge,\n> March 2026). Original: https:\u002F\u002Fgithub.com\u002FChriss54\u002Fmultilingual-int\n\n## Key References\n\n- `..\u002Fblog-translate\u002Freferences\u002Fcultural-adaptation.md`, the shared cultural\n  profiles file with substitution tables for DACH, Francophone, Hispanic,\n  Japanese, and a custom template. Do not duplicate this file.\n\n## When to Use\n\n- Right after `blog-translate` produces a base translation.\n- When existing translated content reads like \"translated from English\".\n- When targeting a specific market, not just a language.\n- When content needs local statistics, examples, and brand references.\n\n## Workflow\n\n### Phase 1: Locale Understanding\n\n1. Parse the locale code. Accept full codes (`de-DE`, `fr-CA`, `es-MX`,\n   `pt-BR`, `zh-TW`) or plain language codes (`de`, `fr`).\n2. Load the cultural profile from\n   `..\u002Fblog-translate\u002Freferences\u002Fcultural-adaptation.md`.\n   - If the locale has a profile, use it.\n   - If not, follow the \"Custom-locale template\" section in that reference\n     to build a minimal profile inline.\n3. Read the translated post and identify adaptation targets.\n\n### Phase 2: Cultural Audit\n\nScan for elements that signal foreign origin:\n\n| Element | What to look for |\n|---------|------------------|\n| Brand examples | US or UK brands with no relevance locally |\n| Statistics sources | US-only studies and surveys |\n| CTAs | American-style aggressive calls-to-action |\n| Idioms | Literally translated English expressions |\n| Legal references | Foreign laws (CCPA, FTC) where local law applies (DSGVO, RGPD) |\n| Cultural references | Foreign holidays, events, customs |\n| Currency and pricing | USD without conversion or context |\n| Tone | Too casual or too formal for the target market |\n| Address form | Inconsistent Sie\u002Fdu, tu\u002Fvous, formal\u002Finformal |\n\nOutput an audit report listing every target with severity (critical,\nrecommended, optional).\n\n### Phase 3: Adaptation\n\n#### 3a. Example Substitution\n\nSwap foreign examples for local equivalents:\n\n- Use WebSearch to find local case studies, brands, or scenarios.\n- Replace inline, preserving the same argument and structure.\n- If no local equivalent exists, keep the original but add local context\n  (\"In the German market, the equivalent dynamic is X\").\n\n#### 3b. Statistics Localization\n\n- Search for equivalent local statistics (`[topic] statistik [country] 2025\n  2026`).\n- If local data exists, swap the source and the figure together. Keep one\n  named source per claim.\n- If not, keep the original stat but mark its geographic scope (\"In the\n  US, ...\").\n- Never strip source attribution.\n\n#### 3c. CTA Adaptation\n\nRewrite calls-to-action per the cultural profile:\n\n- Adjust aggressiveness level (DACH and JA prefer informational, US prefers\n  imperative).\n- Use culturally appropriate action verbs.\n- Adapt urgency framing.\n\n#### 3d. Tone Calibration\n\n- Match formality per profile (DACH defaults to Sie for B2B, du for B2C\n  lifestyle; FR defaults to vous; JA shifts register sharply by audience).\n- Ensure consistent formal or informal address throughout the entire\n  document.\n- Match local content-style conventions.\n\n#### 3e. Legal and Regulatory Context\n\n- Replace references to foreign laws with local equivalents (CCPA becomes\n  DSGVO in DE, RGPD in FR, LGPD in BR).\n- Add local compliance notes where they help the reader.\n- Remove irrelevant foreign regulatory references.\n\n#### 3f. Brand Example Swaps (Quick Map)\n\nProfiles in `..\u002Fblog-translate\u002Freferences\u002Fcultural-adaptation.md` provide\nsubstitution tables. Common examples:\n\n| Source (US) | DACH | FR | ES (Spain) | LATAM | JA |\n|-------------|------|----|----|-------|----|\n| Walmart | MediaMarkt | Carrefour | El Corte Ingles | Walmart MX | Aeon |\n| Target | Saturn | Auchan | Hipercor | Liverpool | Ito-Yokado |\n| FTC | Bundeskartellamt | DGCCRF | CNMC | Profeco (MX) | JFTC |\n| CCPA | DSGVO | RGPD | RGPD | LGPD (BR) | APPI |\n\n### Phase 4: Quality Verification\n\n- All critical adaptation targets addressed.\n- Tone is consistent throughout.\n- No remaining foreign-origin markers.\n- Statistics have valid sources (original or localized).\n- CTAs match cultural expectations.\n- Formal or informal address is consistent end to end.\n- Content still supports the same argument as the original.\n- SEO elements remain optimized (keywords, meta, headings).\n- Word count is within the expected ratio for the language pair.\n\n### Phase 5: Save and Report\n\n1. Save the localized version. Default: overwrite the translated file.\n   Optional: save as `{slug}-localized.{ext}` if the user wants to keep the\n   pre-localization version.\n\n2. Present the summary:\n\n   ```\n   ## Localization complete: [Title]\n\n   ### Target locale: [locale-code] ([locale-name])\n\n   ### Adaptations made\n   | Type | Count | Examples |\n   |------|-------|----------|\n   | Brand examples | [N] | Walmart -> MediaMarkt |\n   | Statistics | [N] | US survey -> DACH survey |\n   | CTAs | [N] | \"Buy now\" -> \"Jetzt entdecken\" |\n   | Tone adjustments | [N] | Casual -> Sie |\n   | Legal references | [N] | CCPA -> DSGVO |\n   | Cultural references | [N] | Thanksgiving -> Weihnachtsgeschaeft |\n\n   ### Cultural fit score\n   - Naturalness: [1-10]\n   - Market relevance: [1-10]\n   - Tone match: [1-10]\n   - Overall: [N]\u002F30\n\n   ### Remaining recommendations\n   - [Optional adaptations not applied]\n   ```\n\n## Error Handling\n\n| Scenario | Action |\n|----------|--------|\n| No cultural profile for the locale | Build a minimal profile from the custom-locale template, proceed |\n| File is not in the expected language | Warn the user, offer to translate first |\n| No local statistics available | Keep the original stat with a geographic-scope note |\n| Locale code ambiguous (e.g., `pt`) | Ask: \"Did you mean `pt-BR` (Brazil) or `pt-PT` (Portugal)?\" |\n\n## Cross-References\n\n- Pre-step (translation): `\u002Fblog translate \u003Cfile> --to \u003Ccode>`\n- QA across language versions: `\u002Fblog locale-audit \u003Cdirectory>`\n- One-command pipeline: `\u002Fblog multilingual \u003Ctopic> --languages \u003Ccodes>`\n",{"name":46,"license":47,"metadata":48,"description":52,"argument-hint":53,"compatibility":54,"user_invocable":55},"blog-localize","MIT",{"author":49,"version":50,"category":51},"AgriciDaniel","1.9.1","blog","Cultural adaptation for translated content. Run AFTER blog-translate completes. Adjusts brand examples, CTAs, legal references, and formality for the target market (German, French, Japanese, Spanish, etc.). Deep cultural adaptation of translated blog posts. Goes beyond translation to swap brand examples, adapt CTAs, substitute legal references, localize statistic sources where possible, and adjust formality (Sie\u002Fdu, tu\u002Fvous, formal\u002Finformal). Built-in profiles for DACH, Francophone, Hispanic, and Japanese markets, plus a custom-locale template. Makes content feel locally authored, not translated. Use when user says \"localize blog\", \"blog localize\", \"cultural adaptation\", \"adapt for Germany\", \"adapt for France\", \"lokalisieren\", \"localiser\", \"adaptar\".","\u003Cfile> --locale \u003Clocale-code>","Standalone within claude-blog. Invoked by blog-multilingual.",true,"main","60a901a00f46e71601f58727cb5661f8d3fb6d24",".claude\u002Fskills\u002Fecc\u002Fjpa-patterns","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile","2026-11-08 20:29:14",{"source":8,"skillName":46,"commands":63,"prompt":73,"zipAvailable":55},[64,67,70],{"tool":65,"command":66},"npx","npx skills add sakamoto-family-smile\u002Fagent_monorepo --skill blog-localize",{"tool":68,"command":69},"bunx","bunx skills add sakamoto-family-smile\u002Fagent_monorepo --skill blog-localize",{"tool":71,"command":72},"pnpm","pnpm dlx skills add sakamoto-family-smile\u002Fagent_monorepo --skill blog-localize","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fecc\u002Fjpa-patterns\u002FSKILL.md",[],[76,108,116,136,159,187],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":88,"publishedAt":41},"01M6RW50THEFSKK42YNR8XFZA1","remotion-video-creation","Best practices for Remotion - Video creation in React. 29 domain-specific rules covering 3D, animations, audio, captions, charts, transitions, and more.","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fecc\u002Fremotion-video-creation\u002FSKILL.md",[82,85],{"categoryNo":83,"categoryName":84,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":86,"categoryName":87,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",[89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,38],"Video","remotion video","remotion video creation","creation","Remotion","Charts","Captions","Audio","3D","Composition","Animation","best practices","more","animations","domain-specific","domain","three","Rules","Lottie",{"skillNo":109,"name":110,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":41},"01M6VCJ23NPECPSZJKGY691F75","hotcook-recipes","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002Fhotcook-agent\u002Fdata\u002Fskills\u002Fhotcook-recipes\u002FSKILL.md",[],[114,115],"hotcook recipes","recipes",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":130,"publishedAt":41},"01M6VCHHE00X5XHSDRD1KH1BW2","code-helper","Code review and assistance skill","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002Fagent-system-2\u002Fskills\u002Fcode-helper\u002Fskill.md",[122,125],{"categoryNo":123,"categoryName":124,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":126,"categoryName":127,"taxonomyType":128,"taxonomyTypeDesc":129},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[131,132,133,134,135],"code helper","helper","code","code review","review",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":148,"publishedAt":41},"01M6VCH3Q31A20H6SQ1H0J7JB2","research-assistant","Web research assistant skill using Brave Search MCP","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002Fagent-system-1\u002Fskills\u002Fresearch-assistant\u002Fskill.md",[142,145],{"categoryNo":143,"categoryName":144,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":146,"categoryName":147,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[149,150,151,152,153,154,155,156,157,158],"research assistant","research","assistant","MCP","web","search","brave search","web research","brave","web research assistant",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":169,"publishedAt":41},"01M6VCGZZGPNVJSCZ1JTMNZAHY","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fecc\u002Fx-api\u002FSKILL.md",[165,168],{"categoryNo":166,"categoryName":167,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":126,"categoryName":127,"taxonomyType":128,"taxonomyTypeDesc":129},[170,171,172,173,174,175,38,176,177,178,179,180,23,181,182,183,184,185,154,186],"x api","api","with","when","limits","rate","threads","reading","native","posting","platform","api integration","twitter","use","auth","analytics","OAuth",{"skillNo":188,"name":189,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":191,"categories":192,"keywords":194,"publishedAt":41},"01M6VCGVX6DGB1FKTA53QBBCQB","workspace-surface-audit","Audit the active repo, MCP servers, plugins, connectors, env surfaces, and harness setup, then recommend the highest-value ECC-native skills, hooks, agents, and operator workflows. Use when the user wants help setting up Claude Code or understanding what capabilities are actually available in their environment.","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fecc\u002Fworkspace-surface-audit\u002FSKILL.md",[193],{"categoryNo":146,"categoryName":147,"taxonomyType":20,"taxonomyTypeDesc":21},[195,196,197,198,152,199,200,133,201,202,203,204,183,205,206,207,208,178,209,173],"workspace surface audit","workspace","audit","hooks","workflows","connectors","capabilities","harness","repo","environment","up","harness setup","active","env","value"]