[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79SW0WTFTXKEH4RRAY3A27N":3,"skill-same:01M79SW0WTFTXKEH4RRAY3A27N":102},{"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":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":6,"ownerHtmlUrl":41,"ownerBlogUrl":6,"ownerDescription":42,"updatedAt":43,"install":44,"resources":57},"01M79SW0WTFTXKEH4RRAY3A27N","release-readiness-reviewer",null,"Describe what this skill helps an agent do.","domehahn\u002Fskil","domehahn","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F41511445?v=4","01M735R3R9KEBEJ6D5YYAE9A61","Dominik Hahn","01M79S340TEWDQRH7SG9K78X3X",1,"MIT","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskil\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Frelease-readiness-reviewer\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskil\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Frelease-readiness-reviewer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"release-readiness-reviewer\"\ndescription: \"Describe what this skill helps an agent do.\"\nversion: \"0.1.0\"\nsince: \"2026-07-28\"\nlast_modified: \"2026-07-28\"\nauthors:\n  - \"platform-engineering\"\nstability: \"experimental\"\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: \"0.1.0\"\n    date: \"2026-07-28\"\n    change: \"Initial generated production-ready SDLC \u002F DevSecOps skill\"\n---\n# Release Readiness Reviewer\n\n## Purpose\n\nDetermine whether a change or system is ready for release by reviewing test status, security findings, known issues, rollback, migrations, monitoring, alerts, runbooks, feature flags, approvals, release notes, support readiness, and go\u002Fno-go recommendation.\n\n## When to use\n\n- A release, deployment, version bump, migration, or production rollout needs go\u002Fno-go review.\n- Known issues, security findings, rollback, monitoring, or support readiness are unclear.\n- Feature flags, staged rollout, or compatibility risk must be assessed.\n- Release notes, approvals, or operational ownership need validation.\n- The central agent routes to release readiness review.\n\n## Operating model\n\n1. Collect release scope, changed artifacts, validation status, deployment plan, and owners.\n2. Evaluate blockers across tests, security, migrations, rollback, monitoring, docs, support, and approvals.\n3. Separate go\u002Fno-go criteria from follow-up work and known accepted risks.\n4. Assess rollout strategy, feature flags, blast radius, and recovery time.\n5. Return go, conditional go, or no-go with explicit blockers.\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- Test status, validation evidence, security findings, and known issues.\n- Rollback, migrations, compatibility, feature flags, and staged rollout.\n- Monitoring, alerts, runbooks, support readiness, and ownership.\n- Approvals, release notes, communication, and go\u002Fno-go decision.\n- Blockers, exceptions, residual risk, and follow-up actions.\n\n## Skill-Specific Checklist\n\n- [ ] Verify required tests, builds, scans, migrations, and smoke checks are complete.\n- [ ] Identify unresolved blockers and classify known issues by user impact.\n- [ ] Check open security findings, exceptions, owners, and expiry.\n- [ ] Verify rollback plan, rollback trigger, rollback owner, and data rollback constraints.\n- [ ] Check migration forward\u002Fbackward compatibility, idempotency, and backup plan.\n- [ ] Verify monitoring dashboards, alerts, SLO indicators, and post-deploy validation.\n- [ ] Check runbooks, escalation contacts, on-call coverage, and support readiness.\n- [ ] Check release notes, changelog, customer communication, and breaking-change guidance.\n- [ ] Identify feature flag, canary, staged rollout, kill switch, or traffic-shaping options.\n- [ ] Confirm approvals, release owner, deployment window, and freeze constraints.\n- [ ] Check dependencies on external services, infra capacity, and version compatibility.\n- [ ] Produce go\u002Fno-go with explicit conditions.\n\n## Decision Rules\n\n- If rollback is impossible or untested for high-impact change, no-go unless risk is accepted by owner.\n- If Critical\u002FHigh security findings are open without approved exception, no-go.\n- If migrations can corrupt or lose data without backup and validation, no-go.\n- If monitoring cannot detect release failure, require conditional go or no-go by impact.\n- If known issues affect core user journeys, require mitigation, communication, or staged rollout.\n- If release notes omit breaking changes or migrations, block external release readiness.\n\n## Finding Categories\n\n- Missing go\u002Fno-go evidence or owner.\n- Failed, skipped, stale, or insufficient validation gate.\n- Open security, compliance, privacy, or known-issue blocker.\n- Rollback, migration, compatibility, or data-safety gap.\n- Monitoring, alerting, runbook, on-call, or support readiness gap.\n- Release notes, communication, approval, or change-management gap.\n\n## Severity Guidance\n\n- Critical: immediate exploitability or operational failure can expose secrets, regulated data, production safety, or release integrity.\n- High: credible security, reliability, compliance, rollback, or user-impact risk requires owner action before merge or release.\n- Medium: meaningful maintainability, validation, documentation, or process gap should be tracked and resolved.\n- Low: advisory improvement, clarity issue, or hardening opportunity with limited immediate impact.\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- Go\u002Fno-go summary with blockers, conditions, and owner.\n- Release checklist covering tests, security, migrations, rollback, monitoring, docs, support, and approvals.\n- Known issues table with severity, impact, mitigation, and acceptance owner.\n- Rollback and post-deploy validation plan.\n- Feature flag, canary, staged rollout, or kill-switch recommendation.\n- Residual risks and follow-up actions with deadlines.\n\n## Acceptance Criteria\n\n- All release blockers are resolved or explicitly accepted.\n- Rollback, migration, monitoring, and support readiness are verified.\n- Security findings and known issues have owner-approved disposition.\n- Release notes cover breaking changes, migrations, and operational impact.\n- Go\u002Fno-go recommendation follows evidence.\n- Post-release validation and escalation path are defined.\n\n## Anti-Patterns\n\n- Treating green CI as complete release readiness.\n- Approving release with no rollback trigger or owner.\n- Ignoring known issues because they are documented elsewhere.\n- Skipping monitoring and support readiness until after deployment.\n- Accepting security findings without expiry and owner.\n- Publishing breaking changes without migration guidance.\n\n## Changelog\n\n### 0.1.0 - 2026-07-28\n\n- Initial generated production-ready SDLC \u002F DevSecOps skill.\n","# Release Readiness Reviewer\n\n## Purpose\n\nDetermine whether a change or system is ready for release by reviewing test status, security findings, known issues, rollback, migrations, monitoring, alerts, runbooks, feature flags, approvals, release notes, support readiness, and go\u002Fno-go recommendation.\n\n## When to use\n\n- A release, deployment, version bump, migration, or production rollout needs go\u002Fno-go review.\n- Known issues, security findings, rollback, monitoring, or support readiness are unclear.\n- Feature flags, staged rollout, or compatibility risk must be assessed.\n- Release notes, approvals, or operational ownership need validation.\n- The central agent routes to release readiness review.\n\n## Operating model\n\n1. Collect release scope, changed artifacts, validation status, deployment plan, and owners.\n2. Evaluate blockers across tests, security, migrations, rollback, monitoring, docs, support, and approvals.\n3. Separate go\u002Fno-go criteria from follow-up work and known accepted risks.\n4. Assess rollout strategy, feature flags, blast radius, and recovery time.\n5. Return go, conditional go, or no-go with explicit blockers.\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- Test status, validation evidence, security findings, and known issues.\n- Rollback, migrations, compatibility, feature flags, and staged rollout.\n- Monitoring, alerts, runbooks, support readiness, and ownership.\n- Approvals, release notes, communication, and go\u002Fno-go decision.\n- Blockers, exceptions, residual risk, and follow-up actions.\n\n## Skill-Specific Checklist\n\n- [ ] Verify required tests, builds, scans, migrations, and smoke checks are complete.\n- [ ] Identify unresolved blockers and classify known issues by user impact.\n- [ ] Check open security findings, exceptions, owners, and expiry.\n- [ ] Verify rollback plan, rollback trigger, rollback owner, and data rollback constraints.\n- [ ] Check migration forward\u002Fbackward compatibility, idempotency, and backup plan.\n- [ ] Verify monitoring dashboards, alerts, SLO indicators, and post-deploy validation.\n- [ ] Check runbooks, escalation contacts, on-call coverage, and support readiness.\n- [ ] Check release notes, changelog, customer communication, and breaking-change guidance.\n- [ ] Identify feature flag, canary, staged rollout, kill switch, or traffic-shaping options.\n- [ ] Confirm approvals, release owner, deployment window, and freeze constraints.\n- [ ] Check dependencies on external services, infra capacity, and version compatibility.\n- [ ] Produce go\u002Fno-go with explicit conditions.\n\n## Decision Rules\n\n- If rollback is impossible or untested for high-impact change, no-go unless risk is accepted by owner.\n- If Critical\u002FHigh security findings are open without approved exception, no-go.\n- If migrations can corrupt or lose data without backup and validation, no-go.\n- If monitoring cannot detect release failure, require conditional go or no-go by impact.\n- If known issues affect core user journeys, require mitigation, communication, or staged rollout.\n- If release notes omit breaking changes or migrations, block external release readiness.\n\n## Finding Categories\n\n- Missing go\u002Fno-go evidence or owner.\n- Failed, skipped, stale, or insufficient validation gate.\n- Open security, compliance, privacy, or known-issue blocker.\n- Rollback, migration, compatibility, or data-safety gap.\n- Monitoring, alerting, runbook, on-call, or support readiness gap.\n- Release notes, communication, approval, or change-management gap.\n\n## Severity Guidance\n\n- Critical: immediate exploitability or operational failure can expose secrets, regulated data, production safety, or release integrity.\n- High: credible security, reliability, compliance, rollback, or user-impact risk requires owner action before merge or release.\n- Medium: meaningful maintainability, validation, documentation, or process gap should be tracked and resolved.\n- Low: advisory improvement, clarity issue, or hardening opportunity with limited immediate impact.\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- Go\u002Fno-go summary with blockers, conditions, and owner.\n- Release checklist covering tests, security, migrations, rollback, monitoring, docs, support, and approvals.\n- Known issues table with severity, impact, mitigation, and acceptance owner.\n- Rollback and post-deploy validation plan.\n- Feature flag, canary, staged rollout, or kill-switch recommendation.\n- Residual risks and follow-up actions with deadlines.\n\n## Acceptance Criteria\n\n- All release blockers are resolved or explicitly accepted.\n- Rollback, migration, monitoring, and support readiness are verified.\n- Security findings and known issues have owner-approved disposition.\n- Release notes cover breaking changes, migrations, and operational impact.\n- Go\u002Fno-go recommendation follows evidence.\n- Post-release validation and escalation path are defined.\n\n## Anti-Patterns\n\n- Treating green CI as complete release readiness.\n- Approving release with no rollback trigger or owner.\n- Ignoring known issues because they are documented elsewhere.\n- Skipping monitoring and support readiness until after deployment.\n- Accepting security findings without expiry and owner.\n- Publishing breaking changes without migration guidance.\n\n## Changelog\n\n### 0.1.0 - 2026-07-28\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-07-28",[27],"platform-engineering","0.1.0",[30],{"date":25,"change":31,"version":28},"Initial generated production-ready SDLC \u002F DevSecOps skill","experimental",[],{"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","ce77407acf7712c54de9f45e736e76806c73acb7",".github\u002Fskills\u002Frelease-readiness-reviewer",2,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskil","https:\u002F\u002Fgithub.com\u002Fdomehahn","Proud to live. Love to code and explore. DevSecOps | Cloud & Cloud Native | Java | Go | Python | IaC | AI ","2026-11-11 00:29:29",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add domehahn\u002Fskil --skill release-readiness-reviewer",{"tool":50,"command":51},"bunx","bunx skills add domehahn\u002Fskil --skill release-readiness-reviewer",{"tool":53,"command":54},"pnpm","pnpm dlx skills add domehahn\u002Fskil --skill release-readiness-reviewer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskil\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Frelease-readiness-reviewer\u002FSKILL.md",true,[58,64,70,74,78,82,88,92,96],{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"assets\u002FREADME.md","ASSET","资产文件",147,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskil\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Frelease-readiness-reviewer\u002Fassets\u002FREADME.md",{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"CHANGELOG.md","REFERENCE","参考文档",49,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskil\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Frelease-readiness-reviewer\u002FCHANGELOG.md",{"path":71,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":16},"LICENSE","许可证",214,{"path":75,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":76,"sourceHtmlUrl":77},"README.md",396,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskil\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Frelease-readiness-reviewer\u002FREADME.md",{"path":79,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002FREADME.md",180,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskil\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Frelease-readiness-reviewer\u002Freferences\u002FREADME.md",{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"scripts\u002FREADME.md","SCRIPT","脚本",215,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskil\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Frelease-readiness-reviewer\u002Fscripts\u002FREADME.md",{"path":89,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":90,"sourceHtmlUrl":91},"skill.yaml",242,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskil\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Frelease-readiness-reviewer\u002Fskill.yaml",{"path":93,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":94,"sourceHtmlUrl":95},"tests\u002FREADME.md",102,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskil\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Frelease-readiness-reviewer\u002Ftests\u002FREADME.md",{"path":97,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":100,"sourceHtmlUrl":101},"VERSION","OTHER","其他",6,"https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskil\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Frelease-readiness-reviewer\u002FVERSION",[103,110,116,122,128,134],{"skillNo":104,"name":105,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":106,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":20},"01M79TB68RNF60T02TCFPK0XGB","yara-malware","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskil\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fsecurity\u002Fyara-malware\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":106,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":20},"01M79TB2ZSY0K8Q6PT9CX0KXNP","vulnerable-osv","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskil\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fsecurity\u002Fvulnerable-osv\u002FSKILL.md",[],[],{"skillNo":117,"name":118,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":106,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":20},"01M79TAZMZ6V0H92CF3AA029JW","vulnerable-dependency","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskil\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fsecurity\u002Fvulnerable-dependency\u002FSKILL.md",[],[],{"skillNo":123,"name":124,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":106,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":20},"01M79TAWESFSFZE3M9GB7RD4RC","unicode-deception","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskil\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fsecurity\u002Funicode-deception\u002FSKILL.md",[],[],{"skillNo":129,"name":130,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":106,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":20},"01M79TATMDXB6J79H1EQRMVN70","secret-exfiltration","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskil\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fsecurity\u002Fsecret-exfiltration\u002FSKILL.md",[],[],{"skillNo":135,"name":136,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":106,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":20},"01M79TAQ8JEA7YTD0YD9WCSQEQ","prompt-injection","https:\u002F\u002Fgithub.com\u002Fdomehahn\u002Fskil\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fsecurity\u002Fprompt-injection\u002FSKILL.md",[],[]]