[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75MK89N6DVEF08J54JS5QH6":3,"skill-same:01M75MK89N6DVEF08J54JS5QH6":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},"01M75MK89N6DVEF08J54JS5QH6","lean-on-oss-standards",null,"Use when choosing implementation patterns for observability, runtime configuration, API typing, CI, auth, or infrastructure. Biases toward proven open standards before custom machinery.","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\u002Flean-on-oss-standards\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: lean-on-oss-standards\ndescription: Use when choosing implementation patterns for observability, runtime configuration, API typing, CI, auth, or infrastructure. Biases toward proven open standards before custom machinery.\n---\n\n# Lean On OSS Standards\n\nBefore building custom machinery, reach for the battle-tested open standard that\nalready solves the problem. Most cross-cutting concerns — how a service emits\ntelemetry, flips a flag at runtime, types an API, gates CI — have a standard the\necosystem has already hardened. Adopt it; spend your invention budget on the\ndomain logic that is actually yours.\n\n## The test\n\nFor any infrastructure-shaped decision, ask: *is there a proven open standard for\nthis exact concern?*\n\n- **Yes** → adopt it, even if it is slightly heavier than a hand-rolled version\n  today. You inherit its tooling, docs, integrations, and bug fixes.\n- **No, but the repo already has a strong local pattern** → follow the local\n  pattern; consistency beats a second standard.\n- **Genuinely no standard** → only then build, and keep the surface small so a\n  standard can replace it later.\n\n## Examples of the standards to reach for\n\nThese are illustrations of the discipline, not the point:\n\n- Observability: OpenTelemetry traces, metrics, and structured logs.\n- Runtime knobs: OpenFeature or the repository's existing flag client.\n- API typing: shared types and typed RPC clients.\n- Infrastructure: declarative IaC, package-native charts, GitOps, managed secret\n  stores, keyless workload identity.\n- CI\u002Ftest policy: ecosystem-native test tools plus required status checks.\n\n## Anti-pattern: bespoke reinvention\n\nThe smell is a homegrown component that re-implements what a standard already\ndoes — a custom metrics wire format instead of OTel, a hand-rolled flag service\ninstead of OpenFeature, a one-off secret loader instead of a managed store. It\ncosts nothing the day you write it and everything later: no ecosystem, no\nintegrations, and a maintenance burden only you carry. If you find yourself\ndesigning protocol-level plumbing for a solved concern, stop and adopt the\nstandard.\n","# Lean On OSS Standards\n\nBefore building custom machinery, reach for the battle-tested open standard that\nalready solves the problem. Most cross-cutting concerns — how a service emits\ntelemetry, flips a flag at runtime, types an API, gates CI — have a standard the\necosystem has already hardened. Adopt it; spend your invention budget on the\ndomain logic that is actually yours.\n\n## The test\n\nFor any infrastructure-shaped decision, ask: *is there a proven open standard for\nthis exact concern?*\n\n- **Yes** → adopt it, even if it is slightly heavier than a hand-rolled version\n  today. You inherit its tooling, docs, integrations, and bug fixes.\n- **No, but the repo already has a strong local pattern** → follow the local\n  pattern; consistency beats a second standard.\n- **Genuinely no standard** → only then build, and keep the surface small so a\n  standard can replace it later.\n\n## Examples of the standards to reach for\n\nThese are illustrations of the discipline, not the point:\n\n- Observability: OpenTelemetry traces, metrics, and structured logs.\n- Runtime knobs: OpenFeature or the repository's existing flag client.\n- API typing: shared types and typed RPC clients.\n- Infrastructure: declarative IaC, package-native charts, GitOps, managed secret\n  stores, keyless workload identity.\n- CI\u002Ftest policy: ecosystem-native test tools plus required status checks.\n\n## Anti-pattern: bespoke reinvention\n\nThe smell is a homegrown component that re-implements what a standard already\ndoes — a custom metrics wire format instead of OTel, a hand-rolled flag service\ninstead of OpenFeature, a one-off secret loader instead of a managed store. It\ncosts nothing the day you write it and everything later: no ecosystem, no\nintegrations, and a maintenance burden only you carry. If you find yourself\ndesigning protocol-level plumbing for a solved concern, stop and adopt the\nstandard.\n",{"name":5,"description":7},"main","54007b08157feb09e5bb9d7ff5ce4ddd21625dbf","skills\u002Flean-on-oss-standards",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 lean-on-oss-standards",{"tool":37,"command":38},"bunx","bunx skills add selamy-labs\u002Fagent-skills --skill lean-on-oss-standards",{"tool":40,"command":41},"pnpm","pnpm dlx skills add selamy-labs\u002Fagent-skills --skill lean-on-oss-standards","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fselamy-labs\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Flean-on-oss-standards\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",[],[]]