[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BJZ1TPYWNMXD1ED10KFD97":3,"skill-same:01M7BJZ1TPYWNMXD1ED10KFD97":73},{"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":46,"commitSha":47,"skillDirectory":48,"forksCount":13,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":6,"updatedAt":52,"install":53,"resources":66},"01M7BJZ1TPYWNMXD1ED10KFD97","design-md",null,"Author\u002Fvalidate\u002Fexport Google's DESIGN.md token spec files.","darkmatter\u002Fhermes","darkmatter","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F17834193?v=4","01M7BHSAW99WRAMTSSHNHX73V0","01M7BHSAXDR4PY4NA2DY5PN6W8",0,"MIT","https:\u002F\u002Fgithub.com\u002Fdarkmatter\u002Fhermes\u002Fblob\u002Fmain\u002Fprofiles\u002Fdevbox\u002Fskills\u002Fcreative\u002Fdesign-md\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: design-md\ndescription: Author\u002Fvalidate\u002Fexport Google's DESIGN.md token spec files.\nversion: 1.1.0\nauthor: Hermes Agent\nlicense: MIT\nplatforms: [linux, macos, windows]\nmetadata:\n  hermes:\n    tags: [design, design-system, tokens, ui, accessibility, wcag, tailwind, dtcg, google]\n    related_skills: [popular-web-designs, claude-design, excalidraw, architecture-diagram]\n---\n\n# DESIGN.md Skill\n\nDESIGN.md is Google's open spec (Apache-2.0, `google-labs-code\u002Fdesign.md`) for\ndescribing a visual identity to coding agents. One file combines:\n\n- **YAML front matter** — machine-readable design tokens (normative values)\n- **Markdown body** — human-readable rationale, organized into canonical sections\n\nTokens give exact values. Prose tells agents *why* those values exist and how to\napply them. The CLI (`npx @google\u002Fdesign.md`) lints structure + WCAG contrast,\ndiffs versions for regressions, and exports to Tailwind or W3C DTCG JSON.\n\n## When to use this skill\n\n- User asks for a DESIGN.md file, design tokens, or a design system spec\n- User wants consistent UI\u002Fbrand across multiple projects or tools\n- User pastes an existing DESIGN.md and asks to lint, diff, export, or extend it\n- User asks to port a style guide into a format agents can consume\n- User wants contrast \u002F WCAG accessibility validation on their color palette\n\nFor purely visual inspiration or layout examples, use `popular-web-designs`\ninstead. For *process and taste* when designing a one-off HTML artifact\nfrom scratch (prototype, deck, landing page, component lab), use\n`claude-design`. This skill is for the *formal spec file* itself.\n\n## File anatomy\n\n```md\n---\nversion: alpha\nname: Heritage\ndescription: Architectural minimalism meets journalistic gravitas.\ncolors:\n  primary: \"#1A1C1E\"\n  secondary: \"#6C7278\"\n  tertiary: \"#B8422E\"\n  neutral: \"#F7F5F2\"\ntypography:\n  h1:\n    fontFamily: Public Sans\n    fontSize: 3rem\n    fontWeight: 700\n    lineHeight: 1.1\n    letterSpacing: \"-0.02em\"\n  body-md:\n    fontFamily: Public Sans\n    fontSize: 1rem\nrounded:\n  sm: 4px\n  md: 8px\n  lg: 16px\nspacing:\n  sm: 8px\n  md: 16px\n  lg: 24px\ncomponents:\n  button-primary:\n    backgroundColor: \"{colors.tertiary}\"\n    textColor: \"#FFFFFF\"\n    rounded: \"{rounded.sm}\"\n    padding: 12px\n  button-primary-hover:\n    backgroundColor: \"{colors.primary}\"\n---\n\n## Overview\n\nArchitectural Minimalism meets Journalistic Gravitas...\n\n## Colors\n\n- **Primary (#1A1C1E):** Deep ink for headlines and core text.\n- **Tertiary (#B8422E):** \"Boston Clay\" — the sole driver for interaction.\n\n## Typography\n\nPublic Sans for everything except small all-caps labels...\n\n## Components\n\n`button-primary` is the only high-emphasis action on a page...\n```\n\n## Token types\n\n| Type | Format | Example |\n|------|--------|---------|\n| Color | any CSS color (hex, `rgb()`, `oklch()`, named) | `\"#1A1C1E\"`, `\"oklch(62% 0.18 250)\"` |\n| Dimension | number + unit (`px`, `em`, `rem`) | `48px`, `-0.02em` |\n| Token reference | `{path.to.token}` | `{colors.primary}` |\n| Typography | object with `fontFamily`, `fontSize`, `fontWeight`, `lineHeight`, `letterSpacing`, `fontFeature`, `fontVariation` | see above |\n\nComponent property whitelist: `backgroundColor`, `textColor`, `typography`,\n`rounded`, `padding`, `size`, `height`, `width`. Variants (hover, active,\npressed) are **separate component entries** with related key names\n(`button-primary-hover`), not nested.\n\n## Canonical section order\n\nSections are optional, but present ones should appear in this order. The\nlinter flags out-of-order sections (`section-order`, warning) and duplicate\nheadings — consumers per the spec reject duplicates, so fix both before\nreturning the file.\n\n1. Overview (alias: Brand & Style)\n2. Colors\n3. Typography\n4. Layout (alias: Layout & Spacing)\n5. Elevation & Depth (alias: Elevation)\n6. Shapes\n7. Components\n8. Do's and Don'ts\n\nUnknown sections are preserved, not errored. Unknown token names are accepted\nif the value type is valid. Unknown component properties produce a warning.\n\n## Workflow: authoring a new DESIGN.md\n\n1. **Ask the user** (or infer) the brand tone, accent color, and typography\n   direction. If they provided a site, image, or vibe, translate it to the\n   token shape above.\n2. **Write `DESIGN.md`** in their project root using `write_file`. Always\n   include `name:` and `colors:`; other sections optional but encouraged.\n3. **Use token references** (`{colors.primary}`) in the `components:` section\n   instead of re-typing hex values. Keeps the palette single-source.\n4. **Lint it** (see below). Fix any broken references or WCAG failures\n   before returning.\n5. **If the user has an existing project**, also write Tailwind or DTCG\n   exports next to the file (`tailwind.theme.json`, `tokens.json`).\n\n## Workflow: lint \u002F diff \u002F export\n\nThe CLI is `@google\u002Fdesign.md` (Node). Use `npx` — no global install needed.\n\n```bash\n# Validate structure + token references + WCAG contrast\nnpx -y @google\u002Fdesign.md lint DESIGN.md\n\n# Compare two versions, fail on regression (exit 1 = regression)\nnpx -y @google\u002Fdesign.md diff DESIGN.md DESIGN-v2.md\n\n# Export to Tailwind v3 theme JSON (`tailwind` is a back-compat alias)\nnpx -y @google\u002Fdesign.md export --format json-tailwind DESIGN.md > tailwind.theme.json\n\n# Export to a Tailwind v4 CSS @theme block (--color-*, --text-*, --radius-*, ...)\nnpx -y @google\u002Fdesign.md export --format css-tailwind DESIGN.md > theme.css\n\n# Export to W3C DTCG (Design Tokens Format Module) JSON\nnpx -y @google\u002Fdesign.md export --format dtcg DESIGN.md > tokens.json\n\n# Print the spec itself — useful when injecting into an agent prompt\nnpx -y @google\u002Fdesign.md spec --rules-only --format json\n```\n\nAll commands accept `-` for stdin. `lint` returns exit 1 on errors (warnings\nalone exit 0). `export` exits 0 on a successful export regardless of lint\nfindings in the source — run `lint` separately to gate on those. Output is\nJSON by default; parse it if you need to report findings structurally.\n\nOn Windows, the `design.md` bin name can collide with the `.md` file\nassociation (silent no-op or the file opens in an editor). Use the dot-free\nalias: `npx -y -p @google\u002Fdesign.md designmd lint DESIGN.md`.\n\n### Lint rule reference (the 9 rules, as of CLI 0.3.0)\n\n- `broken-ref` (error) — `{colors.missing}` points at a non-existent token\n- `contrast-ratio` (warning) — component `textColor` vs `backgroundColor`\n  below WCAG AA (4.5:1)\n- `missing-primary` (warning) — colors defined but no `primary` token\n- `missing-typography` (warning) — colors defined but no typography tokens\n- `orphaned-tokens` (warning) — color tokens never referenced by a component\n- `section-order` (warning) — sections out of the canonical order\n- `unknown-key` (warning) — top-level YAML key that looks like a typo of a\n  schema key (`colours:` → `colors:`); custom extension keys stay silent\n- `token-summary`, `missing-sections` (info) — counts and absent optional\n  sections\n\nWhen the user cares about accessibility, call this out explicitly in your\nsummary — WCAG findings are the most load-bearing reason to use the CLI.\n\n## Pitfalls\n\n- **Don't nest component variants.** `button-primary.hover` is wrong;\n  `button-primary-hover` as a sibling key is right.\n- **Hex colors must be quoted strings.** YAML will otherwise choke on `#` or\n  truncate values like `#1A1C1E` oddly.\n- **Negative dimensions need quotes too.** `letterSpacing: -0.02em` parses as\n  a YAML flow — write `letterSpacing: \"-0.02em\"`.\n- **Section order matters even though the linter only warns.** If the user\n  gives you prose in a random order, reorder it to match the canonical list\n  before saving — spec-compliant consumers expect it.\n- **Typography sub-property typos are silently dropped.** As of CLI 0.3.0 a\n  typo like `fontwight:` produces no finding and the value vanishes from\n  exports — double-check sub-property names against the schema\n  (`fontFamily`, `fontSize`, `fontWeight`, `lineHeight`, `letterSpacing`,\n  `fontFeature`, `fontVariation`).\n- **`version: alpha` is the current spec version** (as of Jul 2026, CLI\n  0.3.0). The spec is marked alpha — watch for breaking changes.\n- **Token references resolve by dotted path.** `{colors.primary}` works;\n  `{primary}` does not.\n\n## Spec source of truth\n\n- Repo: https:\u002F\u002Fgithub.com\u002Fgoogle-labs-code\u002Fdesign.md (Apache-2.0)\n- CLI: `@google\u002Fdesign.md` on npm\n- License of generated DESIGN.md files: whatever the user's project uses;\n  the spec itself is Apache-2.0.\n","# DESIGN.md Skill\n\nDESIGN.md is Google's open spec (Apache-2.0, `google-labs-code\u002Fdesign.md`) for\ndescribing a visual identity to coding agents. One file combines:\n\n- **YAML front matter** — machine-readable design tokens (normative values)\n- **Markdown body** — human-readable rationale, organized into canonical sections\n\nTokens give exact values. Prose tells agents *why* those values exist and how to\napply them. The CLI (`npx @google\u002Fdesign.md`) lints structure + WCAG contrast,\ndiffs versions for regressions, and exports to Tailwind or W3C DTCG JSON.\n\n## When to use this skill\n\n- User asks for a DESIGN.md file, design tokens, or a design system spec\n- User wants consistent UI\u002Fbrand across multiple projects or tools\n- User pastes an existing DESIGN.md and asks to lint, diff, export, or extend it\n- User asks to port a style guide into a format agents can consume\n- User wants contrast \u002F WCAG accessibility validation on their color palette\n\nFor purely visual inspiration or layout examples, use `popular-web-designs`\ninstead. For *process and taste* when designing a one-off HTML artifact\nfrom scratch (prototype, deck, landing page, component lab), use\n`claude-design`. This skill is for the *formal spec file* itself.\n\n## File anatomy\n\n```md\n---\nversion: alpha\nname: Heritage\ndescription: Architectural minimalism meets journalistic gravitas.\ncolors:\n  primary: \"#1A1C1E\"\n  secondary: \"#6C7278\"\n  tertiary: \"#B8422E\"\n  neutral: \"#F7F5F2\"\ntypography:\n  h1:\n    fontFamily: Public Sans\n    fontSize: 3rem\n    fontWeight: 700\n    lineHeight: 1.1\n    letterSpacing: \"-0.02em\"\n  body-md:\n    fontFamily: Public Sans\n    fontSize: 1rem\nrounded:\n  sm: 4px\n  md: 8px\n  lg: 16px\nspacing:\n  sm: 8px\n  md: 16px\n  lg: 24px\ncomponents:\n  button-primary:\n    backgroundColor: \"{colors.tertiary}\"\n    textColor: \"#FFFFFF\"\n    rounded: \"{rounded.sm}\"\n    padding: 12px\n  button-primary-hover:\n    backgroundColor: \"{colors.primary}\"\n---\n\n## Overview\n\nArchitectural Minimalism meets Journalistic Gravitas...\n\n## Colors\n\n- **Primary (#1A1C1E):** Deep ink for headlines and core text.\n- **Tertiary (#B8422E):** \"Boston Clay\" — the sole driver for interaction.\n\n## Typography\n\nPublic Sans for everything except small all-caps labels...\n\n## Components\n\n`button-primary` is the only high-emphasis action on a page...\n```\n\n## Token types\n\n| Type | Format | Example |\n|------|--------|---------|\n| Color | any CSS color (hex, `rgb()`, `oklch()`, named) | `\"#1A1C1E\"`, `\"oklch(62% 0.18 250)\"` |\n| Dimension | number + unit (`px`, `em`, `rem`) | `48px`, `-0.02em` |\n| Token reference | `{path.to.token}` | `{colors.primary}` |\n| Typography | object with `fontFamily`, `fontSize`, `fontWeight`, `lineHeight`, `letterSpacing`, `fontFeature`, `fontVariation` | see above |\n\nComponent property whitelist: `backgroundColor`, `textColor`, `typography`,\n`rounded`, `padding`, `size`, `height`, `width`. Variants (hover, active,\npressed) are **separate component entries** with related key names\n(`button-primary-hover`), not nested.\n\n## Canonical section order\n\nSections are optional, but present ones should appear in this order. The\nlinter flags out-of-order sections (`section-order`, warning) and duplicate\nheadings — consumers per the spec reject duplicates, so fix both before\nreturning the file.\n\n1. Overview (alias: Brand & Style)\n2. Colors\n3. Typography\n4. Layout (alias: Layout & Spacing)\n5. Elevation & Depth (alias: Elevation)\n6. Shapes\n7. Components\n8. Do's and Don'ts\n\nUnknown sections are preserved, not errored. Unknown token names are accepted\nif the value type is valid. Unknown component properties produce a warning.\n\n## Workflow: authoring a new DESIGN.md\n\n1. **Ask the user** (or infer) the brand tone, accent color, and typography\n   direction. If they provided a site, image, or vibe, translate it to the\n   token shape above.\n2. **Write `DESIGN.md`** in their project root using `write_file`. Always\n   include `name:` and `colors:`; other sections optional but encouraged.\n3. **Use token references** (`{colors.primary}`) in the `components:` section\n   instead of re-typing hex values. Keeps the palette single-source.\n4. **Lint it** (see below). Fix any broken references or WCAG failures\n   before returning.\n5. **If the user has an existing project**, also write Tailwind or DTCG\n   exports next to the file (`tailwind.theme.json`, `tokens.json`).\n\n## Workflow: lint \u002F diff \u002F export\n\nThe CLI is `@google\u002Fdesign.md` (Node). Use `npx` — no global install needed.\n\n```bash\n# Validate structure + token references + WCAG contrast\nnpx -y @google\u002Fdesign.md lint DESIGN.md\n\n# Compare two versions, fail on regression (exit 1 = regression)\nnpx -y @google\u002Fdesign.md diff DESIGN.md DESIGN-v2.md\n\n# Export to Tailwind v3 theme JSON (`tailwind` is a back-compat alias)\nnpx -y @google\u002Fdesign.md export --format json-tailwind DESIGN.md > tailwind.theme.json\n\n# Export to a Tailwind v4 CSS @theme block (--color-*, --text-*, --radius-*, ...)\nnpx -y @google\u002Fdesign.md export --format css-tailwind DESIGN.md > theme.css\n\n# Export to W3C DTCG (Design Tokens Format Module) JSON\nnpx -y @google\u002Fdesign.md export --format dtcg DESIGN.md > tokens.json\n\n# Print the spec itself — useful when injecting into an agent prompt\nnpx -y @google\u002Fdesign.md spec --rules-only --format json\n```\n\nAll commands accept `-` for stdin. `lint` returns exit 1 on errors (warnings\nalone exit 0). `export` exits 0 on a successful export regardless of lint\nfindings in the source — run `lint` separately to gate on those. Output is\nJSON by default; parse it if you need to report findings structurally.\n\nOn Windows, the `design.md` bin name can collide with the `.md` file\nassociation (silent no-op or the file opens in an editor). Use the dot-free\nalias: `npx -y -p @google\u002Fdesign.md designmd lint DESIGN.md`.\n\n### Lint rule reference (the 9 rules, as of CLI 0.3.0)\n\n- `broken-ref` (error) — `{colors.missing}` points at a non-existent token\n- `contrast-ratio` (warning) — component `textColor` vs `backgroundColor`\n  below WCAG AA (4.5:1)\n- `missing-primary` (warning) — colors defined but no `primary` token\n- `missing-typography` (warning) — colors defined but no typography tokens\n- `orphaned-tokens` (warning) — color tokens never referenced by a component\n- `section-order` (warning) — sections out of the canonical order\n- `unknown-key` (warning) — top-level YAML key that looks like a typo of a\n  schema key (`colours:` → `colors:`); custom extension keys stay silent\n- `token-summary`, `missing-sections` (info) — counts and absent optional\n  sections\n\nWhen the user cares about accessibility, call this out explicitly in your\nsummary — WCAG findings are the most load-bearing reason to use the CLI.\n\n## Pitfalls\n\n- **Don't nest component variants.** `button-primary.hover` is wrong;\n  `button-primary-hover` as a sibling key is right.\n- **Hex colors must be quoted strings.** YAML will otherwise choke on `#` or\n  truncate values like `#1A1C1E` oddly.\n- **Negative dimensions need quotes too.** `letterSpacing: -0.02em` parses as\n  a YAML flow — write `letterSpacing: \"-0.02em\"`.\n- **Section order matters even though the linter only warns.** If the user\n  gives you prose in a random order, reorder it to match the canonical list\n  before saving — spec-compliant consumers expect it.\n- **Typography sub-property typos are silently dropped.** As of CLI 0.3.0 a\n  typo like `fontwight:` produces no finding and the value vanishes from\n  exports — double-check sub-property names against the schema\n  (`fontFamily`, `fontSize`, `fontWeight`, `lineHeight`, `letterSpacing`,\n  `fontFeature`, `fontVariation`).\n- **`version: alpha` is the current spec version** (as of Jul 2026, CLI\n  0.3.0). The spec is marked alpha — watch for breaking changes.\n- **Token references resolve by dotted path.** `{colors.primary}` works;\n  `{primary}` does not.\n\n## Spec source of truth\n\n- Repo: https:\u002F\u002Fgithub.com\u002Fgoogle-labs-code\u002Fdesign.md (Apache-2.0)\n- CLI: `@google\u002Fdesign.md` on npm\n- License of generated DESIGN.md files: whatever the user's project uses;\n  the spec itself is Apache-2.0.\n",{"name":5,"author":23,"license":14,"version":24,"metadata":25,"platforms":42,"description":7},"Hermes Agent","1.1.0",{"hermes":26},{"tags":27,"related_skills":37},[28,29,30,31,32,33,34,35,36],"design","design-system","tokens","ui","accessibility","wcag","tailwind","dtcg","google",[38,39,40,41],"popular-web-designs","claude-design","excalidraw","architecture-diagram",[43,44,45],"linux","macos","windows","main","81189f70e1089f9b3a944ffc480e6887efd831b9","profiles\u002Fdevbox\u002Fskills\u002Fcreative\u002Fdesign-md","https:\u002F\u002Fgithub.com\u002Fdarkmatter\u002Fhermes","https:\u002F\u002Fgithub.com\u002Fdarkmatter","dm.sh","2026-09-14 08:11:52",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add darkmatter\u002Fhermes --skill design-md",{"tool":59,"command":60},"bunx","bunx skills add darkmatter\u002Fhermes --skill design-md",{"tool":62,"command":63},"pnpm","pnpm dlx skills add darkmatter\u002Fhermes --skill design-md","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdarkmatter\u002Fhermes\u002Fblob\u002Fmain\u002Fprofiles\u002Fdevbox\u002Fskills\u002Fcreative\u002Fdesign-md\u002FSKILL.md",true,[67],{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"templates\u002Fstarter.md","REFERENCE","参考文档",2566,"https:\u002F\u002Fgithub.com\u002Fdarkmatter\u002Fhermes\u002Fblob\u002Fmain\u002Fprofiles\u002Fdevbox\u002Fskills\u002Fcreative\u002Fdesign-md\u002Ftemplates\u002Fstarter.md",[74,81,88,95,102,109],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M7BMC2PYBVXM6FQEZMBQZB4G","plan","Write a markdown plan to .hermes\u002Fplans\u002F; no execution.","https:\u002F\u002Fgithub.com\u002Fdarkmatter\u002Fhermes\u002Fblob\u002Fmain\u002Fskills\u002Fsoftware-development\u002Fplan\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M7BMBSEKDVQ09Z666RCWT7BR","monorepo-fleet-sync","Sync docs and configs when a Flue monorepo fleet changes.","https:\u002F\u002Fgithub.com\u002Fdarkmatter\u002Fhermes\u002Fblob\u002Fmain\u002Fskills\u002Fsoftware-development\u002Fmonorepo-fleet-sync\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":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":18},"01M7BMBNWFJT2TJZ2AKA64GEV9","inspecting-hermes-desktop-dom","Read the live Hermes desktop DOM\u002FCSS over CDP.","https:\u002F\u002Fgithub.com\u002Fdarkmatter\u002Fhermes\u002Fblob\u002Fmain\u002Fskills\u002Fsoftware-development\u002Finspecting-hermes-desktop-dom\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":18},"01M7BMAZM4VJ97K7JD0FDN58M8","grounded-citations","Ground answers and documents in cited, verifiable sources.","https:\u002F\u002Fgithub.com\u002Fdarkmatter\u002Fhermes\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fgrounded-citations\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":18},"01M7BMATPEDZ4BPP67Y4ZS0BMM","competitor-news-monitor","Watch named companies for material news; cited digests.","https:\u002F\u002Fgithub.com\u002Fdarkmatter\u002Fhermes\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fcompetitor-news-monitor\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":18},"01M7BMAQZV7YFA2SFPT7HCVCTX","blocked-page-recovery","Recover blocked\u002Fpaywalled\u002FWAF'd pages via fallbacks.","https:\u002F\u002Fgithub.com\u002Fdarkmatter\u002Fhermes\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fblocked-page-recovery\u002FSKILL.md",[],[]]