[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DN7RB84F9BAE4PMJBHGFSB":3,"skill-same:01M7DN7RB84F9BAE4PMJBHGFSB":79},{"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":15,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":13,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7DN7RB84F9BAE4PMJBHGFSB","cratis-discoverability",null,"Check Cratis content before publishing for search and AI answers without sacrificing readability. Use when reviewing discoverability, SEO, AEO or GEO; writing fact blocks or download claims; editing package\u002Frepo metadata; checking docs titles, descriptions or LLM export budgets; or reviewing founder\u002Fcompany JSON-LD and member profile indexing. Not for page voice and structure (cratis-documentation-writing), llms.txt design (cratis-llm-friendly-documentation), distribution plans (cratis-developer-marketing) or length decisions (cratis-content-length).","Cratis\u002FFundamentals.Go","Cratis","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F16456213?v=4","01M6BXRH290K4C8RS4PTKK3HXQ","01M7DN6YCMASAFGKYBBH3C1Z6E",0,"MIT","https:\u002F\u002Fgithub.com\u002FCratis\u002FFundamentals.Go\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fcratis-discoverability\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FCratis\u002FFundamentals.Go\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fcratis-discoverability\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: cratis-discoverability\ndescription: Check Cratis content before publishing for search and AI answers without sacrificing readability. Use when reviewing discoverability, SEO, AEO or GEO; writing fact blocks or download claims; editing package\u002Frepo metadata; checking docs titles, descriptions or LLM export budgets; or reviewing founder\u002Fcompany JSON-LD and member profile indexing. Not for page voice and structure (cratis-documentation-writing), llms.txt design (cratis-llm-friendly-documentation), distribution plans (cratis-developer-marketing) or length decisions (cratis-content-length).\nlicense: MIT\n---\n\u003C!-- cratis-ai-managed: skills\u002Fcratis-discoverability\u002FSKILL.md -->\n\n# Discoverability before you publish\n\nDiscoverability is a property of good content: a clear definition, an honest title, one name per\nthing and working links. The always-on rule is [discoverability.md](..\u002F..\u002Frules\u002Fdiscoverability.md);\nthis skill is the procedure to run on the finished draft. If a fix makes the page worse to read,\ndrop the fix and say so.\n\n## Procedure\n\n1. Name the content type: docs page, blog post, landing page, README, package\u002Frepo metadata or member profile.\n2. Name the reader's one job and, for docs, the page type (tutorial, how-to, reference, explanation).\n3. Apply the checks for that type below, including facts, adoption claims and privacy without waiting for a separate request. Fix the draft; do not annotate it.\n4. For a built site, run the checker and fix errors; warnings are judgment calls to report.\n5. Report what was changed, what was left alone and why.\n\nRead `references\u002Fpage-checklist.md` when checking a page, including docs lint baselines and LLM export budgets.\n\n## Checks by content type\n\n- **Docs page.** The `description` is written by hand as one self-contained\n  definition or outcome sentence. Tutorials, getting-started pages and explanations follow\n  `writing-cratis-docs` (scenario first); the definition lives in the `description`, and one\n  definition sentence may follow the opening scenario where it reads naturally. `writing-cratis-docs`\n  wins on voice and structure. Product index pages open with the definition sentence.\n  Reference pages stay terse: title is the exact name plus its product, no question headings, no\n  intro. Titles are unique across the site and name the product (\"Chronicle projections\"). Keep\n  description and duplicate-title lint baselines at 0; never raise a baseline to pass. Check\n  rendered titles and measure `llms.txt` \u002F `llms-small.txt` bytes against the site budgets.\n- **Blog post.** The title states the topic in the words a reader would search. The intro gives the\n  conclusion in two sentences. Show the named author and date, add `lastUpdated` only for real\n  changes, link the owning docs pages with `https:\u002F\u002Fwww.cratis.io\u002F...`, keep `description` apart\n  from the card `excerpt`.\n- **Landing page.** One primary term in the title, the `\u003Ch1>` or the first paragraph, and a\n  one-sentence definition above the fold. Brand lines stay; pair them with a category term in the\n  title and description. Respect the claim gate in `BRAND.md`, `MESSAGING.md` and `SITE.md`.\n- **README.** The H1 may be the product name (\"Cratis \u003CProduct>\"). The first sentence defines the product in 15-35 plain\n  nouns, with no logo-only or metaphor opener. Links are absolute; link the docs page.\n- **Package metadata.** One sentence naming what the package is and which Cratis product it belongs\n  to, identical to the README opener. `PackageProjectUrl` and `homepage` point at the docs page, not\n  only at GitHub. Read `references\u002Fpackage-metadata.md` when editing package fields, GitHub About,\n  Docker Hub descriptions, analyzer help links, template messages or README footers. Check these\n  surfaces together; Authors and Company are `Cratis`.\n\n## Fact blocks and adoption claims\n\nFor each entity page, assemble one sourced \"at a glance\" block from verifiable facts, with dates\nfor counts. Read `references\u002Ffacts-and-adoption.md` when selecting facts or calculating downloads:\nidentify entry packages and continuation predecessors, exclude sub-packages and overlapping\nshared dependencies, round down to a stated threshold, and publish the month and registries.\nDownloads are never users or customers. Omit unsupported claims instead of inventing customers,\nuser counts, benchmarks, certifications, prices or competitor comparisons. Keep shared guidance\ngeneric; do not copy private integration names, legal entity details or factual counts into it.\n\n## Names\n\nUse the canonical names, one per concept, and the first-mention rule. Read\n`references\u002Fentities.md` when naming a product, writing a definition sentence or filling `sameAs`.\nDo not invent a name, URL, maturity word or claim that the references do not state.\n\n## Structured data\n\nDescribe only what is visible on the page, one `@graph` per page, stable `@id`s. Add no `HowTo` and\nno new `FAQPage`. Read `references\u002Fstructured-data.md` for the patterns and what each page type\ngets. Use only public, owner-approved founder\u002Fcompany facts. Do not name other people in\nstructured data; never add personal data or `Person` entities for community members. Member\nprofiles are `noindex`; check profile and CV routes, rendered robots directives and JSON-LD.\nWithout approved public founder facts, reference the organization by `@id` instead.\n\n## Checking a built site\n\nFor a built static site (Astro `dist\u002F` or a plain-HTML repository root), run with Node.js:\n`node \u003Cskill-directory>\u002Fscripts\u002Fverify-discoverability.mjs --root \u003Cdir> --site \u003Chttps:\u002F\u002Fhost>`.\nIt reports `\u003Chtml lang>`, title, description, canonical host, `\u003Ch1>` count, JSON-LD parse errors,\n`robots.txt`, the sitemap and `llms.txt` structure. Errors exit 1; warnings do not. Pass\n`--warn-only` to downgrade errors and `--require-llms` where the site ships `llms.txt`.\nRead `scripts\u002Fverify-discoverability.mjs` only when changing the checker.\n\n## Pitfalls\n\n- Question headings everywhere: use them only where they read naturally (concept pages, FAQs,\n  comparisons, blog), never on reference pages or tutorial steps.\n- Padding to a word count: there is no minimum length; a complete page is done.\n- Apex `https:\u002F\u002Fcratis.io\u002F` links: the docs host is `https:\u002F\u002Fwww.cratis.io`.\n- A description that repeats the title or a sibling page's description.\n","\u003C!-- cratis-ai-managed: skills\u002Fcratis-discoverability\u002FSKILL.md -->\n\n# Discoverability before you publish\n\nDiscoverability is a property of good content: a clear definition, an honest title, one name per\nthing and working links. The always-on rule is [discoverability.md](..\u002F..\u002Frules\u002Fdiscoverability.md);\nthis skill is the procedure to run on the finished draft. If a fix makes the page worse to read,\ndrop the fix and say so.\n\n## Procedure\n\n1. Name the content type: docs page, blog post, landing page, README, package\u002Frepo metadata or member profile.\n2. Name the reader's one job and, for docs, the page type (tutorial, how-to, reference, explanation).\n3. Apply the checks for that type below, including facts, adoption claims and privacy without waiting for a separate request. Fix the draft; do not annotate it.\n4. For a built site, run the checker and fix errors; warnings are judgment calls to report.\n5. Report what was changed, what was left alone and why.\n\nRead `references\u002Fpage-checklist.md` when checking a page, including docs lint baselines and LLM export budgets.\n\n## Checks by content type\n\n- **Docs page.** The `description` is written by hand as one self-contained\n  definition or outcome sentence. Tutorials, getting-started pages and explanations follow\n  `writing-cratis-docs` (scenario first); the definition lives in the `description`, and one\n  definition sentence may follow the opening scenario where it reads naturally. `writing-cratis-docs`\n  wins on voice and structure. Product index pages open with the definition sentence.\n  Reference pages stay terse: title is the exact name plus its product, no question headings, no\n  intro. Titles are unique across the site and name the product (\"Chronicle projections\"). Keep\n  description and duplicate-title lint baselines at 0; never raise a baseline to pass. Check\n  rendered titles and measure `llms.txt` \u002F `llms-small.txt` bytes against the site budgets.\n- **Blog post.** The title states the topic in the words a reader would search. The intro gives the\n  conclusion in two sentences. Show the named author and date, add `lastUpdated` only for real\n  changes, link the owning docs pages with `https:\u002F\u002Fwww.cratis.io\u002F...`, keep `description` apart\n  from the card `excerpt`.\n- **Landing page.** One primary term in the title, the `\u003Ch1>` or the first paragraph, and a\n  one-sentence definition above the fold. Brand lines stay; pair them with a category term in the\n  title and description. Respect the claim gate in `BRAND.md`, `MESSAGING.md` and `SITE.md`.\n- **README.** The H1 may be the product name (\"Cratis \u003CProduct>\"). The first sentence defines the product in 15-35 plain\n  nouns, with no logo-only or metaphor opener. Links are absolute; link the docs page.\n- **Package metadata.** One sentence naming what the package is and which Cratis product it belongs\n  to, identical to the README opener. `PackageProjectUrl` and `homepage` point at the docs page, not\n  only at GitHub. Read `references\u002Fpackage-metadata.md` when editing package fields, GitHub About,\n  Docker Hub descriptions, analyzer help links, template messages or README footers. Check these\n  surfaces together; Authors and Company are `Cratis`.\n\n## Fact blocks and adoption claims\n\nFor each entity page, assemble one sourced \"at a glance\" block from verifiable facts, with dates\nfor counts. Read `references\u002Ffacts-and-adoption.md` when selecting facts or calculating downloads:\nidentify entry packages and continuation predecessors, exclude sub-packages and overlapping\nshared dependencies, round down to a stated threshold, and publish the month and registries.\nDownloads are never users or customers. Omit unsupported claims instead of inventing customers,\nuser counts, benchmarks, certifications, prices or competitor comparisons. Keep shared guidance\ngeneric; do not copy private integration names, legal entity details or factual counts into it.\n\n## Names\n\nUse the canonical names, one per concept, and the first-mention rule. Read\n`references\u002Fentities.md` when naming a product, writing a definition sentence or filling `sameAs`.\nDo not invent a name, URL, maturity word or claim that the references do not state.\n\n## Structured data\n\nDescribe only what is visible on the page, one `@graph` per page, stable `@id`s. Add no `HowTo` and\nno new `FAQPage`. Read `references\u002Fstructured-data.md` for the patterns and what each page type\ngets. Use only public, owner-approved founder\u002Fcompany facts. Do not name other people in\nstructured data; never add personal data or `Person` entities for community members. Member\nprofiles are `noindex`; check profile and CV routes, rendered robots directives and JSON-LD.\nWithout approved public founder facts, reference the organization by `@id` instead.\n\n## Checking a built site\n\nFor a built static site (Astro `dist\u002F` or a plain-HTML repository root), run with Node.js:\n`node \u003Cskill-directory>\u002Fscripts\u002Fverify-discoverability.mjs --root \u003Cdir> --site \u003Chttps:\u002F\u002Fhost>`.\nIt reports `\u003Chtml lang>`, title, description, canonical host, `\u003Ch1>` count, JSON-LD parse errors,\n`robots.txt`, the sitemap and `llms.txt` structure. Errors exit 1; warnings do not. Pass\n`--warn-only` to downgrade errors and `--require-llms` where the site ships `llms.txt`.\nRead `scripts\u002Fverify-discoverability.mjs` only when changing the checker.\n\n## Pitfalls\n\n- Question headings everywhere: use them only where they read naturally (concept pages, FAQs,\n  comparisons, blog), never on reference pages or tutorial steps.\n- Padding to a word count: there is no minimum length; a complete page is done.\n- Apex `https:\u002F\u002Fcratis.io\u002F` links: the docs host is `https:\u002F\u002Fwww.cratis.io`.\n- A description that repeats the title or a sibling page's description.\n",{"name":5,"license":14,"description":7},"main","45728854e223fd51b203724ca0e5be9c8f93a5a4",".cratis\u002Fai\u002Fskills\u002Fcratis-discoverability","https:\u002F\u002Fgithub.com\u002FCratis\u002FFundamentals.Go","https:\u002F\u002Fwww.cratis.io\u002Ffundamentals\u002Fgo\u002F","https:\u002F\u002Fgithub.com\u002FCratis","https:\u002F\u002Fwww.cratis.io","Open-source (MIT) event sourcing and CQRS for .NET and beyond: Chronicle, Arc, Components and Screenplay.","2026-11-14 15:52:19",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add Cratis\u002FFundamentals.Go --skill cratis-discoverability",{"tool":39,"command":40},"bunx","bunx skills add Cratis\u002FFundamentals.Go --skill cratis-discoverability",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Cratis\u002FFundamentals.Go --skill cratis-discoverability","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCratis\u002FFundamentals.Go\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fcratis-discoverability\u002FSKILL.md",true,[47,51,57,61,65,69,73],{"path":48,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":15},"LICENSE","许可证",201,{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fentities.md","REFERENCE","参考文档",4434,"https:\u002F\u002Fgithub.com\u002FCratis\u002FFundamentals.Go\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fcratis-discoverability\u002Freferences\u002Fentities.md",{"path":58,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Ffacts-and-adoption.md",3577,"https:\u002F\u002Fgithub.com\u002FCratis\u002FFundamentals.Go\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fcratis-discoverability\u002Freferences\u002Ffacts-and-adoption.md",{"path":62,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fpackage-metadata.md",3742,"https:\u002F\u002Fgithub.com\u002FCratis\u002FFundamentals.Go\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fcratis-discoverability\u002Freferences\u002Fpackage-metadata.md",{"path":66,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fpage-checklist.md",5857,"https:\u002F\u002Fgithub.com\u002FCratis\u002FFundamentals.Go\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fcratis-discoverability\u002Freferences\u002Fpage-checklist.md",{"path":70,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fstructured-data.md",3385,"https:\u002F\u002Fgithub.com\u002FCratis\u002FFundamentals.Go\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fcratis-discoverability\u002Freferences\u002Fstructured-data.md",{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"scripts\u002Fverify-discoverability.mjs","SCRIPT","脚本",6129,"https:\u002F\u002Fgithub.com\u002FCratis\u002FFundamentals.Go\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fcratis-discoverability\u002Fscripts\u002Fverify-discoverability.mjs",[80,88,96,104,113,120],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":84,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7DNCY3BCGY3MC5BFJ9S59BF","spf13-go","Review Go library APIs, package boundaries, tests, iterators and standard-library choices. Load for broad design or idiom reviews after the repository-owned Go skills.","https:\u002F\u002Fgithub.com\u002FCratis\u002FFundamentals.Go\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fspf13-go\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FCratis\u002FFundamentals.Go\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fspf13-go\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7DNCSQQH7GQ03ZETFX9XHAS","samber-golang-error-handling","Review Go error creation, wrapping, inspection and logging boundaries. Load when changing caller-visible failures after go-errors-and-context.","https:\u002F\u002Fgithub.com\u002FCratis\u002FFundamentals.Go\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fsamber-golang-error-handling\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FCratis\u002FFundamentals.Go\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fsamber-golang-error-handling\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":100,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M7DNCM4ZC15SSDA5FAAHN5S0","samber-golang-context","Design Go context propagation, cancellation, deadlines and request metadata. Load for operation-lifetime changes or context-related leaks after go-errors-and-context.","https:\u002F\u002Fgithub.com\u002FCratis\u002FFundamentals.Go\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fsamber-golang-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FCratis\u002FFundamentals.Go\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fsamber-golang-context\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":108,"licenseFileUrl":109,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":19},"01M7DNCGNSMHK640AK1R3J0CPD","jetbrains-go-modern-guidelines","Choose version-compatible modern Go syntax and standard-library APIs. Load when modernizing touched Go code after reading go.mod and build constraints.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FCratis\u002FFundamentals.Go\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fjetbrains-go-modern-guidelines\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FCratis\u002FFundamentals.Go\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fjetbrains-go-modern-guidelines\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"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":19},"01M7DNCBYSD6FPAPWM6PPSJR96","go-testing","Write and review Go unit, contract, transport, race, fuzz, and deterministic concurrency tests. Use for new behavior, bug fixes, flaky tests, and public API parity evidence.","https:\u002F\u002Fgithub.com\u002FCratis\u002FFundamentals.Go\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fgo-testing\u002FSKILL.md",[],[],{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":19},"01M7DNC7ES2RD6WGKC94KMMXTD","go-release-modules","Review Go module dependencies, minimum versions, compatibility, semantic labels, release-action tags, and proxy discoverability. Use for release preparation, retractions, and major-version migration planning.","https:\u002F\u002Fgithub.com\u002FCratis\u002FFundamentals.Go\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fgo-release-modules\u002FSKILL.md",[],[]]