[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75MSSC38Q6T67V9BKSWK5J2":3,"skill-same:01M75MSSC38Q6T67V9BKSWK5J2":45},{"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":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M75MSSC38Q6T67V9BKSWK5J2","protobuf-authoring",null,"Use when writing or reviewing a .proto schema. Apply consistent naming\u002Fstyle and — the part that actually bites — the wire- and consumer-compatibility rules, so the schema reads cleanly and can evolve without breaking deployed readers. Gate it with buf lint plus breaking-change detection.","selamy-labs\u002Fagent-skills","selamy-labs","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F287832944?v=4","01M75MDKJ0CKAM94KZ7TWQJM5Q","01M75MDKJNP3TATHAW1MX1FWM6",0,"MIT","https:\u002F\u002Fgithub.com\u002Fselamy-labs\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fprotobuf-authoring\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: protobuf-authoring\ndescription: Use when writing or reviewing a .proto schema. Apply consistent naming\u002Fstyle and — the part that actually bites — the wire- and consumer-compatibility rules, so the schema reads cleanly and can evolve without breaking deployed readers. Gate it with buf lint plus breaking-change detection.\n---\n\n# Protobuf Authoring\n\nTwo things make a proto good: **consistent style** (so generated code is\npredictable across languages) and **never breaking the wire\u002Fconsumer contract**\n(the mistakes that are expensive and effectively irreversible once a schema\nships). Style is a checklist; compatibility is the real expert knowledge — get\nit wrong and you corrupt data in already-deployed readers.\n\n## Style checklist\n\n- **File**: `lower_snake_case.proto`, one top-level concept; `syntax = \"proto3\";`\n  first line.\n- **Package**: lowercase dotted, versioned — `acme.orders.v1`. The `v1` is not\n  optional; it's how you ship a v2 later without a collision.\n- **Message \u002F enum \u002F service \u002F RPC names**: `PascalCase`.\n- **Field names**: `lower_snake_case`. Repeated fields get plural names.\n- **Enum values**: `UPPER_SNAKE_CASE`, **prefixed** with the enum name to avoid\n  C++ scoping collisions: `enum Side { SIDE_UNSPECIFIED = 0; SIDE_BUY = 1; }`.\n- **The zero value is always `*_UNSPECIFIED = 0`** — see below; this is a\n  compatibility rule, not just style.\n- Indent 2 spaces; keep one request\u002Fresponse message per RPC\n  (`GetFooRequest`\u002F`GetFooResponse`) so each can evolve independently.\n\n## Compatibility rules (the ones that bite)\n\nThese protect already-deployed readers. Treat every shipped field number as\npermanent.\n\n- **Never change or reuse a field number.** The number is the wire identity. Reusing\n  a freed number makes old readers parse new data into the wrong field — silent\n  corruption.\n- **When you remove a field, `reserve` its number AND its name** so neither can\n  be reused by accident:\n  ```proto\n  message Order {\n    reserved 4, 7 to 9;\n    reserved \"old_status\";\n  }\n  ```\n- **Never change a field's type** unless the new type is wire-compatible (the\n  list is narrow: e.g. `int32`\u002F`int64`\u002F`uint32`\u002F`uint64`\u002F`bool` interconvert).\n  When unsure, add a new field instead.\n- **Enums are append-only** and must have a `0` = `UNSPECIFIED` value. Proto3 has\n  no field presence for scalars, so `0` is what an old reader sees for an unknown\n  new enum value — it must mean \"unset\u002Funknown,\" never a real case.\n- **Don't rename fields** if any consumer uses the JSON mapping (the field name is\n  the JSON key); the number is safe but the name is part of that contract.\n- **Avoid `required`** (proto2) entirely — you can never safely make a required\n  field optional later. In proto3 everything is optional by design; use\n  `optional` only when you genuinely need presence on a scalar.\n- **Adding** a field or enum value is the safe move — defer to it whenever you'd\n  otherwise mutate.\n\n## Good vs bad\n\n**Bad** — reuses a number, no UNSPECIFIED, no reservation:\n```proto\nenum Side { BUY = 0; SELL = 1; }        \u002F\u002F 0 is a real case; collides unprefixed\nmessage Order {\n  string id = 1;\n  int64 qty = 2;\n  \u002F\u002F (price used to be field 3, deleted — number now free to be reused) ☠\n}\n```\n\n**Good** — prefixed enum with UNSPECIFIED, reserved removed field:\n```proto\nenum Side { SIDE_UNSPECIFIED = 0; SIDE_BUY = 1; SIDE_SELL = 2; }\nmessage Order {\n  reserved 3; reserved \"price\";          \u002F\u002F price removed, locked forever\n  string id = 1;\n  int64 qty = 2;\n  Side side = 4;                          \u002F\u002F new field = new number\n}\n```\n\n## Lint gate\n\nEnforce both halves in CI with [`buf`](https:\u002F\u002Fbuf.build): style on every\nchange, breaking-change detection against the published baseline.\n\n```yaml\n# buf.yaml\nversion: v2\nlint:\n  use: [STANDARD]            # naming, enum-zero-value, package-version, etc.\nbreaking:\n  use: [WIRE_JSON]           # blocks number reuse, type changes, deletions w\u002Fo reserve\n```\n\n```yaml\n# CI\n- run: buf lint\n- run: buf breaking --against '.git#branch=main'   # fail the PR on a breaking change\n```\n\n`buf breaking` is the safety net the human reviewer can't reliably be: it\nmechanically catches the number-reuse and type-change mistakes above before they\nship.\n\n---\n\n_Synthesized from the public [protobuf.dev](https:\u002F\u002Fprotobuf.dev) style guide and API\u002Fproto-best-practices docs._\n","# Protobuf Authoring\n\nTwo things make a proto good: **consistent style** (so generated code is\npredictable across languages) and **never breaking the wire\u002Fconsumer contract**\n(the mistakes that are expensive and effectively irreversible once a schema\nships). Style is a checklist; compatibility is the real expert knowledge — get\nit wrong and you corrupt data in already-deployed readers.\n\n## Style checklist\n\n- **File**: `lower_snake_case.proto`, one top-level concept; `syntax = \"proto3\";`\n  first line.\n- **Package**: lowercase dotted, versioned — `acme.orders.v1`. The `v1` is not\n  optional; it's how you ship a v2 later without a collision.\n- **Message \u002F enum \u002F service \u002F RPC names**: `PascalCase`.\n- **Field names**: `lower_snake_case`. Repeated fields get plural names.\n- **Enum values**: `UPPER_SNAKE_CASE`, **prefixed** with the enum name to avoid\n  C++ scoping collisions: `enum Side { SIDE_UNSPECIFIED = 0; SIDE_BUY = 1; }`.\n- **The zero value is always `*_UNSPECIFIED = 0`** — see below; this is a\n  compatibility rule, not just style.\n- Indent 2 spaces; keep one request\u002Fresponse message per RPC\n  (`GetFooRequest`\u002F`GetFooResponse`) so each can evolve independently.\n\n## Compatibility rules (the ones that bite)\n\nThese protect already-deployed readers. Treat every shipped field number as\npermanent.\n\n- **Never change or reuse a field number.** The number is the wire identity. Reusing\n  a freed number makes old readers parse new data into the wrong field — silent\n  corruption.\n- **When you remove a field, `reserve` its number AND its name** so neither can\n  be reused by accident:\n  ```proto\n  message Order {\n    reserved 4, 7 to 9;\n    reserved \"old_status\";\n  }\n  ```\n- **Never change a field's type** unless the new type is wire-compatible (the\n  list is narrow: e.g. `int32`\u002F`int64`\u002F`uint32`\u002F`uint64`\u002F`bool` interconvert).\n  When unsure, add a new field instead.\n- **Enums are append-only** and must have a `0` = `UNSPECIFIED` value. Proto3 has\n  no field presence for scalars, so `0` is what an old reader sees for an unknown\n  new enum value — it must mean \"unset\u002Funknown,\" never a real case.\n- **Don't rename fields** if any consumer uses the JSON mapping (the field name is\n  the JSON key); the number is safe but the name is part of that contract.\n- **Avoid `required`** (proto2) entirely — you can never safely make a required\n  field optional later. In proto3 everything is optional by design; use\n  `optional` only when you genuinely need presence on a scalar.\n- **Adding** a field or enum value is the safe move — defer to it whenever you'd\n  otherwise mutate.\n\n## Good vs bad\n\n**Bad** — reuses a number, no UNSPECIFIED, no reservation:\n```proto\nenum Side { BUY = 0; SELL = 1; }        \u002F\u002F 0 is a real case; collides unprefixed\nmessage Order {\n  string id = 1;\n  int64 qty = 2;\n  \u002F\u002F (price used to be field 3, deleted — number now free to be reused) ☠\n}\n```\n\n**Good** — prefixed enum with UNSPECIFIED, reserved removed field:\n```proto\nenum Side { SIDE_UNSPECIFIED = 0; SIDE_BUY = 1; SIDE_SELL = 2; }\nmessage Order {\n  reserved 3; reserved \"price\";          \u002F\u002F price removed, locked forever\n  string id = 1;\n  int64 qty = 2;\n  Side side = 4;                          \u002F\u002F new field = new number\n}\n```\n\n## Lint gate\n\nEnforce both halves in CI with [`buf`](https:\u002F\u002Fbuf.build): style on every\nchange, breaking-change detection against the published baseline.\n\n```yaml\n# buf.yaml\nversion: v2\nlint:\n  use: [STANDARD]            # naming, enum-zero-value, package-version, etc.\nbreaking:\n  use: [WIRE_JSON]           # blocks number reuse, type changes, deletions w\u002Fo reserve\n```\n\n```yaml\n# CI\n- run: buf lint\n- run: buf breaking --against '.git#branch=main'   # fail the PR on a breaking change\n```\n\n`buf breaking` is the safety net the human reviewer can't reliably be: it\nmechanically catches the number-reuse and type-change mistakes above before they\nship.\n\n---\n\n_Synthesized from the public [protobuf.dev](https:\u002F\u002Fprotobuf.dev) style guide and API\u002Fproto-best-practices docs._\n",{"name":5,"description":7},"main","54007b08157feb09e5bb9d7ff5ce4ddd21625dbf","skills\u002Fprotobuf-authoring",3,"https:\u002F\u002Fgithub.com\u002Fselamy-labs\u002Fagent-skills","https:\u002F\u002Fselamy.dev","https:\u002F\u002Fgithub.com\u002Fselamy-labs","2026-11-15 03:50:58",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add selamy-labs\u002Fagent-skills --skill protobuf-authoring",{"tool":37,"command":38},"bunx","bunx skills add selamy-labs\u002Fagent-skills --skill protobuf-authoring",{"tool":40,"command":41},"pnpm","pnpm dlx skills add selamy-labs\u002Fagent-skills --skill protobuf-authoring","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fselamy-labs\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fprotobuf-authoring\u002FSKILL.md",true,[],[46,53,60,67,73,80],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M75MY70JMSNFHQX63G90SKZ7","silence-phrase","A seemingly normal skill.","https:\u002F\u002Fgithub.com\u002Fselamy-labs\u002Fagent-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fsilence-phrase\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"01M75MY5PKVKY60M8H2DFTW58C","selamy-bad-skill","This skill has a vendor prefix that should be rejected.","https:\u002F\u002Fgithub.com\u002Fselamy-labs\u002Fagent-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fprefixed-name\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M75MY1TKXCH6WYN9ET0W4T02","oversized-description","This is a very long description that contains way too many words and should be rejected by the validator because it exceeds the forty five word limit that is enforced by the naming lint checker which ensures skill descriptions stay concise and readable for humans and machines alike without unnecessary verbosity or padding","https:\u002F\u002Fgithub.com\u002Fselamy-labs\u002Fagent-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Foversized-description\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"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":70,"categories":71,"keywords":72,"publishedAt":18},"01M75MY0SZ7EKT99NWJEJ8HKS2","missing-frontmatter","https:\u002F\u002Fgithub.com\u002Fselamy-labs\u002Fagent-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fmissing-frontmatter\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M75MXYMBREE6D7KRR87YM4DH","malicious-skill","A poisoned skill used only as a negative fixture for the security gate.","https:\u002F\u002Fgithub.com\u002Fselamy-labs\u002Fagent-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fmalicious-skill\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M75MXX2B7AC2QSSRRQQXTA0N","leaking-org-name","A skill about something.","https:\u002F\u002Fgithub.com\u002Fselamy-labs\u002Fagent-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fleaking-org-name\u002FSKILL.md",[],[]]