[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7E7CYJSYYA39FGS9GSPH46N":3,"skill-same:01M7E7CYJSYYA39FGS9GSPH46N":129},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":14,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":6,"ownerDescription":41,"updatedAt":42,"install":43,"resources":56},"01M7E7CYJSYYA39FGS9GSPH46N","cncf-haproxy-technologies-member-reviewer",null,"Review HAProxy Technologies (member) using its official documentation and repository in the CNCF Members \u002F Silver category.","domehahn\u002Fskrun","domehahn","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F41511445?v=4","01M735R3R9KEBEJ6D5YYAE9A61","Dominik Hahn","01M7CDBG3E33XA789X08REJ55H",0,"MIT","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskrun\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcncf-haproxy-technologies-member-reviewer\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskrun\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcncf-haproxy-technologies-member-reviewer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"cncf-haproxy-technologies-member-reviewer\"\ndescription: \"Review HAProxy Technologies (member) using its official documentation and repository in the CNCF Members \u002F Silver category.\"\nversion: \"1.0.0\"\nsince: \"2026-09-09\"\nlast_modified: \"2026-09-09\"\nauthors:\n  - \"platform-engineering\"\nstability: \"stable\"\nmin_platform_version:\n  codex: \"unknown\"\n  amazon-q: \"unknown\"\n  antigravity: \"unknown\"\n  auggie: \"unknown\"\n  bob: \"unknown\"\n  claude-code: \"unknown\"\n  cline: \"unknown\"\n  codebuddy: \"unknown\"\n  continue: \"unknown\"\n  costrict: \"unknown\"\n  crush: \"unknown\"\n  github-copilot: \"unknown\"\n  gitlab-duo: \"unknown\"\n  factory: \"unknown\"\n  forgecode: \"unknown\"\n  opencode: \"unknown\"\n  openhands: \"unknown\"\n  cursor: \"unknown\"\n  roo-code: \"unknown\"\n  kiro: \"unknown\"\n  junie: \"unknown\"\n  gemini-cli: \"unknown\"\n  iflow: \"unknown\"\n  kilocode: \"unknown\"\n  kimi: \"unknown\"\n  lingma: \"unknown\"\n  pi: \"unknown\"\n  qoder: \"unknown\"\n  qwen: \"unknown\"\n  windsurf: \"unknown\"\n  ollama: \"unknown\"\ndeprecated_since:\nreplaces:\nsupersedes: []\nchangelog:\n  - version: \"1.0.0\"\n    date: \"2026-09-09\"\n    change: \"Initial generated production-ready SDLC \u002F DevSecOps skill\"\n---\n# Cncf Haproxy Technologies Member Reviewer\n\n## Purpose\n\nReview HAProxy Technologies (member) as an organization listed in the CNCF Landscape using current first-party evidence and explicit procurement, governance, security, portability, and operational criteria.\n\n## Goal and behavioral contract\n\nThe authoritative Goal and artifact references are defined in `descriptor.yaml`. Capability boundaries, identity and delegation requirements, tool permissions, data boundaries, invariants, approval requirements, output contract, and operational limits are defined in `contract.yaml`. MCP\u002FA2A trust boundaries and the reviewed execution closure live in `integrations\u002F` and `dependencies.yaml`; ASPS and assurance requirements live in `assurance.yaml`.\n\nTreat those declarations as mandatory execution constraints. `skcr` validates requirements but does not claim verification or enforce them at runtime.\n\n## When to use\n\n- The organization, its cloud-native products, support, partnership, procurement, outsourcing, or exit strategy is being assessed.\n- Claims about CNCF membership or capabilities need current verification.\n\n## Operating model\n\n1. Treat CNCF Landscape inclusion as classification metadata, not endorsement, certification, security assurance, or proof of product fitness.\n2. Verify current claims against the organization's first-party material and the official CNCF Landscape entry.\n3. Separate organization-level membership from the maturity or CNCF status of individual projects.\n\n## Spec-Driven Change Context\n\n- Treat repository specs, ADRs, runbooks, change proposals, design notes, and task files as durable context that outlives a chat session.\n- For non-trivial changes, prefer a checked-in change artifact or equivalent proposal\u002Fdesign\u002Ftasks record before implementation begins.\n- Capture requirement deltas explicitly: added, modified, removed, deprecated, or unchanged behavior.\n- Keep implementation tasks traceable to acceptance criteria, affected specs, validation commands, and owners.\n- During verification, compare the implementation against the proposal, design decisions, task checklist, and spec deltas.\n- After completion, sync or archive completed change artifacts so the repository's source of truth reflects the final behavior.\n- If the repository has no spec workflow yet, report the missing artifact and provide a minimal proposal\u002Fspec\u002Ftasks outline instead of relying on chat-only intent.\n\n## Skill-Specific Review Scope\n\n- CNCF classification: CNCF Members \u002F Silver\n- First-party source: https:\u002F\u002Fwww.haproxy.com\n- product scope, ownership, support, security, compliance, portability, commercial dependencies, concentration risk, and exit strategy\n\n## Skill-Specific Checklist\n\n- [ ] Confirm legal and product identity, current CNCF classification, offered services, support boundaries, regions, data handling, and shared responsibilities.\n- [ ] Check security documentation, incident handling, vulnerability disclosure, support SLAs, audit evidence, subcontractors, portability, and termination assistance.\n- [ ] Identify proprietary dependencies, lock-in, pricing or licensing constraints, migration paths, and operational ownership.\n- [ ] Trace HAProxy Technologies (member) inputs, outputs, identities, trust boundaries, external dependencies, and persistent state.\n- [ ] Check HAProxy Technologies (member) defaults, configuration precedence, environment separation, and drift from reviewed source.\n- [ ] Check HAProxy Technologies (member) least privilege, credential rotation, audit events, policy enforcement, and break-glass behavior.\n- [ ] Check HAProxy Technologies (member) resource ownership, cleanup, quotas, rate limits, timeouts, retries, and backpressure.\n- [ ] Check HAProxy Technologies (member) release notes, supported upgrade paths, schema or API compatibility, and rollback constraints.\n- [ ] Check HAProxy Technologies (member) dashboards, alerts, health signals, incident procedures, backup evidence, and recovery exercises.\n- [ ] Check HAProxy Technologies (member) license, maintenance state, vulnerability handling, provenance, signatures, and dependency pinning.\n\n## Decision Rules\n\n- Do not infer CNCF project status, certification, security, or endorsement from membership.\n- Do not make procurement or legal conclusions without the applicable current contract and accountable reviewers.\n- Require an exit path and evidence for material capability or compliance claims.\n- If HAProxy Technologies (member) identity, version, edition, or deployment model cannot be established, report the uncertainty before recommending a change.\n- If a HAProxy Technologies (member) change can affect availability, security boundaries, persistent data, or external consumers, require staged validation and explicit rollback criteria.\n\n## Finding Categories\n\n- Identity, scope, classification, or claim mismatch.\n- Security, compliance, support, responsibility, or incident-management gap.\n- Portability, concentration, licensing, cost, contract, or exit-strategy risk.\n- HAProxy Technologies (member) documentation, ownership, maintenance, licensing, provenance, or evidence gap.\n- HAProxy Technologies (member) integration, dependency, compatibility, migration, or decommissioning risk.\n\n## Severity Guidance\n\n- Critical: HAProxy Technologies (member) can enable broad compromise, destructive production mutation, tenant escape, secret exposure, or material data loss.\n- High: HAProxy Technologies (member) can cause exploitable access, sustained outage, corrupt state, unsafe upgrade, or loss of recovery capability.\n- Medium: HAProxy Technologies (member) has a bounded correctness, reliability, compatibility, observability, maintenance, or performance risk.\n- Low: HAProxy Technologies (member) needs documentation, classification, idiomatic configuration, or validation-evidence improvement.\n\n## DevSecOps Guardrails\n\n- Do not read secrets, `.env` files, private keys, production credentials, masked CI\u002FCD variables, database dumps, or sensitive logs unless explicitly required.\n- Do not push, deploy, publish, merge, or create releases unless explicitly asked.\n- Prefer merge requests, reviewable diffs, and auditable validation evidence.\n- Prefer least privilege, minimal changes, and explicit rollback notes.\n- Do not fabricate test results, repository state, commands, security findings, or validation outcomes.\n- Report assumptions, uncertainty, residual risk, and validation gaps clearly.\n\n## Output Requirements\n\n- State the Landscape snapshot classification and sources checked.\n- Return an evidence-backed capability and risk assessment with open questions, owners, and expiry dates.\n- Include a HAProxy Technologies (member) architecture and dependency summary with trust boundaries and persistent state.\n- Include HAProxy Technologies (member) validation commands or tests that are safe for the stated environment.\n- Include HAProxy Technologies (member) ownership, rollout, rollback, monitoring, and follow-up actions.\n\n## Acceptance Criteria\n\n- Membership is not presented as endorsement or project maturity.\n- Material claims, responsibilities, dependencies, and exit assumptions are traceable to current evidence.\n- HAProxy Technologies (member) identity, version, configuration, dependencies, and deployment assumptions are explicit.\n- HAProxy Technologies (member) failure, upgrade, rollback, observability, and recovery paths have proportionate evidence.\n- HAProxy Technologies (member) security boundaries, credentials, network exposure, data handling, and supply-chain risks are addressed.\n\n## Anti-Patterns\n\n- Equating a Landscape logo with CNCF certification or technical approval.\n- Inventing product features, contract terms, regions, certifications, or support commitments.\n- Assuming Landscape inclusion or popularity proves that HAProxy Technologies (member) is secure, supported, compatible, or suitable.\n- Using an unpinned latest version of HAProxy Technologies (member) as the basis for migration or production guidance.\n- Ignoring HAProxy Technologies (member) operational ownership, data lifecycle, upgrade constraints, rollback, and decommissioning.\n\n## Changelog\n\n### 1.0.0 - 2026-09-09\n\n- Initial generated production-ready SDLC \u002F DevSecOps skill.\n","# Cncf Haproxy Technologies Member Reviewer\n\n## Purpose\n\nReview HAProxy Technologies (member) as an organization listed in the CNCF Landscape using current first-party evidence and explicit procurement, governance, security, portability, and operational criteria.\n\n## Goal and behavioral contract\n\nThe authoritative Goal and artifact references are defined in `descriptor.yaml`. Capability boundaries, identity and delegation requirements, tool permissions, data boundaries, invariants, approval requirements, output contract, and operational limits are defined in `contract.yaml`. MCP\u002FA2A trust boundaries and the reviewed execution closure live in `integrations\u002F` and `dependencies.yaml`; ASPS and assurance requirements live in `assurance.yaml`.\n\nTreat those declarations as mandatory execution constraints. `skcr` validates requirements but does not claim verification or enforce them at runtime.\n\n## When to use\n\n- The organization, its cloud-native products, support, partnership, procurement, outsourcing, or exit strategy is being assessed.\n- Claims about CNCF membership or capabilities need current verification.\n\n## Operating model\n\n1. Treat CNCF Landscape inclusion as classification metadata, not endorsement, certification, security assurance, or proof of product fitness.\n2. Verify current claims against the organization's first-party material and the official CNCF Landscape entry.\n3. Separate organization-level membership from the maturity or CNCF status of individual projects.\n\n## Spec-Driven Change Context\n\n- Treat repository specs, ADRs, runbooks, change proposals, design notes, and task files as durable context that outlives a chat session.\n- For non-trivial changes, prefer a checked-in change artifact or equivalent proposal\u002Fdesign\u002Ftasks record before implementation begins.\n- Capture requirement deltas explicitly: added, modified, removed, deprecated, or unchanged behavior.\n- Keep implementation tasks traceable to acceptance criteria, affected specs, validation commands, and owners.\n- During verification, compare the implementation against the proposal, design decisions, task checklist, and spec deltas.\n- After completion, sync or archive completed change artifacts so the repository's source of truth reflects the final behavior.\n- If the repository has no spec workflow yet, report the missing artifact and provide a minimal proposal\u002Fspec\u002Ftasks outline instead of relying on chat-only intent.\n\n## Skill-Specific Review Scope\n\n- CNCF classification: CNCF Members \u002F Silver\n- First-party source: https:\u002F\u002Fwww.haproxy.com\n- product scope, ownership, support, security, compliance, portability, commercial dependencies, concentration risk, and exit strategy\n\n## Skill-Specific Checklist\n\n- [ ] Confirm legal and product identity, current CNCF classification, offered services, support boundaries, regions, data handling, and shared responsibilities.\n- [ ] Check security documentation, incident handling, vulnerability disclosure, support SLAs, audit evidence, subcontractors, portability, and termination assistance.\n- [ ] Identify proprietary dependencies, lock-in, pricing or licensing constraints, migration paths, and operational ownership.\n- [ ] Trace HAProxy Technologies (member) inputs, outputs, identities, trust boundaries, external dependencies, and persistent state.\n- [ ] Check HAProxy Technologies (member) defaults, configuration precedence, environment separation, and drift from reviewed source.\n- [ ] Check HAProxy Technologies (member) least privilege, credential rotation, audit events, policy enforcement, and break-glass behavior.\n- [ ] Check HAProxy Technologies (member) resource ownership, cleanup, quotas, rate limits, timeouts, retries, and backpressure.\n- [ ] Check HAProxy Technologies (member) release notes, supported upgrade paths, schema or API compatibility, and rollback constraints.\n- [ ] Check HAProxy Technologies (member) dashboards, alerts, health signals, incident procedures, backup evidence, and recovery exercises.\n- [ ] Check HAProxy Technologies (member) license, maintenance state, vulnerability handling, provenance, signatures, and dependency pinning.\n\n## Decision Rules\n\n- Do not infer CNCF project status, certification, security, or endorsement from membership.\n- Do not make procurement or legal conclusions without the applicable current contract and accountable reviewers.\n- Require an exit path and evidence for material capability or compliance claims.\n- If HAProxy Technologies (member) identity, version, edition, or deployment model cannot be established, report the uncertainty before recommending a change.\n- If a HAProxy Technologies (member) change can affect availability, security boundaries, persistent data, or external consumers, require staged validation and explicit rollback criteria.\n\n## Finding Categories\n\n- Identity, scope, classification, or claim mismatch.\n- Security, compliance, support, responsibility, or incident-management gap.\n- Portability, concentration, licensing, cost, contract, or exit-strategy risk.\n- HAProxy Technologies (member) documentation, ownership, maintenance, licensing, provenance, or evidence gap.\n- HAProxy Technologies (member) integration, dependency, compatibility, migration, or decommissioning risk.\n\n## Severity Guidance\n\n- Critical: HAProxy Technologies (member) can enable broad compromise, destructive production mutation, tenant escape, secret exposure, or material data loss.\n- High: HAProxy Technologies (member) can cause exploitable access, sustained outage, corrupt state, unsafe upgrade, or loss of recovery capability.\n- Medium: HAProxy Technologies (member) has a bounded correctness, reliability, compatibility, observability, maintenance, or performance risk.\n- Low: HAProxy Technologies (member) needs documentation, classification, idiomatic configuration, or validation-evidence improvement.\n\n## DevSecOps Guardrails\n\n- Do not read secrets, `.env` files, private keys, production credentials, masked CI\u002FCD variables, database dumps, or sensitive logs unless explicitly required.\n- Do not push, deploy, publish, merge, or create releases unless explicitly asked.\n- Prefer merge requests, reviewable diffs, and auditable validation evidence.\n- Prefer least privilege, minimal changes, and explicit rollback notes.\n- Do not fabricate test results, repository state, commands, security findings, or validation outcomes.\n- Report assumptions, uncertainty, residual risk, and validation gaps clearly.\n\n## Output Requirements\n\n- State the Landscape snapshot classification and sources checked.\n- Return an evidence-backed capability and risk assessment with open questions, owners, and expiry dates.\n- Include a HAProxy Technologies (member) architecture and dependency summary with trust boundaries and persistent state.\n- Include HAProxy Technologies (member) validation commands or tests that are safe for the stated environment.\n- Include HAProxy Technologies (member) ownership, rollout, rollback, monitoring, and follow-up actions.\n\n## Acceptance Criteria\n\n- Membership is not presented as endorsement or project maturity.\n- Material claims, responsibilities, dependencies, and exit assumptions are traceable to current evidence.\n- HAProxy Technologies (member) identity, version, configuration, dependencies, and deployment assumptions are explicit.\n- HAProxy Technologies (member) failure, upgrade, rollback, observability, and recovery paths have proportionate evidence.\n- HAProxy Technologies (member) security boundaries, credentials, network exposure, data handling, and supply-chain risks are addressed.\n\n## Anti-Patterns\n\n- Equating a Landscape logo with CNCF certification or technical approval.\n- Inventing product features, contract terms, regions, certifications, or support commitments.\n- Assuming Landscape inclusion or popularity proves that HAProxy Technologies (member) is secure, supported, compatible, or suitable.\n- Using an unpinned latest version of HAProxy Technologies (member) as the basis for migration or production guidance.\n- Ignoring HAProxy Technologies (member) operational ownership, data lifecycle, upgrade constraints, rollback, and decommissioning.\n\n## Changelog\n\n### 1.0.0 - 2026-09-09\n\n- Initial generated production-ready SDLC \u002F DevSecOps skill.\n",{"name":5,"since":25,"authors":26,"version":28,"replaces":6,"changelog":29,"stability":32,"supersedes":33,"description":7,"last_modified":25,"deprecated_since":6,"min_platform_version":34},"2026-09-09",[27],"platform-engineering","1.0.0",[30],{"date":25,"change":31,"version":28},"Initial generated production-ready SDLC \u002F DevSecOps skill","stable",[],{"pi":35,"bob":35,"kimi":35,"kiro":35,"qwen":35,"cline":35,"codex":35,"crush":35,"iflow":35,"junie":35,"qoder":35,"auggie":35,"cursor":35,"lingma":35,"ollama":35,"factory":35,"amazon-q":35,"continue":35,"costrict":35,"kilocode":35,"opencode":35,"roo-code":35,"windsurf":35,"codebuddy":35,"forgecode":35,"openhands":35,"gemini-cli":35,"gitlab-duo":35,"antigravity":35,"claude-code":35,"github-copilot":35},"unknown","main","ff231df24dc67dfce27f02a6e9a0c51a9d0a0deb",".agents\u002Fskills\u002Fcncf-haproxy-technologies-member-reviewer","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskrun","https:\u002F\u002Fgithub.com\u002Fdomehahn","Proud to live. Love to code and explore. DevSecOps | Cloud & Cloud Native | Java | Go | Python | IaC | AI ","2026-09-10 04:40:25",{"source":8,"skillName":5,"commands":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add domehahn\u002Fskrun --skill cncf-haproxy-technologies-member-reviewer",{"tool":49,"command":50},"bunx","bunx skills add domehahn\u002Fskrun --skill cncf-haproxy-technologies-member-reviewer",{"tool":52,"command":53},"pnpm","pnpm dlx skills add domehahn\u002Fskrun --skill cncf-haproxy-technologies-member-reviewer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskrun\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcncf-haproxy-technologies-member-reviewer\u002FSKILL.md",true,[57,63,69,73,77,81,85,89,93,97,101,105,109,113,119,123],{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"assets\u002FREADME.md","ASSET","资产文件",162,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskrun\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcncf-haproxy-technologies-member-reviewer\u002Fassets\u002FREADME.md",{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"assurance.yaml","REFERENCE","参考文档",393,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskrun\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcncf-haproxy-technologies-member-reviewer\u002Fassurance.yaml",{"path":70,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":71,"sourceHtmlUrl":72},"CHANGELOG.md",133,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskrun\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcncf-haproxy-technologies-member-reviewer\u002FCHANGELOG.md",{"path":74,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":75,"sourceHtmlUrl":76},"contract.yaml",3776,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskrun\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcncf-haproxy-technologies-member-reviewer\u002Fcontract.yaml",{"path":78,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":79,"sourceHtmlUrl":80},"dependencies.yaml",85,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskrun\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcncf-haproxy-technologies-member-reviewer\u002Fdependencies.yaml",{"path":82,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":83,"sourceHtmlUrl":84},"descriptor.yaml",686,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskrun\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcncf-haproxy-technologies-member-reviewer\u002Fdescriptor.yaml",{"path":86,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":87,"sourceHtmlUrl":88},"evals\u002Fbaseline.yaml",2227,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskrun\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcncf-haproxy-technologies-member-reviewer\u002Fevals\u002Fbaseline.yaml",{"path":90,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":91,"sourceHtmlUrl":92},"evals\u002FREADME.md",747,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskrun\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcncf-haproxy-technologies-member-reviewer\u002Fevals\u002FREADME.md",{"path":94,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":95,"sourceHtmlUrl":96},"integrations\u002Fa2a.yaml",307,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskrun\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcncf-haproxy-technologies-member-reviewer\u002Fintegrations\u002Fa2a.yaml",{"path":98,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":99,"sourceHtmlUrl":100},"integrations\u002Fmcp.yaml",32,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskrun\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcncf-haproxy-technologies-member-reviewer\u002Fintegrations\u002Fmcp.yaml",{"path":102,"resourceType":102,"resourceTypeDesc":103,"sizeBytes":104,"sourceHtmlUrl":16},"LICENSE","许可证",214,{"path":106,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":107,"sourceHtmlUrl":108},"README.md",1449,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskrun\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcncf-haproxy-technologies-member-reviewer\u002FREADME.md",{"path":110,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":111,"sourceHtmlUrl":112},"references\u002FREADME.md",195,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskrun\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcncf-haproxy-technologies-member-reviewer\u002Freferences\u002FREADME.md",{"path":114,"resourceType":115,"resourceTypeDesc":116,"sizeBytes":117,"sourceHtmlUrl":118},"scripts\u002FREADME.md","SCRIPT","脚本",230,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskrun\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcncf-haproxy-technologies-member-reviewer\u002Fscripts\u002FREADME.md",{"path":120,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":121,"sourceHtmlUrl":122},"tests\u002FREADME.md",194,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskrun\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcncf-haproxy-technologies-member-reviewer\u002Ftests\u002FREADME.md",{"path":124,"resourceType":125,"resourceTypeDesc":126,"sizeBytes":127,"sourceHtmlUrl":128},"VERSION","OTHER","其他",6,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskrun\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcncf-haproxy-technologies-member-reviewer\u002FVERSION",[130,138,146,154,162,170],{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":134,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":20},"01M7EXRJG42HFM51YA2GYRJQ19","cncf-tikv-reviewer","Review TiKV using its official documentation and repository in the App Definition and Development \u002F Database category. A distributed transactional key-value database. Based on the design of Google Spanner and HBase, but simpler to manage and without dependencies on any distributed filesystem","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskrun\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcncf-tikv-reviewer\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskrun\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcncf-tikv-reviewer\u002FSKILL.md",[],[],{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":142,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":20},"01M7EXRCXG0REKRSZ4ZJVTQKDD","cncf-tigris-data-member-reviewer","Review Tigris Data (member) using its official documentation and repository in the CNCF Members \u002F Silver category.","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskrun\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcncf-tigris-data-member-reviewer\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskrun\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcncf-tigris-data-member-reviewer\u002FSKILL.md",[],[],{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":150,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":20},"01M7EXR7S1RT11KB74JCD0EB5E","cncf-tigera-reviewer","Review Tigera using its official documentation and repository in the Provisioning \u002F Security & Compliance category.","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskrun\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcncf-tigera-reviewer\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskrun\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcncf-tigera-reviewer\u002FSKILL.md",[],[],{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":158,"sourceHtmlUrl":159,"categories":160,"keywords":161,"publishedAt":20},"01M7EXR045HJEW1JAPSZJJFP24","cncf-tigera-member-reviewer","Review Tigera (member) using its official documentation and repository in the CNCF Members \u002F Silver category.","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskrun\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcncf-tigera-member-reviewer\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskrun\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcncf-tigera-member-reviewer\u002FSKILL.md",[],[],{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":166,"sourceHtmlUrl":167,"categories":168,"keywords":169,"publishedAt":20},"01M7EXQSJEW08G3R79VHDDRA7A","cncf-tigera-kcsp-reviewer","Review Tigera (KCSP) using its official documentation and repository in the Special \u002F Kubernetes Certified Service Provider category. Calico helps solve complex use cases, accelerate your adoption process of microservices and bring your team up to speed in operating and supporting your application modernization initiative.","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskrun\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcncf-tigera-kcsp-reviewer\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskrun\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcncf-tigera-kcsp-reviewer\u002FSKILL.md",[],[],{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":174,"sourceHtmlUrl":175,"categories":176,"keywords":177,"publishedAt":20},"01M7EXQMP1D59K2PF8NWRAJ2Q1","cncf-tidb-reviewer","Review TiDB using its official documentation and repository in the App Definition and Development \u002F Database category.","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskrun\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcncf-tidb-reviewer\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskrun\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcncf-tidb-reviewer\u002FSKILL.md",[],[]]