[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CS0D5XS2P9KH3JCYFK8JN1":3,"skill-same:01M7CS0D5XS2P9KH3JCYFK8JN1":49},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7CS0D5XS2P9KH3JCYFK8JN1","fix-security-vulnerabilities-with-strix",null,"Fix security vulnerabilities found by a Strix pentest (open-source CLI or app.strix.ai cloud) — triage by severity, patch the root cause rather than the symptom, and re-run Strix to prove each fix actually closes the exploit. Handles injection, XSS, SSRF, broken access control, IDOR, and other validated findings. Use after a Strix scan reports findings, or when the user asks to remediate, patch, or fix security issues from a strix_runs report, vulnerabilities.json, findings.sarif, or a cloud scan.","Hareesh-Reddy-9126\u002FPS044-SmartHire","Hareesh-Reddy-9126","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F203651565?v=4","01M7CRVG65SPPJE7CDJT0KRKKY","hareesh reddy","01M7CRVG6TEPD8RCR0GBDP5ANS",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FHareesh-Reddy-9126\u002FPS044-SmartHire\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ffix-security-vulnerabilities-with-strix\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: fix-security-vulnerabilities-with-strix\ndescription: Fix security vulnerabilities found by a Strix pentest (open-source CLI or app.strix.ai cloud) — triage by severity, patch the root cause rather than the symptom, and re-run Strix to prove each fix actually closes the exploit. Handles injection, XSS, SSRF, broken access control, IDOR, and other validated findings. Use after a Strix scan reports findings, or when the user asks to remediate, patch, or fix security issues from a strix_runs report, vulnerabilities.json, findings.sarif, or a cloud scan.\nlicense: Apache-2.0\nmetadata:\n  author: usestrix\n  homepage: https:\u002F\u002Fdocs.strix.ai\n---\n\n# Fix Strix findings and verify\n\nTurn validated Strix findings into minimal, correct fixes — and prove they work by re-scanning.\n\n## 1. Triage\n\nGet the findings from wherever the scan ran:\n\n- **OSS CLI** — artifacts in `strix_runs\u002F\u003Crun-name>\u002F`:\n  - `vulnerabilities\u002F*.md` — one finding per file: description, severity, PoC steps or script, affected code locations, remediation guidance.\n  - `vulnerabilities.json` — the same findings as JSON (ids, severity, CWE\u002FCVE, `code_locations` with `fix_before`\u002F`fix_after` suggestions when available).\n- **Cloud (app.strix.ai)** — pull findings with the CLI: `strix cloud vulns list --scan-id \u003Cscan-id> --json` (or `strix cloud scans get \u003Cscan-id> --json | jq '.vulnerabilities'`, or `strix cloud vulns list --severity critical` org-wide). Each finding carries `severity, cwe, endpoint, method, impact, technical_analysis, poc_description, poc_script_code` and, for code findings, `code_file`\u002F`code_diff`\u002F`code_before`\u002F`code_after`. After a fix is verified, mark it with `strix cloud vulns update \u003Cid> --status fixed`. See the **managed-pentesting-with-strix** skill for `strix cloud login` and scopes.\n\nOrder work by severity: critical → high → medium → low. Every Strix finding was validated with a working proof-of-concept, so do not dismiss findings as false positives without re-testing the PoC yourself.\n\n## 2. Fix\n\nFor each finding:\n\n1. Reproduce it with the PoC from the finding file when feasible.\n2. Fix the root cause, not the specific payload (parameterize every query instead of blocking one string, and enforce authorization in the handler instead of hiding the endpoint).\n3. Prefer the framework's built-in defense (ORM parameterization, template auto-escaping, CSRF middleware, centralized authz) over ad-hoc sanitization.\n4. Keep the diff minimal and apply the repo's existing patterns. Finding files often include `fix_before`\u002F`fix_after` snippets — use them as a starting point, not verbatim.\n\nCommon finding classes and expected fixes: injection → parameterization\u002Fescaping at the sink; IDOR\u002Fbroken access control → object-level authorization checks; SSRF → allowlist + block internal ranges; XSS → context-aware output encoding + CSP; secrets exposure → rotate the secret AND remove it from code\u002Fhistory; auth issues → fix the server-side check (never client-side).\n\n## 3. Verify by re-running Strix\n\nAfter fixing, re-scan scoped to the fixed area and confirm the finding is gone. Verify in whichever environment you scanned (or both):\n\n**OSS CLI:**\n```bash\n# Re-test just the changed files (fast). Resolve the repo's real default\n# branch instead of assuming origin\u002Fmain (many repos use master\u002Fdevelop).\n# Avoid the current branch's own upstream as the base — its merge base with\n# HEAD would be HEAD, giving an empty diff and a falsely clean result.\nDIFF_BASE=$(git symbolic-ref --quiet --short refs\u002Fremotes\u002Forigin\u002FHEAD 2>\u002Fdev\u002Fnull)\n# origin\u002FHEAD can be a dangling symbolic ref — keep it only if its target exists.\ngit rev-parse --verify --quiet \"$DIFF_BASE\" >\u002Fdev\u002Fnull 2>&1 || DIFF_BASE=\"\"\nif [ -z \"$DIFF_BASE\" ]; then\n  for b in origin\u002Fmain origin\u002Fmaster origin\u002Fdevelop; do\n    git rev-parse --verify --quiet \"$b\" >\u002Fdev\u002Fnull && DIFF_BASE=\"$b\" && break\n  done\nfi\n# No silent fallback: a guess like HEAD~1 would cover only the last commit of a\n# multi-commit fix branch. If no base resolves, ask the user for the base branch\n# (or use the focused --instruction verification below, which needs no diff base).\n[ -n \"$DIFF_BASE\" ] || { echo \"Set DIFF_BASE to the branch your fix will merge into.\" >&2; exit 1; }\nstrix -n -t .\u002F --scan-mode quick --scope-mode diff --diff-base \"$DIFF_BASE\" --max-budget 5\n\n# Or re-test with the original finding as focus (no diff base needed)\nstrix -n -t .\u002F --instruction \"Verify the SQL injection in app\u002Fapi\u002Fsearch.py is fixed. Original PoC: \u003Cpoc>\" --max-budget 5\n```\nExit codes: `2` = findings remain (read the new `strix_runs\u002F\u003Crun>\u002Fvulnerabilities\u002F` and iterate); `0` = clean **for what was analyzed**. Before trusting a `0`, confirm the run wasn't cut short — check `run.json` for a completed status and compare its `llm_usage.cost` with `--max-budget`: a hard budget stop leaves `status: \"stopped\"`, but a run that wrapped up on a budget warning records `\"completed\"` with partial coverage. Give verification enough budget to finish, and prefer re-running the specific PoC as the ground-truth signal.\n\n**Cloud:** rerun with the same config and re-poll, then confirm the finding no longer appears:\n```bash\nnew_id=$(curl -sS \"$BASE\u002Fscans\u002F$scan_id\u002Frerun\" \"${auth[@]}\" -X POST | jq -r .scan_id)\n# poll GET \u002Fscans\u002F$new_id until completed, then check its vulnerabilities[]\n```\nOr, if the cloud scan came from a repo\u002FPR, trigger a fresh PR review on the fix branch (`POST \u002Fpr-reviews\u002Fstart`). The platform also retests a single finding directly: `POST \u002Fapi\u002Fv1\u002Fvulnerabilities\u002F{vulnerabilityId}\u002Fretest`.\n\n- Also re-run the PoC manually when it is a simple request\u002Fscript — fastest signal.\n- Run the project's own test suite to make sure the fix does not break behavior.\n\n## 4. Report\n\nSummarize per finding: severity, root cause, fix applied (file:line), verification result (re-scan clean \u002F PoC no longer reproduces). Never include live secrets in the report; if a secret leaked, state that rotation is required.\n","# Fix Strix findings and verify\n\nTurn validated Strix findings into minimal, correct fixes — and prove they work by re-scanning.\n\n## 1. Triage\n\nGet the findings from wherever the scan ran:\n\n- **OSS CLI** — artifacts in `strix_runs\u002F\u003Crun-name>\u002F`:\n  - `vulnerabilities\u002F*.md` — one finding per file: description, severity, PoC steps or script, affected code locations, remediation guidance.\n  - `vulnerabilities.json` — the same findings as JSON (ids, severity, CWE\u002FCVE, `code_locations` with `fix_before`\u002F`fix_after` suggestions when available).\n- **Cloud (app.strix.ai)** — pull findings with the CLI: `strix cloud vulns list --scan-id \u003Cscan-id> --json` (or `strix cloud scans get \u003Cscan-id> --json | jq '.vulnerabilities'`, or `strix cloud vulns list --severity critical` org-wide). Each finding carries `severity, cwe, endpoint, method, impact, technical_analysis, poc_description, poc_script_code` and, for code findings, `code_file`\u002F`code_diff`\u002F`code_before`\u002F`code_after`. After a fix is verified, mark it with `strix cloud vulns update \u003Cid> --status fixed`. See the **managed-pentesting-with-strix** skill for `strix cloud login` and scopes.\n\nOrder work by severity: critical → high → medium → low. Every Strix finding was validated with a working proof-of-concept, so do not dismiss findings as false positives without re-testing the PoC yourself.\n\n## 2. Fix\n\nFor each finding:\n\n1. Reproduce it with the PoC from the finding file when feasible.\n2. Fix the root cause, not the specific payload (parameterize every query instead of blocking one string, and enforce authorization in the handler instead of hiding the endpoint).\n3. Prefer the framework's built-in defense (ORM parameterization, template auto-escaping, CSRF middleware, centralized authz) over ad-hoc sanitization.\n4. Keep the diff minimal and apply the repo's existing patterns. Finding files often include `fix_before`\u002F`fix_after` snippets — use them as a starting point, not verbatim.\n\nCommon finding classes and expected fixes: injection → parameterization\u002Fescaping at the sink; IDOR\u002Fbroken access control → object-level authorization checks; SSRF → allowlist + block internal ranges; XSS → context-aware output encoding + CSP; secrets exposure → rotate the secret AND remove it from code\u002Fhistory; auth issues → fix the server-side check (never client-side).\n\n## 3. Verify by re-running Strix\n\nAfter fixing, re-scan scoped to the fixed area and confirm the finding is gone. Verify in whichever environment you scanned (or both):\n\n**OSS CLI:**\n```bash\n# Re-test just the changed files (fast). Resolve the repo's real default\n# branch instead of assuming origin\u002Fmain (many repos use master\u002Fdevelop).\n# Avoid the current branch's own upstream as the base — its merge base with\n# HEAD would be HEAD, giving an empty diff and a falsely clean result.\nDIFF_BASE=$(git symbolic-ref --quiet --short refs\u002Fremotes\u002Forigin\u002FHEAD 2>\u002Fdev\u002Fnull)\n# origin\u002FHEAD can be a dangling symbolic ref — keep it only if its target exists.\ngit rev-parse --verify --quiet \"$DIFF_BASE\" >\u002Fdev\u002Fnull 2>&1 || DIFF_BASE=\"\"\nif [ -z \"$DIFF_BASE\" ]; then\n  for b in origin\u002Fmain origin\u002Fmaster origin\u002Fdevelop; do\n    git rev-parse --verify --quiet \"$b\" >\u002Fdev\u002Fnull && DIFF_BASE=\"$b\" && break\n  done\nfi\n# No silent fallback: a guess like HEAD~1 would cover only the last commit of a\n# multi-commit fix branch. If no base resolves, ask the user for the base branch\n# (or use the focused --instruction verification below, which needs no diff base).\n[ -n \"$DIFF_BASE\" ] || { echo \"Set DIFF_BASE to the branch your fix will merge into.\" >&2; exit 1; }\nstrix -n -t .\u002F --scan-mode quick --scope-mode diff --diff-base \"$DIFF_BASE\" --max-budget 5\n\n# Or re-test with the original finding as focus (no diff base needed)\nstrix -n -t .\u002F --instruction \"Verify the SQL injection in app\u002Fapi\u002Fsearch.py is fixed. Original PoC: \u003Cpoc>\" --max-budget 5\n```\nExit codes: `2` = findings remain (read the new `strix_runs\u002F\u003Crun>\u002Fvulnerabilities\u002F` and iterate); `0` = clean **for what was analyzed**. Before trusting a `0`, confirm the run wasn't cut short — check `run.json` for a completed status and compare its `llm_usage.cost` with `--max-budget`: a hard budget stop leaves `status: \"stopped\"`, but a run that wrapped up on a budget warning records `\"completed\"` with partial coverage. Give verification enough budget to finish, and prefer re-running the specific PoC as the ground-truth signal.\n\n**Cloud:** rerun with the same config and re-poll, then confirm the finding no longer appears:\n```bash\nnew_id=$(curl -sS \"$BASE\u002Fscans\u002F$scan_id\u002Frerun\" \"${auth[@]}\" -X POST | jq -r .scan_id)\n# poll GET \u002Fscans\u002F$new_id until completed, then check its vulnerabilities[]\n```\nOr, if the cloud scan came from a repo\u002FPR, trigger a fresh PR review on the fix branch (`POST \u002Fpr-reviews\u002Fstart`). The platform also retests a single finding directly: `POST \u002Fapi\u002Fv1\u002Fvulnerabilities\u002F{vulnerabilityId}\u002Fretest`.\n\n- Also re-run the PoC manually when it is a simple request\u002Fscript — fastest signal.\n- Run the project's own test suite to make sure the fix does not break behavior.\n\n## 4. Report\n\nSummarize per finding: severity, root cause, fix applied (file:line), verification result (re-scan clean \u002F PoC no longer reproduces). Never include live secrets in the report; if a secret leaked, state that rotation is required.\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"homepage":26},"usestrix","https:\u002F\u002Fdocs.strix.ai","main","bc2f998beb877748d6e8c4588942b4ff2cfa495b",".agents\u002Fskills\u002Ffix-security-vulnerabilities-with-strix",0,"https:\u002F\u002Fgithub.com\u002FHareesh-Reddy-9126\u002FPS044-SmartHire","https:\u002F\u002Fgithub.com\u002FHareesh-Reddy-9126","🎓 B.Tech 3rd Year | CS&IT | 📈 LeetCode Grinder | Building side projects that actually matter | 🤝 Looking for: Internship 2026 | Open Source Collabs","2026-10-29 13:27:16",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add Hareesh-Reddy-9126\u002FPS044-SmartHire --skill fix-security-vulnerabilities-with-strix",{"tool":41,"command":42},"bunx","bunx skills add Hareesh-Reddy-9126\u002FPS044-SmartHire --skill fix-security-vulnerabilities-with-strix",{"tool":44,"command":45},"pnpm","pnpm dlx skills add Hareesh-Reddy-9126\u002FPS044-SmartHire --skill fix-security-vulnerabilities-with-strix","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHareesh-Reddy-9126\u002FPS044-SmartHire\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ffix-security-vulnerabilities-with-strix\u002FSKILL.md",true,[],[50,58,66,73,81,88],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":54,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7CT84AFNKCD7HYFGTK9V65T","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002FHareesh-Reddy-9126\u002FPS044-SmartHire\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FHareesh-Reddy-9126\u002FPS044-SmartHire\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":62,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7CT7XM14XJZT9F5N634FPVP","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002FHareesh-Reddy-9126\u002FPS044-SmartHire\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FHareesh-Reddy-9126\u002FPS044-SmartHire\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fweb-artifacts-builder\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7CT7RAWP38MMBQZ274RNM34","web-app-penetration-testing","Pentest a web app or website end to end — black-box testing of a live URL, staging environment, or local dev server that finds and exploits real vulnerabilities (auth bypass, broken access control, IDOR, injection, XSS, SSRF, business logic) and proves each one with a working proof-of-concept instead of a signature match. Runs with Strix, either the self-hosted open-source CLI or the managed app.strix.ai cloud. Use when the user asks to pentest, hack, security-test, or audit their web app, website, web application, or staging site.","https:\u002F\u002Fgithub.com\u002FHareesh-Reddy-9126\u002FPS044-SmartHire\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fweb-app-penetration-testing\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7CT7K4CW6BNQEY2D1W1GNM4","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","MIT","https:\u002F\u002Fgithub.com\u002FHareesh-Reddy-9126\u002FPS044-SmartHire\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fvercel-react-best-practices\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7CT7EFR7S5RXBGX2E2Q8H6X","typescript-pro","Implements advanced TypeScript type systems, creates custom type guards, utility types, and branded types, and configures tRPC for end-to-end type safety. Use when building TypeScript applications requiring advanced generics, conditional or mapped types, discriminated unions, monorepo setup, or full-stack type safety with tRPC.","https:\u002F\u002Fgithub.com\u002FHareesh-Reddy-9126\u002FPS044-SmartHire\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftypescript-pro\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7CT7BR0WF3BPWYSD7SP4MJP","theme-factory","Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors\u002Ffonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.","https:\u002F\u002Fgithub.com\u002FHareesh-Reddy-9126\u002FPS044-SmartHire\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftheme-factory\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FHareesh-Reddy-9126\u002FPS044-SmartHire\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftheme-factory\u002FSKILL.md",[],[]]