[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72WN498V7W175THWDF9TF6D":3,"skill-same:01M72WN498V7W175THWDF9TF6D":106},{"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":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":41,"ownerHtmlUrl":42,"ownerBlogUrl":41,"ownerDescription":43,"updatedAt":44,"install":45,"resources":57},"01M72WN498V7W175THWDF9TF6D","copywriting",null,"Writes and reviews web copy for landing pages, README introductions and UX microcopy: hero, value proposition, headlines, CTA labels, error and empty-state text, SEO title and meta description, with a bundled script that lints headline, CTA, title and meta description length and banned phrases. Use when drafting or critiquing page content, marketing copy, a project tagline, button labels or error messages, or when copy must fit length limits before it is handed to a developer. Trigger terms: landing page, headline, CTA, call to action, microcopy, meta description, SEO title, tagline, PAS, AIDA, banned phrases. Not for HTML or CSS implementation (frontend), Astro pages and components (astro), technical documentation or ADRs (doc-writer) or PR descriptions (pr-logbook).","crewrig\u002Fcrewrig","crewrig","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F283580446?v=4","01M72WDBD9H0YW5JBHNZ0TEVWB","01M72WDBEBNRBAS94AXRPEVYNK",24,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig\u002Fblob\u002Fmain\u002Fartifacts\u002Fcore\u002Fskills\u002Fcopywriting\u002FSKILL.md",[],[],"2026-11-10 22:39:42",false,"---\nname: copywriting\ndescription: \"Writes and reviews web copy for landing pages, README introductions and UX microcopy: hero, value proposition, headlines, CTA labels, error and empty-state text, SEO title and meta description, with a bundled script that lints headline, CTA, title and meta description length and banned phrases. Use when drafting or critiquing page content, marketing copy, a project tagline, button labels or error messages, or when copy must fit length limits before it is handed to a developer. Trigger terms: landing page, headline, CTA, call to action, microcopy, meta description, SEO title, tagline, PAS, AIDA, banned phrases. Not for HTML or CSS implementation (frontend), Astro pages and components (astro), technical documentation or ADRs (doc-writer) or PR descriptions (pr-logbook).\"\ntype: skill\nlicense: Apache-2.0\ncompatibility: \"Requires Node.js 24 to run scripts\u002Flint-copy.ts as node scripts\u002Flint-copy.ts; without Node the skill still works as written guidance and the limits are read from references\u002Fseo-and-limits.md.\"\nmetadata:\n  provenance:\n    canonical: \"${CANONICAL_REPO}\"\n    feedback: \"${CANONICAL_REPO}\"\n    version: \"2.0.0\"\nclaude:\n  allowed-tools:\n    - Read\n    - Bash\n    - Write\n    - Edit\n  user-invocable: true\n---\n\n# Copywriting\n\nProduct-oriented web copy that converts instead of decorating. Positioning and audience\nare decisions made before this skill runs; layout and visual hierarchy belong to a\ndesigner. Deliver Markdown with clear section labels and no HTML, styling or layout\ndecisions in the copy.\n\n## Lint before handing over\n\nFixed questions (is the headline short enough, does the CTA name an action, did filler\nslip in) are settled by a script, not by eye. Run it from this skill's directory on every\npage you write or review:\n\n```sh\nnode scripts\u002Flint-copy.ts \u003Cpage.md|page.html|-> [--banned \u003Cfile>] [--format md|html] [--json]\n```\n\nIt reads front matter `title` and `description`, the first H1 as the headline, and links\nalone on their line (Markdown) or `\u003Cbutton>` and button-styled `\u003Ca>` (HTML) as CTAs. The\nnumeric limits live in the script (`--help` prints them) and are explained in\n`references\u002Fseo-and-limits.md`; do not restate the numbers in your own text.\n\n| Exit | Meaning | What to do |\n|---|---|---|\n| `0` | No error finding. Warnings (missing headline, title or description) may be listed. | Say which warnings are intended, then hand over. |\n| `1` | A length limit, a banned phrase or a CTA with no action. Each finding names the line and the fix. | Rewrite the flagged copy, never the limit, and run again. |\n| `2` | Usage error. | Fix the command line. |\n| `3` | The input or the `--banned` file cannot be read. | Check the path. |\n\nWhen the project keeps its own list of forbidden words, pass it with `--banned \u003Cfile>`\n(it replaces the default list). A finding is evidence for a rewrite: quote it in a review\nand propose the shorter text.\n\n## When to activate\n\n- Drafting or revising a landing page (hero, features, social proof, CTA blocks).\n- Writing README introductions or project taglines.\n- Editing microcopy: buttons, empty states, error messages, tooltips.\n- Reviewing someone else's copy for vague headlines, weak CTAs, jargon or translation\n  hazards.\n\n## Landing page anatomy\n\nA landing page is a sequence of decisions the reader makes. Each section answers exactly\none question, and the order is not arbitrary.\n\n1. **Hero**: *what is this and why should I care?* A headline (the outcome), a subheadline\n   (the specificity) and one primary CTA. No secondary distractions above the fold.\n2. **Value proposition**: *what changes for me?* The user-visible benefit, not the\n   implementation detail.\n3. **Feature sections**: *how does it do that?* One feature per block, each tied to a\n   benefit. Features without benefits are filler.\n4. **Social proof**: *why should I trust this?* Specificity beats superlatives (\"12k weekly\n   downloads\" beats \"loved by developers\").\n5. **Objection handling**: *what about my edge case?* FAQ, comparison table or a \"who this\n   is not for\" section. Naming objections out loud disarms them.\n6. **Final CTA**: repeats the hero's primary action, so the reader who scrolled this far\n   does not scroll back up.\n\nEach section should be removable without breaking the page. A section that cannot be\nremoved does two jobs and needs splitting. For the structure of a long page, or when the\nreader may not know they have the problem, pick a framework in\n`references\u002Fframeworks-and-tone.md` (PAS, BAB, AIDA) and the tone register for the audience.\n\n## Headlines\n\nThe headline carries more weight than the rest of the page, because most readers never\nreach the body.\n\n- **Outcome-focused**: name the result, not the mechanism. \"Deploy in under a minute\" beats\n  \"Kubernetes-based deployment platform\".\n- **Specific**: numbers, time bounds, named comparisons. \"Cut build time by 80 %\" beats\n  \"Faster builds\".\n- **No undefined jargon**: define the term in the subheadline or change the word.\n- **Active voice, present tense**: \"Ship faster\" beats \"Shipping is made faster\".\n\nA headline that describes what the company *is* rather than what the reader *gets* (\"A\nmodern platform for X\") is a positioning statement, not a headline.\n\n## CTAs\n\nA CTA is a contract: clicking it must lead to exactly what the label promises.\n\n- **One primary action per section.** Two equally weighted CTAs make the reader pick neither.\n- **Verb-first labels.** \"Start free trial\" beats \"Free trial\"; \"Read the docs\" beats\n  \"Documentation\".\n- **Friction reduction.** \"Start free, no credit card\" lowers the imagined cost of the\n  click. Name the next step when it is smaller than the reader expects.\n- **Secondary CTAs are subordinate**: a link, not a second button.\n- **Repeat the primary CTA** at commitment points (end of the hero, after social proof,\n  end of the page) rather than inventing a new one each time.\n\n## Microcopy\n\nMicrocopy is the writing inside the UI, where copy stops being marketing and becomes product.\n\n- **Buttons**: verb-first, scoped to the action. \"Save changes\" beats \"OK\"; \"Delete\n  project\" beats \"Confirm\".\n- **Error messages**: say what went wrong and what the user can do about it. Never show a\n  stack trace or internal code without a human-readable explanation beside it.\n- **Empty states**: explain what the screen will show once it has data, and provide the\n  action that fills it.\n- **Tooltips**: short, factual, one job. Anything that educates belongs in the docs.\n- **Confirmation dialogs**: name the consequence in the body and the action in the button\n  (\"This will permanently delete 12 files.\" with `[Cancel]` `[Delete 12 files]`). Do not\n  make the destructive action the highlighted default.\n\nRead the label out loud as if asking the user to do it; if the sentence feels odd, the\nlabel is wrong.\n\n## Output\n\nFor a writing task, deliver the copy as Markdown (front matter `title` and `description`\nwhen the page needs SEO text), lint it, and report the lint result. For a review, return\nfindings as a list: section, the specific weakness, a concrete rewrite. \"The hero feels\nweak\" is not actionable; a rewrite is.\n\n## References\n\n- `references\u002Fseo-and-limits.md`: the numeric limits and how the script finds each element,\n  SEO-aware writing, length headroom for translation.\n- `references\u002Fframeworks-and-tone.md`: PAS, BAB, AIDA, tone calibration.\n- `references\u002Fshared-friction-reporting.md`: how to report a friction in this skill.\n","# Copywriting\n\nProduct-oriented web copy that converts instead of decorating. Positioning and audience\nare decisions made before this skill runs; layout and visual hierarchy belong to a\ndesigner. Deliver Markdown with clear section labels and no HTML, styling or layout\ndecisions in the copy.\n\n## Lint before handing over\n\nFixed questions (is the headline short enough, does the CTA name an action, did filler\nslip in) are settled by a script, not by eye. Run it from this skill's directory on every\npage you write or review:\n\n```sh\nnode scripts\u002Flint-copy.ts \u003Cpage.md|page.html|-> [--banned \u003Cfile>] [--format md|html] [--json]\n```\n\nIt reads front matter `title` and `description`, the first H1 as the headline, and links\nalone on their line (Markdown) or `\u003Cbutton>` and button-styled `\u003Ca>` (HTML) as CTAs. The\nnumeric limits live in the script (`--help` prints them) and are explained in\n`references\u002Fseo-and-limits.md`; do not restate the numbers in your own text.\n\n| Exit | Meaning | What to do |\n|---|---|---|\n| `0` | No error finding. Warnings (missing headline, title or description) may be listed. | Say which warnings are intended, then hand over. |\n| `1` | A length limit, a banned phrase or a CTA with no action. Each finding names the line and the fix. | Rewrite the flagged copy, never the limit, and run again. |\n| `2` | Usage error. | Fix the command line. |\n| `3` | The input or the `--banned` file cannot be read. | Check the path. |\n\nWhen the project keeps its own list of forbidden words, pass it with `--banned \u003Cfile>`\n(it replaces the default list). A finding is evidence for a rewrite: quote it in a review\nand propose the shorter text.\n\n## When to activate\n\n- Drafting or revising a landing page (hero, features, social proof, CTA blocks).\n- Writing README introductions or project taglines.\n- Editing microcopy: buttons, empty states, error messages, tooltips.\n- Reviewing someone else's copy for vague headlines, weak CTAs, jargon or translation\n  hazards.\n\n## Landing page anatomy\n\nA landing page is a sequence of decisions the reader makes. Each section answers exactly\none question, and the order is not arbitrary.\n\n1. **Hero**: *what is this and why should I care?* A headline (the outcome), a subheadline\n   (the specificity) and one primary CTA. No secondary distractions above the fold.\n2. **Value proposition**: *what changes for me?* The user-visible benefit, not the\n   implementation detail.\n3. **Feature sections**: *how does it do that?* One feature per block, each tied to a\n   benefit. Features without benefits are filler.\n4. **Social proof**: *why should I trust this?* Specificity beats superlatives (\"12k weekly\n   downloads\" beats \"loved by developers\").\n5. **Objection handling**: *what about my edge case?* FAQ, comparison table or a \"who this\n   is not for\" section. Naming objections out loud disarms them.\n6. **Final CTA**: repeats the hero's primary action, so the reader who scrolled this far\n   does not scroll back up.\n\nEach section should be removable without breaking the page. A section that cannot be\nremoved does two jobs and needs splitting. For the structure of a long page, or when the\nreader may not know they have the problem, pick a framework in\n`references\u002Fframeworks-and-tone.md` (PAS, BAB, AIDA) and the tone register for the audience.\n\n## Headlines\n\nThe headline carries more weight than the rest of the page, because most readers never\nreach the body.\n\n- **Outcome-focused**: name the result, not the mechanism. \"Deploy in under a minute\" beats\n  \"Kubernetes-based deployment platform\".\n- **Specific**: numbers, time bounds, named comparisons. \"Cut build time by 80 %\" beats\n  \"Faster builds\".\n- **No undefined jargon**: define the term in the subheadline or change the word.\n- **Active voice, present tense**: \"Ship faster\" beats \"Shipping is made faster\".\n\nA headline that describes what the company *is* rather than what the reader *gets* (\"A\nmodern platform for X\") is a positioning statement, not a headline.\n\n## CTAs\n\nA CTA is a contract: clicking it must lead to exactly what the label promises.\n\n- **One primary action per section.** Two equally weighted CTAs make the reader pick neither.\n- **Verb-first labels.** \"Start free trial\" beats \"Free trial\"; \"Read the docs\" beats\n  \"Documentation\".\n- **Friction reduction.** \"Start free, no credit card\" lowers the imagined cost of the\n  click. Name the next step when it is smaller than the reader expects.\n- **Secondary CTAs are subordinate**: a link, not a second button.\n- **Repeat the primary CTA** at commitment points (end of the hero, after social proof,\n  end of the page) rather than inventing a new one each time.\n\n## Microcopy\n\nMicrocopy is the writing inside the UI, where copy stops being marketing and becomes product.\n\n- **Buttons**: verb-first, scoped to the action. \"Save changes\" beats \"OK\"; \"Delete\n  project\" beats \"Confirm\".\n- **Error messages**: say what went wrong and what the user can do about it. Never show a\n  stack trace or internal code without a human-readable explanation beside it.\n- **Empty states**: explain what the screen will show once it has data, and provide the\n  action that fills it.\n- **Tooltips**: short, factual, one job. Anything that educates belongs in the docs.\n- **Confirmation dialogs**: name the consequence in the body and the action in the button\n  (\"This will permanently delete 12 files.\" with `[Cancel]` `[Delete 12 files]`). Do not\n  make the destructive action the highlighted default.\n\nRead the label out loud as if asking the user to do it; if the sentence feels odd, the\nlabel is wrong.\n\n## Output\n\nFor a writing task, deliver the copy as Markdown (front matter `title` and `description`\nwhen the page needs SEO text), lint it, and report the lint result. For a review, return\nfindings as a list: section, the specific weakness, a concrete rewrite. \"The hero feels\nweak\" is not actionable; a rewrite is.\n\n## References\n\n- `references\u002Fseo-and-limits.md`: the numeric limits and how the script finds each element,\n  SEO-aware writing, length headroom for translation.\n- `references\u002Fframeworks-and-tone.md`: PAS, BAB, AIDA, tone calibration.\n- `references\u002Fshared-friction-reporting.md`: how to report a friction in this skill.\n",{"name":5,"type":23,"claude":24,"license":14,"metadata":31,"description":7,"compatibility":35},"skill",{"allowed-tools":25,"user-invocable":30},[26,27,28,29],"Read","Bash","Write","Edit",true,{"provenance":32},{"version":33,"feedback":34,"canonical":34},"2.0.0","${CANONICAL_REPO}","Requires Node.js 24 to run scripts\u002Flint-copy.ts as node scripts\u002Flint-copy.ts; without Node the skill still works as written guidance and the limits are read from references\u002Fseo-and-limits.md.","main","6d7f2262eb86a02d21a60a8147ed6f8a27d7b8eb","artifacts\u002Fcore\u002Fskills\u002Fcopywriting",6,"https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig","https:\u002F\u002Fcrewrig.org","https:\u002F\u002Fgithub.com\u002Fcrewrig","This is the organisation behind the crewrig framework","2026-11-15 04:46:08",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":30},[47,50,53],{"tool":48,"command":49},"npx","npx skills add crewrig\u002Fcrewrig --skill copywriting",{"tool":51,"command":52},"bunx","bunx skills add crewrig\u002Fcrewrig --skill copywriting",{"tool":54,"command":55},"pnpm","pnpm dlx skills add crewrig\u002Fcrewrig --skill copywriting","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig\u002Fblob\u002Fmain\u002Fartifacts\u002Fcore\u002Fskills\u002Fcopywriting\u002FSKILL.md",[58,64,68,72,76,80,84,88,92,96,100],{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"evals\u002Fevals.json","REFERENCE","参考文档",12276,"https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig\u002Fblob\u002Fmain\u002Fartifacts\u002Fcore\u002Fskills\u002Fcopywriting\u002Fevals\u002Fevals.json",{"path":65,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":66,"sourceHtmlUrl":67},"evals\u002Ffiles\u002Fbrand-banned.txt",41,"https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig\u002Fblob\u002Fmain\u002Fartifacts\u002Fcore\u002Fskills\u002Fcopywriting\u002Fevals\u002Ffiles\u002Fbrand-banned.txt",{"path":69,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":70,"sourceHtmlUrl":71},"evals\u002Ffiles\u002Flanding-clean.md",437,"https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig\u002Fblob\u002Fmain\u002Fartifacts\u002Fcore\u002Fskills\u002Fcopywriting\u002Fevals\u002Ffiles\u002Flanding-clean.md",{"path":73,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":74,"sourceHtmlUrl":75},"evals\u002Ffiles\u002Flanding-draft.html",500,"https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig\u002Fblob\u002Fmain\u002Fartifacts\u002Fcore\u002Fskills\u002Fcopywriting\u002Fevals\u002Ffiles\u002Flanding-draft.html",{"path":77,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":78,"sourceHtmlUrl":79},"evals\u002Ffiles\u002Flanding-draft.md",718,"https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig\u002Fblob\u002Fmain\u002Fartifacts\u002Fcore\u002Fskills\u002Fcopywriting\u002Fevals\u002Ffiles\u002Flanding-draft.md",{"path":81,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":82,"sourceHtmlUrl":83},"evals\u002Ffiles\u002Fproduct-brief.md",441,"https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig\u002Fblob\u002Fmain\u002Fartifacts\u002Fcore\u002Fskills\u002Fcopywriting\u002Fevals\u002Ffiles\u002Fproduct-brief.md",{"path":85,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":86,"sourceHtmlUrl":87},"evals\u002Ffiles\u002Fui-brief.md",386,"https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig\u002Fblob\u002Fmain\u002Fartifacts\u002Fcore\u002Fskills\u002Fcopywriting\u002Fevals\u002Ffiles\u002Fui-brief.md",{"path":89,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":90,"sourceHtmlUrl":91},"evals\u002Fresults.json",609,"https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig\u002Fblob\u002Fmain\u002Fartifacts\u002Fcore\u002Fskills\u002Fcopywriting\u002Fevals\u002Fresults.json",{"path":93,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Fframeworks-and-tone.md",2605,"https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig\u002Fblob\u002Fmain\u002Fartifacts\u002Fcore\u002Fskills\u002Fcopywriting\u002Freferences\u002Fframeworks-and-tone.md",{"path":97,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":98,"sourceHtmlUrl":99},"references\u002Fseo-and-limits.md",3685,"https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig\u002Fblob\u002Fmain\u002Fartifacts\u002Fcore\u002Fskills\u002Fcopywriting\u002Freferences\u002Fseo-and-limits.md",{"path":101,"resourceType":102,"resourceTypeDesc":103,"sizeBytes":104,"sourceHtmlUrl":105},"scripts\u002Flint-copy.ts","SCRIPT","脚本",13244,"https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig\u002Fblob\u002Fmain\u002Fartifacts\u002Fcore\u002Fskills\u002Fcopywriting\u002Fscripts\u002Flint-copy.ts",[107,115,120,125,130,135],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":114},"01M76AJKRKGGYZFJJHKE32Q5ZZ","fixture","Fixture skill. Mentions scripts\u002Ffrontmatter-only.ts which must be ignored.","https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig\u002Fblob\u002Fmain\u002Fscripts\u002Ftests\u002Ffixtures\u002Fskill-scripts-citations\u002Fyaml-example\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"skillNo":116,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":114},"01M76AJJHS0AHW5HJJQCVVJ4DH","https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig\u002Fblob\u002Fmain\u002Fscripts\u002Ftests\u002Ffixtures\u002Fskill-scripts-citations\u002Funterminated\u002FSKILL.md",[],[],{"skillNo":121,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":114},"01M76AJH8VJ2NAE000285J1D8F","https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig\u002Fblob\u002Fmain\u002Fscripts\u002Ftests\u002Ffixtures\u002Fskill-scripts-citations\u002Funresolved\u002FSKILL.md",[],[],{"skillNo":126,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":114},"01M76AJG4M862QH00H5QVVT60P","https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig\u002Fblob\u002Fmain\u002Fscripts\u002Ftests\u002Ffixtures\u002Fskill-scripts-citations\u002Fstray\u002FSKILL.md",[],[],{"skillNo":131,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":114},"01M76AJEZKZVMWZXCKXCFNQQ6B","https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig\u002Fblob\u002Fmain\u002Fscripts\u002Ftests\u002Ffixtures\u002Fskill-scripts-citations\u002Fresolving\u002FSKILL.md",[],[],{"skillNo":136,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":114},"01M76AJD4G4K2YK2SMN8NSEG9R","https:\u002F\u002Fgithub.com\u002Fcrewrig\u002Fcrewrig\u002Fblob\u002Fmain\u002Fscripts\u002Ftests\u002Ffixtures\u002Fskill-scripts-citations\u002Freferences-unfenced\u002FSKILL.md",[],[]]