[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78QKK83KA9Y0AC3AP0S8MJS":3,"skill-same:01M78QKK83KA9Y0AC3AP0S8MJS":93},{"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":42,"ownerDescription":43,"updatedAt":44,"install":45,"resources":58},"01M78QKK83KA9Y0AC3AP0S8MJS","implementing-code-signing-for-artifacts",null,"This skill covers implementing code signing for build artifacts to ensure integrity and authenticity throughout the software supply chain. It addresses signing binaries, packages, and containers using GPG, Sigstore, and platform-specific signing tools, establishing trust chains, and verifying signatures in deployment pipelines.","jukeyman\u002Fjukeyman-skills","jukeyman","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F142960420?v=4","01M78FR4Y3DHMMCBCC0GXXNB3F","RICK JEFFERSON","01M78FR4Z8RVQRAD31Y5J7V6EB",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-code-signing-for-artifacts\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-code-signing-for-artifacts\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: implementing-code-signing-for-artifacts\ndescription: >\n  This skill covers implementing code signing for build artifacts to ensure integrity\n  and authenticity throughout the software supply chain. It addresses signing binaries,\n  packages, and containers using GPG, Sigstore, and platform-specific signing tools,\n  establishing trust chains, and verifying signatures in deployment pipelines.\ndomain: cybersecurity\nsubdomain: devsecops\ntags: [devsecops, cicd, code-signing, supply-chain, sigstore, secure-sdlc]\nversion: 1.0.0\nauthor: mahipal\nlicense: Apache-2.0\n---\n\n# Implementing Code Signing for Artifacts\n\n## When to Use\n\n- When establishing artifact integrity verification to prevent supply chain tampering\n- When compliance requires cryptographic proof that build artifacts are authentic and unmodified\n- When distributing software to customers who need to verify publisher identity\n- When implementing zero-trust deployment pipelines that reject unsigned artifacts\n- When meeting SLSA Level 2+ requirements for provenance and integrity\n\n**Do not use** for encrypting artifacts (signing provides integrity, not confidentiality), for container image signing specifically (use cosign), or for source code authentication (use commit signing).\n\n## Prerequisites\n\n- GPG key pair for traditional signing or Sigstore account for keyless signing\n- Code signing certificate from a Certificate Authority for public distribution\n- CI\u002FCD pipeline with access to signing keys or identity provider\n- Verification infrastructure in deployment pipelines\n\n## Workflow\n\n### Step 1: Generate and Manage Signing Keys\n\n```bash\n# Generate GPG key for artifact signing\ngpg --full-generate-key --batch \u003C\u003CEOF\nKey-Type: eddsa\nKey-Curve: ed25519\nSubkey-Type: eddsa\nSubkey-Curve: ed25519\nName-Real: CI Build System\nName-Email: ci-signing@company.com\nExpire-Date: 1y\n%no-protection\nEOF\n\n# Export public key for distribution\ngpg --armor --export ci-signing@company.com > signing-key.pub\n\n# Export private key for CI\u002FCD (store in secrets manager)\ngpg --armor --export-secret-keys ci-signing@company.com > signing-key.priv\n```\n\n### Step 2: Sign Build Artifacts in CI\u002FCD\n\n```yaml\n# .github\u002Fworkflows\u002Fbuild-sign.yml\nname: Build and Sign\n\non:\n  push:\n    tags: ['v*']\n\njobs:\n  build-sign:\n    runs-on: ubuntu-latest\n    permissions:\n      contents: write\n      id-token: write  # For Sigstore keyless signing\n    steps:\n      - uses: actions\u002Fcheckout@v4\n\n      - name: Build artifacts\n        run: |\n          make build\n          sha256sum dist\u002F* > dist\u002Fchecksums.sha256\n\n      - name: Import GPG Key\n        run: |\n          echo \"${{ secrets.GPG_PRIVATE_KEY }}\" | gpg --batch --import\n          gpg --list-secret-keys\n\n      - name: Sign artifacts\n        run: |\n          for file in dist\u002F*; do\n            gpg --detach-sign --armor --local-user ci-signing@company.com \"$file\"\n          done\n\n      - name: Install cosign for keyless signing\n        uses: sigstore\u002Fcosign-installer@v3\n\n      - name: Keyless sign with Sigstore\n        run: |\n          for file in dist\u002F*.tar.gz; do\n            cosign sign-blob \"$file\" \\\n              --output-signature \"${file}.sig\" \\\n              --output-certificate \"${file}.cert\" \\\n              --yes\n          done\n\n      - name: Create Release with signed artifacts\n        uses: softprops\u002Faction-gh-release@v2\n        with:\n          files: |\n            dist\u002F*\n            dist\u002F*.asc\n            dist\u002F*.sig\n            dist\u002F*.cert\n```\n\n### Step 3: Verify Signatures in Deployment Pipeline\n\n```bash\n# Verify GPG signature\ngpg --import signing-key.pub\ngpg --verify artifact.tar.gz.asc artifact.tar.gz\n\n# Verify Sigstore keyless signature\ncosign verify-blob artifact.tar.gz \\\n  --signature artifact.tar.gz.sig \\\n  --certificate artifact.tar.gz.cert \\\n  --certificate-identity ci-signing@company.com \\\n  --certificate-oidc-issuer https:\u002F\u002Ftoken.actions.githubusercontent.com\n\n# Verify checksums\nsha256sum --check checksums.sha256\n```\n\n### Step 4: Sign npm Packages with Provenance\n\n```json\n{\n  \"scripts\": {\n    \"prepublishOnly\": \"npm run build && npm run test\"\n  },\n  \"publishConfig\": {\n    \"provenance\": true\n  }\n}\n```\n\n```bash\n# Publish npm package with provenance attestation\nnpm publish --provenance\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| Code Signing | Cryptographic process of signing software artifacts to verify publisher identity and artifact integrity |\n| Detached Signature | Signature stored in a separate file from the artifact, allowing independent distribution |\n| Keyless Signing | Sigstore's approach using short-lived certificates tied to OIDC identities instead of long-lived keys |\n| Provenance | Metadata describing how, where, and by whom an artifact was built |\n| Transparency Log | Append-only log (Rekor) that records all signing events for public auditability |\n| Trust Chain | Hierarchical chain from root CA to signing certificate establishing trust in the signer's identity |\n| SLSA | Supply-chain Levels for Software Artifacts — framework defining levels of supply chain security |\n\n## Tools & Systems\n\n- **GPG\u002FPGP**: Traditional asymmetric cryptography tool for signing and verifying artifacts\n- **Sigstore (cosign)**: Modern keyless signing infrastructure using OIDC identity and transparency logs\n- **Rekor**: Sigstore's transparency log recording all signing events immutably\n- **Fulcio**: Sigstore's certificate authority issuing short-lived certificates bound to OIDC identities\n- **notation**: Microsoft's artifact signing tool for OCI registries (Project Notary v2)\n\n## Common Scenarios\n\n### Scenario: Establishing Signed Release Pipeline\n\n**Context**: An open-source project needs to sign release artifacts so users can verify authenticity and detect tampering.\n\n**Approach**:\n1. Use Sigstore keyless signing in GitHub Actions (no key management overhead)\n2. Sign all release binaries with `cosign sign-blob` using OIDC identity\n3. Generate and sign checksums file for bulk verification\n4. Upload signatures, certificates, and checksums alongside release artifacts\n5. Document verification instructions in the project README\n6. Add verification step to the Homebrew formula or apt repository\n\n**Pitfalls**: GPG key compromise requires revoking and re-signing all artifacts. Sigstore keyless signing avoids this by using ephemeral keys. Long-lived signing keys in CI\u002FCD secrets are a supply chain risk if the CI system is compromised.\n\n## Output Format\n\n```\nArtifact Signing Report\n========================\nPipeline: Build and Sign v2.3.0\nDate: 2026-02-23\nSigning Method: Sigstore Keyless + GPG\n\nSIGNED ARTIFACTS:\n  app-v2.3.0-linux-amd64.tar.gz\n    GPG:      PASS (ci-signing@company.com, EdDSA\u002FEd25519)\n    Sigstore: PASS (Rekor entry: 24658135, Fulcio cert issued)\n    SHA256:   a1b2c3d4...\n\n  app-v2.3.0-darwin-arm64.tar.gz\n    GPG:      PASS\n    Sigstore: PASS (Rekor entry: 24658136)\n    SHA256:   e5f6g7h8...\n\n  checksums.sha256\n    GPG:      PASS (detached signature)\n\nTRANSPARENCY LOG:\n  Entries recorded: 3\n  Log index range: 24658135-24658137\n  Verification: https:\u002F\u002Fsearch.sigstore.dev\n```\n","# Implementing Code Signing for Artifacts\n\n## When to Use\n\n- When establishing artifact integrity verification to prevent supply chain tampering\n- When compliance requires cryptographic proof that build artifacts are authentic and unmodified\n- When distributing software to customers who need to verify publisher identity\n- When implementing zero-trust deployment pipelines that reject unsigned artifacts\n- When meeting SLSA Level 2+ requirements for provenance and integrity\n\n**Do not use** for encrypting artifacts (signing provides integrity, not confidentiality), for container image signing specifically (use cosign), or for source code authentication (use commit signing).\n\n## Prerequisites\n\n- GPG key pair for traditional signing or Sigstore account for keyless signing\n- Code signing certificate from a Certificate Authority for public distribution\n- CI\u002FCD pipeline with access to signing keys or identity provider\n- Verification infrastructure in deployment pipelines\n\n## Workflow\n\n### Step 1: Generate and Manage Signing Keys\n\n```bash\n# Generate GPG key for artifact signing\ngpg --full-generate-key --batch \u003C\u003CEOF\nKey-Type: eddsa\nKey-Curve: ed25519\nSubkey-Type: eddsa\nSubkey-Curve: ed25519\nName-Real: CI Build System\nName-Email: ci-signing@company.com\nExpire-Date: 1y\n%no-protection\nEOF\n\n# Export public key for distribution\ngpg --armor --export ci-signing@company.com > signing-key.pub\n\n# Export private key for CI\u002FCD (store in secrets manager)\ngpg --armor --export-secret-keys ci-signing@company.com > signing-key.priv\n```\n\n### Step 2: Sign Build Artifacts in CI\u002FCD\n\n```yaml\n# .github\u002Fworkflows\u002Fbuild-sign.yml\nname: Build and Sign\n\non:\n  push:\n    tags: ['v*']\n\njobs:\n  build-sign:\n    runs-on: ubuntu-latest\n    permissions:\n      contents: write\n      id-token: write  # For Sigstore keyless signing\n    steps:\n      - uses: actions\u002Fcheckout@v4\n\n      - name: Build artifacts\n        run: |\n          make build\n          sha256sum dist\u002F* > dist\u002Fchecksums.sha256\n\n      - name: Import GPG Key\n        run: |\n          echo \"${{ secrets.GPG_PRIVATE_KEY }}\" | gpg --batch --import\n          gpg --list-secret-keys\n\n      - name: Sign artifacts\n        run: |\n          for file in dist\u002F*; do\n            gpg --detach-sign --armor --local-user ci-signing@company.com \"$file\"\n          done\n\n      - name: Install cosign for keyless signing\n        uses: sigstore\u002Fcosign-installer@v3\n\n      - name: Keyless sign with Sigstore\n        run: |\n          for file in dist\u002F*.tar.gz; do\n            cosign sign-blob \"$file\" \\\n              --output-signature \"${file}.sig\" \\\n              --output-certificate \"${file}.cert\" \\\n              --yes\n          done\n\n      - name: Create Release with signed artifacts\n        uses: softprops\u002Faction-gh-release@v2\n        with:\n          files: |\n            dist\u002F*\n            dist\u002F*.asc\n            dist\u002F*.sig\n            dist\u002F*.cert\n```\n\n### Step 3: Verify Signatures in Deployment Pipeline\n\n```bash\n# Verify GPG signature\ngpg --import signing-key.pub\ngpg --verify artifact.tar.gz.asc artifact.tar.gz\n\n# Verify Sigstore keyless signature\ncosign verify-blob artifact.tar.gz \\\n  --signature artifact.tar.gz.sig \\\n  --certificate artifact.tar.gz.cert \\\n  --certificate-identity ci-signing@company.com \\\n  --certificate-oidc-issuer https:\u002F\u002Ftoken.actions.githubusercontent.com\n\n# Verify checksums\nsha256sum --check checksums.sha256\n```\n\n### Step 4: Sign npm Packages with Provenance\n\n```json\n{\n  \"scripts\": {\n    \"prepublishOnly\": \"npm run build && npm run test\"\n  },\n  \"publishConfig\": {\n    \"provenance\": true\n  }\n}\n```\n\n```bash\n# Publish npm package with provenance attestation\nnpm publish --provenance\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| Code Signing | Cryptographic process of signing software artifacts to verify publisher identity and artifact integrity |\n| Detached Signature | Signature stored in a separate file from the artifact, allowing independent distribution |\n| Keyless Signing | Sigstore's approach using short-lived certificates tied to OIDC identities instead of long-lived keys |\n| Provenance | Metadata describing how, where, and by whom an artifact was built |\n| Transparency Log | Append-only log (Rekor) that records all signing events for public auditability |\n| Trust Chain | Hierarchical chain from root CA to signing certificate establishing trust in the signer's identity |\n| SLSA | Supply-chain Levels for Software Artifacts — framework defining levels of supply chain security |\n\n## Tools & Systems\n\n- **GPG\u002FPGP**: Traditional asymmetric cryptography tool for signing and verifying artifacts\n- **Sigstore (cosign)**: Modern keyless signing infrastructure using OIDC identity and transparency logs\n- **Rekor**: Sigstore's transparency log recording all signing events immutably\n- **Fulcio**: Sigstore's certificate authority issuing short-lived certificates bound to OIDC identities\n- **notation**: Microsoft's artifact signing tool for OCI registries (Project Notary v2)\n\n## Common Scenarios\n\n### Scenario: Establishing Signed Release Pipeline\n\n**Context**: An open-source project needs to sign release artifacts so users can verify authenticity and detect tampering.\n\n**Approach**:\n1. Use Sigstore keyless signing in GitHub Actions (no key management overhead)\n2. Sign all release binaries with `cosign sign-blob` using OIDC identity\n3. Generate and sign checksums file for bulk verification\n4. Upload signatures, certificates, and checksums alongside release artifacts\n5. Document verification instructions in the project README\n6. Add verification step to the Homebrew formula or apt repository\n\n**Pitfalls**: GPG key compromise requires revoking and re-signing all artifacts. Sigstore keyless signing avoids this by using ephemeral keys. Long-lived signing keys in CI\u002FCD secrets are a supply chain risk if the CI system is compromised.\n\n## Output Format\n\n```\nArtifact Signing Report\n========================\nPipeline: Build and Sign v2.3.0\nDate: 2026-02-23\nSigning Method: Sigstore Keyless + GPG\n\nSIGNED ARTIFACTS:\n  app-v2.3.0-linux-amd64.tar.gz\n    GPG:      PASS (ci-signing@company.com, EdDSA\u002FEd25519)\n    Sigstore: PASS (Rekor entry: 24658135, Fulcio cert issued)\n    SHA256:   a1b2c3d4...\n\n  app-v2.3.0-darwin-arm64.tar.gz\n    GPG:      PASS\n    Sigstore: PASS (Rekor entry: 24658136)\n    SHA256:   e5f6g7h8...\n\n  checksums.sha256\n    GPG:      PASS (detached signature)\n\nTRANSPARENCY LOG:\n  Entries recorded: 3\n  Log index range: 24658135-24658137\n  Verification: https:\u002F\u002Fsearch.sigstore.dev\n```\n",{"name":5,"tags":25,"author":32,"domain":33,"license":15,"version":34,"subdomain":26,"description":35},[26,27,28,29,30,31],"devsecops","cicd","code-signing","supply-chain","sigstore","secure-sdlc","mahipal","cybersecurity","1.0.0","This skill covers implementing code signing for build artifacts to ensure integrity and authenticity throughout the software supply chain. It addresses signing binaries, packages, and containers using GPG, Sigstore, and platform-specific signing tools, establishing trust chains, and verifying signatures in deployment pipelines.\n","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fimplementing-code-signing-for-artifacts",0,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills","https:\u002F\u002Fgithub.com\u002Fjukeyman","https:\u002F\u002FRJBUSINESSSOLUTIONS.ORG","Credit and Finance Expert | Developer\r\n\r\nI'm Rick Jefferson, a seasoned credit and finance expert with over a decade of experience in financial literacy,","2026-07-13 07:03:29",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add jukeyman\u002Fjukeyman-skills --skill implementing-code-signing-for-artifacts",{"tool":51,"command":52},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill implementing-code-signing-for-artifacts",{"tool":54,"command":55},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill implementing-code-signing-for-artifacts","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-code-signing-for-artifacts\u002FSKILL.md",true,[59,65,69,75,79,83,89],{"path":60,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":63,"sourceHtmlUrl":64},"assets\u002Ftemplate.md","ASSET","资产文件",1234,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-code-signing-for-artifacts\u002Fassets\u002Ftemplate.md",{"path":66,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Fapi-reference.md","REFERENCE","参考文档",1841,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-code-signing-for-artifacts\u002Freferences\u002Fapi-reference.md",{"path":76,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fstandards.md",1542,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-code-signing-for-artifacts\u002Freferences\u002Fstandards.md",{"path":80,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fworkflows.md",1880,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-code-signing-for-artifacts\u002Freferences\u002Fworkflows.md",{"path":84,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":87,"sourceHtmlUrl":88},"scripts\u002Fagent.py","SCRIPT","脚本",6028,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-code-signing-for-artifacts\u002Fscripts\u002Fagent.py",{"path":90,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":91,"sourceHtmlUrl":92},"scripts\u002Fprocess.py",7435,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-code-signing-for-artifacts\u002Fscripts\u002Fprocess.py",[94,102,109,116,123,131],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":98,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":20},"01M79ANS2SM329NEP5ZCX106RR","zustand-store-creator","Create zustand store creator operations. Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category. Use when working with zustand store creator functionality. Trigger with phrases like \"zustand store creator\", \"zustand creator\", \"zustand\".","MIT","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":98,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":20},"01M79AMZKP4YDEZ7EHG1Y7PP74","zero-trust-config-helper","Configure with zero trust config helper operations. Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category. Use when configuring systems or services. Trigger with phrases like \"zero trust config helper\", \"zero helper\", \"zero\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzero-trust-config-helper\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":98,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":20},"01M79AMJSBCEJQNBTYNAHYN5HM","zapier-integration-helper","Assist with zapier integration helper operations. Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category. Use when working with APIs or building integrations. Trigger with phrases like \"zapier integration helper\", \"zapier helper\", \"zapier\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzapier-integration-helper\u002FSKILL.md",[],[],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":98,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":20},"01M79AHJZGVMARS13VFQYRR1MP","yaml-config-validator","Validate yaml config validator operations. Auto-activating skill for DevOps Basics.\nTriggers on: yaml config validator, yaml config validator\nPart of the DevOps Basics skill category. Use when configuring systems or services. Trigger with phrases like \"yaml config validator\", \"yaml validator\", \"yaml\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fyaml-config-validator\u002FSKILL.md",[],[],{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":98,"licenseFileUrl":127,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":20},"01M79AHGDZRN0020RDQSQDPAM8","xvary-stock-research","Thesis-driven equity analysis from public SEC EDGAR and market data; \u002Fanalyze, \u002Fscore, \u002Fcompare workflows with bundled Python tools (Claude Code, Cursor, Codex).","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FSKILL.md",[],[],{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":98,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":20},"01M79AHCYJ9FV9RMHQ24HDRN33","xss-vulnerability-scanner","Scan xss vulnerability scanner operations. Auto-activating skill for Security Fundamentals.\nTriggers on: xss vulnerability scanner, xss vulnerability scanner\nPart of the Security Fundamentals skill category. Use when working with xss vulnerability scanner functionality. Trigger with phrases like \"xss vulnerability scanner\", \"xss scanner\", \"xss\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxss-vulnerability-scanner\u002FSKILL.md",[],[]]