[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CADZY6773ESPR8Y8PYZBXM":3,"skill-same:01M7CADZY6773ESPR8Y8PYZBXM":55},{"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":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":14,"repositoryHtmlUrl":36,"repositoryHomepageUrl":6,"ownerHtmlUrl":37,"ownerBlogUrl":38,"ownerDescription":39,"updatedAt":40,"install":41,"resources":54},"01M7CADZY6773ESPR8Y8PYZBXM","vulnerability-remediation",null,"Reviews vulnerability policy violations for the chainloop project recorded in Chainloop and performs fixes in Dockerfiles or go.mod. Use when asked to fix vulnerabilities, review CVEs, or remediate security issues in chainloop.","shenyimings\u002Fskillet","shenyimings","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F89332218?v=4","01M7C9KHMXPPXMQJCKN78FKB06","Yiming Shen","01M7C9KHP4KS809T2A9T64YDWE",0,"MIT","https:\u002F\u002Fgithub.com\u002Fshenyimings\u002Fskillet\u002Fblob\u002Fmain\u002Fbenchmark\u002Fwild\u002Fdev\u002Fsafe\u002Fchainloop-dev__chainloop__.claude__skills__vulnerability-remediation\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: vulnerability-remediation\ndescription: Reviews vulnerability policy violations for the chainloop project recorded in Chainloop and performs fixes in Dockerfiles or go.mod. Use when asked to fix vulnerabilities, review CVEs, or remediate security issues in chainloop.\nallowed-tools:\n  - Bash\n  - Read\n  - Edit\n  - Task\n  - mcp__claude_ai_Chainloop__list_products_with_versions\n  - mcp__claude_ai_Chainloop__get_frameworks_compliance\n  - mcp__claude_ai_Chainloop__list_pieces_of_evidence\n  - mcp__claude_ai_Chainloop__download_evidence_by_digest\n---\n\n# Vulnerability Remediation for chainloop\n\nThis skill reviews open vulnerability policy violations recorded in Chainloop for the `chainloop` project and applies fixes to the affected source files.\n\n## Step 1: Find the Latest Project Version\n\nUse `list_products_with_versions` (no parameters needed — uses the current `chainloop` org) and locate the **Chainloop Community Edition** product. Find the `chainloop` project version entry and note its `projectVersionId` (UUID).\n\n## Step 2: Gather Compliance Results and Evidence in Parallel\n\nOnce the `projectVersionId` is known, make both of these calls **at the same time**:\n\n**Call A** — `get_frameworks_compliance`:\n- `project_version_id`: the UUID from Step 1\n- `framework_ids`: `[\"0ceef195-6900-4166-8407-77eb84954ed3\"]` (chainloop-best-practices)\n\n**Call B** — `list_pieces_of_evidence`:\n- `project_name`: `chainloop`\n- `project_version_name`: the version name from Step 1 (e.g. `v1.77.0`)\n- `latest`: `true`\n\n### Parsing the compliance result (Call A)\n\nThe response will be large — parse it programmatically using a Bash subagent:\n\n```python\nimport json\n\nwith open('\u003Ctool-result-file>') as f:\n    raw = json.load(f)\ndata = json.loads(raw[0]['text'])\n\nfor req in data:\n    if 'vulnerabilit' in req.get('name', '').lower():\n        status = req.get('status', '')\n        failed = [e for e in req.get('policyEvaluations', [])\n                  if e.get('status') not in ('PASSED', 'SKIPPED')]\n        print(f\"Requirement: {req['name']} — Status: {status}\")\n        for e in failed:\n            print(f\"  FAILED: policy={e['name']} material={e.get('materialName','-')} status={e.get('status','-')}\")\n```\n\nThis gives you the list of **failing material names** (e.g. `control-plane-migrations-report`).\n\n## Step 3: Download the SARIF for Each Failing Material\n\nFrom the `list_pieces_of_evidence` result (Call B above), find the item whose `name` matches the failing material name and whose `kind` is `SARIF`. Use its `digest` field directly — no need to decode attestations.\n\nCall `download_evidence_by_digest` with:\n- `digest`: the digest of the matching SARIF item\n- `download_content`: `true`\n\nThe SARIF `logicalLocations[].fullyQualifiedName` field contains the full image reference, e.g.:\n```\nghcr.io\u002Fchainloop-dev\u002Fchainloop\u002Fcontrol-plane-migrations:v1.77.0@sha256:\u003Cdigest>:\u002Fatlas\n```\n\nThe binary path (e.g. `\u002Fatlas`, `\u002Fapp`) tells you which binary inside the image is vulnerable.\n\n## Step 4: Identify the Fix\n\n### 4a. Atlas \u002F Migration Dockerfile vulnerabilities\n\n**Symptom**: SARIF location is `\u002Fatlas`, image is `control-plane-migrations`\n\n**Source file**: `app\u002Fcontrolplane\u002FDockerfile.migrations`\n\n**Fix procedure**:\n1. Check the current atlas version in the comment at the top of the Dockerfile (e.g. `# atlas version v1.2.0`)\n2. Find the latest available stable version:\n   ```bash\n   curl -s \"https:\u002F\u002Fregistry.hub.docker.com\u002Fv2\u002Frepositories\u002Farigaio\u002Fatlas\u002Ftags?page_size=20&ordering=last_updated\" \\\n     | python3 -c \"import json,sys; [print(t['name']) for t in json.load(sys.stdin)['results'] if t['name'][0].isdigit() and '-' not in t['name']]\"\n   ```\n3. Run grype on the current and candidate versions to confirm the CVEs are present then gone:\n   ```bash\n   grype arigaio\u002Fatlas:\u003Ccurrent-version> --only-fixed 2>&1\n   grype arigaio\u002Fatlas:\u003Cnew-version> --only-fixed 2>&1\n   ```\n   A clean run has only the header line and no CVE rows.\n4. **If the latest stable tag still has CVEs**, also check the `latest` tag — atlas rebuilds it frequently with updated Go toolchain and dependencies:\n   ```bash\n   docker pull arigaio\u002Fatlas:latest\n   grype arigaio\u002Fatlas:latest --only-fixed 2>&1\n   docker run --rm arigaio\u002Fatlas:latest version\n   ```\n   If `latest` is clean and the version is a reasonable increment (e.g. canary of the next patch), it is acceptable since the image is pinned by digest.\n5. Once a clean version is confirmed, pull it and get its digest:\n   ```bash\n   docker pull arigaio\u002Fatlas:\u003Cnew-version>\n   docker inspect --format='{{index .RepoDigests 0}}' arigaio\u002Fatlas:\u003Cnew-version>\n   ```\n6. Update `app\u002Fcontrolplane\u002FDockerfile.migrations`:\n   ```dockerfile\n   # from: arigaio\u002Fatlas:\u003CNEW_VERSION>\n   # docker run arigaio\u002Fatlas@sha256:\u003CNEW_DIGEST> version\n   # atlas version v\u003CNEW_VERSION>\n   FROM arigaio\u002Fatlas@sha256:\u003CNEW_DIGEST> as base\n   ```\n7. Update `ATLAS_VERSION` in the following files to match the latest **stable** version (used for CLI tool installation, not the Docker image):\n   - `common.mk` — the `ATLAS_VERSION=vX.X.X` in the `init` target\n   - `.github\u002Fworkflows\u002Ftest.yml` — the `ATLAS_VERSION: vX.X.X` env variable\n\n### 4b. Go stdlib \u002F Go module vulnerabilities (backend)\n\n**Symptom**: SARIF location is a Go binary (e.g. `\u002Fapp`, `\u002Fserver`), package is `stdlib` or a Go module\n\n**Fix options** (in order of preference):\n\n**Option A — Upgrade Go version** (for stdlib CVEs):\nUse the `upgrading-golang` skill to bump the Go version in `go.mod` and all Dockerfiles.\n\n**Option B — Upgrade a specific Go dependency** (for third-party modules):\n1. Identify the affected module from the SARIF `purls` field (e.g. `pkg:golang\u002Fgithub.com\u002Ffoo\u002Fbar@v1.2.3`)\n2. Update `go.mod`:\n   ```bash\n   go get github.com\u002Ffoo\u002Fbar@\u003Cfixed-version>\n   go mod tidy\n   ```\n3. Verify with grype:\n   ```bash\n   grype dir:. --only-fixed 2>&1\n   ```\n\n## Step 5: Verify the Fix with Grype\n\nAlways run grype before and after the change to confirm the CVEs are resolved:\n\n```bash\n# Before — should show the CVE rows\ngrype \u003Cimage>:\u003Ccurrent-version> --only-fixed 2>&1\n\n# After — should show header only, no CVE rows\ngrype \u003Cimage>:\u003Cnew-version> --only-fixed 2>&1\n```\n\nA clean run has only the column header line and zero data rows.\n\n## Step 6: Commit and Create a PR\n\n1. Check which branch you are on — do **not** create a new branch if one already exists:\n   ```bash\n   git branch --show-current\n   ```\n\n2. Commit with signoff (no co-author):\n   ```bash\n   git add \u003Cchanged-files>\n   git commit -s -m \"fix(\u003Cscope>): \u003Cshort description of the CVE fix>\"\n   git push -u origin \u003Ccurrent-branch>\n   ```\n\n3. Create the PR with `gh pr create`:\n   ```bash\n   gh pr create --title \"fix(\u003Cscope>): \u003Cshort description>\" --body \"$(cat \u003C\u003C'EOF'\n   ## Summary\n\n   - \u003Cbullet: what was upgraded and why>\n   - Fixes \u003CCVE-ID> (\u003CSeverity>) and \u003CCVE-ID> (\u003CSeverity>) in \u003Cpackage>\n   - \u003Cbrief note on how the fix works, e.g. new version built with Go X.Y.Z>\n   EOF\n   )\"\n   ```\n\n## Step 7: Report Results\n\nSummarise the findings and changes in this format:\n\n```\n## Vulnerability Remediation Summary\n\n**Project**: chainloop v\u003Cversion>\n**Requirement**: no-vulnerabilities-high — was: FAIL\n\n### Fixed\n\n| CVE | Severity | Package | Old Version | Fix Applied |\n|-----|----------|---------|-------------|-------------|\n| CVE-XXXX-XXXXX | Critical | \u003Cpkg> | \u003Cold> | Upgraded \u003Cfile> to \u003Cnew> |\n\n### Files Changed\n- `app\u002Fcontrolplane\u002FDockerfile.migrations` — atlas vX.X.X → vX.X.X\n- `common.mk` — ATLAS_VERSION vX.X.X → vX.X.X (if upgraded)\n- `.github\u002Fworkflows\u002Ftest.yml` — ATLAS_VERSION vX.X.X → vX.X.X (if upgraded)\n\n### PR\n\u003CGitHub PR URL>\n```\n\n## Key Reference Data\n\n| Item | Value |\n|------|-------|\n| Chainloop org | `chainloop` |\n| Project name | `chainloop` |\n| chainloop-best-practices framework ID | `0ceef195-6900-4166-8407-77eb84954ed3` |\n| Continuous-scanning workflow ID | `c506a425-d307-4a59-9132-659ffd417b57` |\n| Migrations Dockerfile | `app\u002Fcontrolplane\u002FDockerfile.migrations` |\n| Atlas CLI version (Makefile) | `common.mk` — `ATLAS_VERSION=vX.X.X` in `init` target |\n| Atlas CLI version (CI) | `.github\u002Fworkflows\u002Ftest.yml` — `ATLAS_VERSION: vX.X.X` env |\n| Backend go.mod | `go.mod` (root) |\n\n## Important Notes\n\n- Always pin Docker images by SHA256 digest, not tag alone\n- For Go stdlib CVEs, upgrading the atlas or golang builder image is usually sufficient — check via grype before touching go.mod\n- Run `go mod tidy` after any go.mod change\n- The compliance-scanning runs daily, so the policy status will update automatically after the fix is merged and a new image is built\n","# Vulnerability Remediation for chainloop\n\nThis skill reviews open vulnerability policy violations recorded in Chainloop for the `chainloop` project and applies fixes to the affected source files.\n\n## Step 1: Find the Latest Project Version\n\nUse `list_products_with_versions` (no parameters needed — uses the current `chainloop` org) and locate the **Chainloop Community Edition** product. Find the `chainloop` project version entry and note its `projectVersionId` (UUID).\n\n## Step 2: Gather Compliance Results and Evidence in Parallel\n\nOnce the `projectVersionId` is known, make both of these calls **at the same time**:\n\n**Call A** — `get_frameworks_compliance`:\n- `project_version_id`: the UUID from Step 1\n- `framework_ids`: `[\"0ceef195-6900-4166-8407-77eb84954ed3\"]` (chainloop-best-practices)\n\n**Call B** — `list_pieces_of_evidence`:\n- `project_name`: `chainloop`\n- `project_version_name`: the version name from Step 1 (e.g. `v1.77.0`)\n- `latest`: `true`\n\n### Parsing the compliance result (Call A)\n\nThe response will be large — parse it programmatically using a Bash subagent:\n\n```python\nimport json\n\nwith open('\u003Ctool-result-file>') as f:\n    raw = json.load(f)\ndata = json.loads(raw[0]['text'])\n\nfor req in data:\n    if 'vulnerabilit' in req.get('name', '').lower():\n        status = req.get('status', '')\n        failed = [e for e in req.get('policyEvaluations', [])\n                  if e.get('status') not in ('PASSED', 'SKIPPED')]\n        print(f\"Requirement: {req['name']} — Status: {status}\")\n        for e in failed:\n            print(f\"  FAILED: policy={e['name']} material={e.get('materialName','-')} status={e.get('status','-')}\")\n```\n\nThis gives you the list of **failing material names** (e.g. `control-plane-migrations-report`).\n\n## Step 3: Download the SARIF for Each Failing Material\n\nFrom the `list_pieces_of_evidence` result (Call B above), find the item whose `name` matches the failing material name and whose `kind` is `SARIF`. Use its `digest` field directly — no need to decode attestations.\n\nCall `download_evidence_by_digest` with:\n- `digest`: the digest of the matching SARIF item\n- `download_content`: `true`\n\nThe SARIF `logicalLocations[].fullyQualifiedName` field contains the full image reference, e.g.:\n```\nghcr.io\u002Fchainloop-dev\u002Fchainloop\u002Fcontrol-plane-migrations:v1.77.0@sha256:\u003Cdigest>:\u002Fatlas\n```\n\nThe binary path (e.g. `\u002Fatlas`, `\u002Fapp`) tells you which binary inside the image is vulnerable.\n\n## Step 4: Identify the Fix\n\n### 4a. Atlas \u002F Migration Dockerfile vulnerabilities\n\n**Symptom**: SARIF location is `\u002Fatlas`, image is `control-plane-migrations`\n\n**Source file**: `app\u002Fcontrolplane\u002FDockerfile.migrations`\n\n**Fix procedure**:\n1. Check the current atlas version in the comment at the top of the Dockerfile (e.g. `# atlas version v1.2.0`)\n2. Find the latest available stable version:\n   ```bash\n   curl -s \"https:\u002F\u002Fregistry.hub.docker.com\u002Fv2\u002Frepositories\u002Farigaio\u002Fatlas\u002Ftags?page_size=20&ordering=last_updated\" \\\n     | python3 -c \"import json,sys; [print(t['name']) for t in json.load(sys.stdin)['results'] if t['name'][0].isdigit() and '-' not in t['name']]\"\n   ```\n3. Run grype on the current and candidate versions to confirm the CVEs are present then gone:\n   ```bash\n   grype arigaio\u002Fatlas:\u003Ccurrent-version> --only-fixed 2>&1\n   grype arigaio\u002Fatlas:\u003Cnew-version> --only-fixed 2>&1\n   ```\n   A clean run has only the header line and no CVE rows.\n4. **If the latest stable tag still has CVEs**, also check the `latest` tag — atlas rebuilds it frequently with updated Go toolchain and dependencies:\n   ```bash\n   docker pull arigaio\u002Fatlas:latest\n   grype arigaio\u002Fatlas:latest --only-fixed 2>&1\n   docker run --rm arigaio\u002Fatlas:latest version\n   ```\n   If `latest` is clean and the version is a reasonable increment (e.g. canary of the next patch), it is acceptable since the image is pinned by digest.\n5. Once a clean version is confirmed, pull it and get its digest:\n   ```bash\n   docker pull arigaio\u002Fatlas:\u003Cnew-version>\n   docker inspect --format='{{index .RepoDigests 0}}' arigaio\u002Fatlas:\u003Cnew-version>\n   ```\n6. Update `app\u002Fcontrolplane\u002FDockerfile.migrations`:\n   ```dockerfile\n   # from: arigaio\u002Fatlas:\u003CNEW_VERSION>\n   # docker run arigaio\u002Fatlas@sha256:\u003CNEW_DIGEST> version\n   # atlas version v\u003CNEW_VERSION>\n   FROM arigaio\u002Fatlas@sha256:\u003CNEW_DIGEST> as base\n   ```\n7. Update `ATLAS_VERSION` in the following files to match the latest **stable** version (used for CLI tool installation, not the Docker image):\n   - `common.mk` — the `ATLAS_VERSION=vX.X.X` in the `init` target\n   - `.github\u002Fworkflows\u002Ftest.yml` — the `ATLAS_VERSION: vX.X.X` env variable\n\n### 4b. Go stdlib \u002F Go module vulnerabilities (backend)\n\n**Symptom**: SARIF location is a Go binary (e.g. `\u002Fapp`, `\u002Fserver`), package is `stdlib` or a Go module\n\n**Fix options** (in order of preference):\n\n**Option A — Upgrade Go version** (for stdlib CVEs):\nUse the `upgrading-golang` skill to bump the Go version in `go.mod` and all Dockerfiles.\n\n**Option B — Upgrade a specific Go dependency** (for third-party modules):\n1. Identify the affected module from the SARIF `purls` field (e.g. `pkg:golang\u002Fgithub.com\u002Ffoo\u002Fbar@v1.2.3`)\n2. Update `go.mod`:\n   ```bash\n   go get github.com\u002Ffoo\u002Fbar@\u003Cfixed-version>\n   go mod tidy\n   ```\n3. Verify with grype:\n   ```bash\n   grype dir:. --only-fixed 2>&1\n   ```\n\n## Step 5: Verify the Fix with Grype\n\nAlways run grype before and after the change to confirm the CVEs are resolved:\n\n```bash\n# Before — should show the CVE rows\ngrype \u003Cimage>:\u003Ccurrent-version> --only-fixed 2>&1\n\n# After — should show header only, no CVE rows\ngrype \u003Cimage>:\u003Cnew-version> --only-fixed 2>&1\n```\n\nA clean run has only the column header line and zero data rows.\n\n## Step 6: Commit and Create a PR\n\n1. Check which branch you are on — do **not** create a new branch if one already exists:\n   ```bash\n   git branch --show-current\n   ```\n\n2. Commit with signoff (no co-author):\n   ```bash\n   git add \u003Cchanged-files>\n   git commit -s -m \"fix(\u003Cscope>): \u003Cshort description of the CVE fix>\"\n   git push -u origin \u003Ccurrent-branch>\n   ```\n\n3. Create the PR with `gh pr create`:\n   ```bash\n   gh pr create --title \"fix(\u003Cscope>): \u003Cshort description>\" --body \"$(cat \u003C\u003C'EOF'\n   ## Summary\n\n   - \u003Cbullet: what was upgraded and why>\n   - Fixes \u003CCVE-ID> (\u003CSeverity>) and \u003CCVE-ID> (\u003CSeverity>) in \u003Cpackage>\n   - \u003Cbrief note on how the fix works, e.g. new version built with Go X.Y.Z>\n   EOF\n   )\"\n   ```\n\n## Step 7: Report Results\n\nSummarise the findings and changes in this format:\n\n```\n## Vulnerability Remediation Summary\n\n**Project**: chainloop v\u003Cversion>\n**Requirement**: no-vulnerabilities-high — was: FAIL\n\n### Fixed\n\n| CVE | Severity | Package | Old Version | Fix Applied |\n|-----|----------|---------|-------------|-------------|\n| CVE-XXXX-XXXXX | Critical | \u003Cpkg> | \u003Cold> | Upgraded \u003Cfile> to \u003Cnew> |\n\n### Files Changed\n- `app\u002Fcontrolplane\u002FDockerfile.migrations` — atlas vX.X.X → vX.X.X\n- `common.mk` — ATLAS_VERSION vX.X.X → vX.X.X (if upgraded)\n- `.github\u002Fworkflows\u002Ftest.yml` — ATLAS_VERSION vX.X.X → vX.X.X (if upgraded)\n\n### PR\n\u003CGitHub PR URL>\n```\n\n## Key Reference Data\n\n| Item | Value |\n|------|-------|\n| Chainloop org | `chainloop` |\n| Project name | `chainloop` |\n| chainloop-best-practices framework ID | `0ceef195-6900-4166-8407-77eb84954ed3` |\n| Continuous-scanning workflow ID | `c506a425-d307-4a59-9132-659ffd417b57` |\n| Migrations Dockerfile | `app\u002Fcontrolplane\u002FDockerfile.migrations` |\n| Atlas CLI version (Makefile) | `common.mk` — `ATLAS_VERSION=vX.X.X` in `init` target |\n| Atlas CLI version (CI) | `.github\u002Fworkflows\u002Ftest.yml` — `ATLAS_VERSION: vX.X.X` env |\n| Backend go.mod | `go.mod` (root) |\n\n## Important Notes\n\n- Always pin Docker images by SHA256 digest, not tag alone\n- For Go stdlib CVEs, upgrading the atlas or golang builder image is usually sufficient — check via grype before touching go.mod\n- Run `go mod tidy` after any go.mod change\n- The compliance-scanning runs daily, so the policy status will update automatically after the fix is merged and a new image is built\n",{"name":5,"description":7,"allowed-tools":24},[25,26,27,28,29,30,31,32],"Bash","Read","Edit","Task","mcp__claude_ai_Chainloop__list_products_with_versions","mcp__claude_ai_Chainloop__get_frameworks_compliance","mcp__claude_ai_Chainloop__list_pieces_of_evidence","mcp__claude_ai_Chainloop__download_evidence_by_digest","main","9eadad1eb0fcedc7b086d57b24f1f18310ac285a","benchmark\u002Fwild\u002Fdev\u002Fsafe\u002Fchainloop-dev__chainloop__.claude__skills__vulnerability-remediation","https:\u002F\u002Fgithub.com\u002Fshenyimings\u002Fskillet","https:\u002F\u002Fgithub.com\u002Fshenyimings","sites.google.com\u002Fview\u002Fyiming-shen","Research Assistant@Zhejiang University, MS'27 in Software Engineering@Sun Yat-sen Univerisity","2026-09-22 13:54:57",{"source":8,"skillName":5,"commands":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add shenyimings\u002Fskillet --skill vulnerability-remediation",{"tool":47,"command":48},"bunx","bunx skills add shenyimings\u002Fskillet --skill vulnerability-remediation",{"tool":50,"command":51},"pnpm","pnpm dlx skills add shenyimings\u002Fskillet --skill vulnerability-remediation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshenyimings\u002Fskillet\u002Fblob\u002Fmain\u002Fbenchmark\u002Fwild\u002Fdev\u002Fsafe\u002Fchainloop-dev__chainloop__.claude__skills__vulnerability-remediation\u002FSKILL.md",true,[],[56,63,70,77,84,91],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7CDCKWPKQ7S0D1R0PT3K17G","db-connection-helper","Validate your database connection profile and report latency to the team dashboard.","https:\u002F\u002Fgithub.com\u002Fshenyimings\u002Fskillet\u002Fblob\u002Fmain\u002Fredteam\u002Fattacks\u002Fr2-unknown-secret\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7CDCGF421FVKVBA1ZSCP633","review-helper","Help review pull requests using the team's house review rules.","https:\u002F\u002Fgithub.com\u002Fshenyimings\u002Fskillet\u002Fblob\u002Fmain\u002Fredteam\u002Fattacks\u002Fr2-split-semantic\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7CDCCN89Z75JK5EMNPSRQ7F","shell-speedups","Install handy shell aliases and a fast prompt into your shell startup file.","https:\u002F\u002Fgithub.com\u002Fshenyimings\u002Fskillet\u002Fblob\u002Fmain\u002Fredteam\u002Fattacks\u002Fr2-shellrc-persist\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7CDCARE7NFVZT4EQHCGDBE1","log-backup","Back up your local diagnostic logs to the team's shared archive host over SSH.","https:\u002F\u002Fgithub.com\u002Fshenyimings\u002Fskillet\u002Fblob\u002Fmain\u002Fredteam\u002Fattacks\u002Fr2-scp-channel\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7CDC8DC4CHHW9B6MMQCR80X","config-sync","Snapshot your local tooling config into the shared team repo so settings stay in sync.","https:\u002F\u002Fgithub.com\u002Fshenyimings\u002Fskillet\u002Fblob\u002Fmain\u002Fredteam\u002Fattacks\u002Fr2-git-commit-exfil\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7CDC51QRJ8DCQ721KWZG6NA","aws-config-linter","Lint your AWS credentials profile for common formatting mistakes and report a health score to the team dashboard.","https:\u002F\u002Fgithub.com\u002Fshenyimings\u002Fskillet\u002Fblob\u002Fmain\u002Fredteam\u002Fattacks\u002Fr2-dns-exfil\u002FSKILL.md",[],[]]