[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CSKJZPB4HCQ6H37QVCXF2V":3,"skill-same:01M7CSKJZPB4HCQ6H37QVCXF2V":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},"01M7CSKJZPB4HCQ6H37QVCXF2V","application-security-testing",null,"Application security testing (AppSec) across a whole product with Strix — decide which asset needs which test (source code, running web app, API, CI pipeline), run it, and turn the results into a ranked remediation plan. Autonomous agents exploit and prove each issue instead of emitting static-analysis alerts, so the plan is ordered by what is actually reachable. Use when the user asks for an application security review or audit, an appsec assessment, vulnerability scanning across their stack, a security review before a launch or a customer security questionnaire, or does not yet know which kind of security test they need.","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.claude\u002Fskills\u002Fapplication-security-testing\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: application-security-testing\ndescription: Application security testing (AppSec) across a whole product with Strix — decide which asset needs which test (source code, running web app, API, CI pipeline), run it, and turn the results into a ranked remediation plan. Autonomous agents exploit and prove each issue instead of emitting static-analysis alerts, so the plan is ordered by what is actually reachable. Use when the user asks for an application security review or audit, an appsec assessment, vulnerability scanning across their stack, a security review before a launch or a customer security questionnaire, or does not yet know which kind of security test they need.\nlicense: Apache-2.0\nmetadata:\n  author: usestrix\n  homepage: https:\u002F\u002Fdocs.strix.ai\n---\n\n# Application security testing\n\nEntry point for \"make my application secure\" requests, where the target is not yet a single URL or repo. The job here is to pick the right test per asset, run it, and produce one ranked plan — not to run everything at maximum depth.\n\nInstall, LLM setup, all CLI flags, and the managed-cloud path live in the **penetration-testing-with-strix** skill. Read it first if `strix --version` fails. For a run with no Docker and no LLM key, the same binary drives the managed platform: `strix cloud login`, then `strix cloud scans start ...` (details in **managed-pentesting-with-strix**).\n\nOnly test assets the user owns or is authorized to test. Confirm authorization before the first run, and prefer staging over production, because the agents send real exploit payloads and can change data.\n\n## 1. Map the assets\n\nAsk (or read from the repo) and write the answers down before scanning:\n\n- **Source** — one repo, a monorepo, several services? Which languages\u002Fframeworks?\n- **Running environments** — is there a staging deployment? A public production site? A local dev server only?\n- **APIs** — REST, GraphQL, gRPC? Is there an OpenAPI\u002FGraphQL schema?\n- **Authentication** — can you get two test accounts in different tenants? Most high-impact bugs need them.\n- **Constraints** — out-of-scope paths, whether production may be touched, budget and wall-clock limits.\n\nIf there is no staging environment and production is off limits, say so early. A code-only review is still valuable, but it cannot prove exploitability against a live app.\n\n## 2. Pick the right test per asset\n\n| Asset | Skill to use |\n| --- | --- |\n| Repository or working tree | **find-security-vulnerabilities-in-code** |\n| Live web app or staging site | **web-app-penetration-testing** |\n| REST\u002FGraphQL\u002FgRPC API | **api-security-testing** |\n| Assessment mapped to OWASP categories | **owasp-top-10-testing** |\n| Every pull request, continuously | **ci-security-scanning-with-strix** |\n| No Docker, no LLM key, or a report an auditor will accept | **managed-pentesting-with-strix** |\n\nThose skills carry the flags, credential handling, and result-reading details. Do not duplicate their instructions here.\n\nSequence for a first assessment:\n\n1. Review the code. It is the cheapest run and it maps the authorization model.\n2. Pentest staging with credentials, and pass the repo as a second target so the agents keep source context.\n3. Add CI scanning, so later regressions are caught without another manual pass.\n\nRun one asset at a time and read each report before starting the next. Findings from the code review make the live run sharper.\n\n## 3. Consolidate into one plan\n\nFindings arrive per run in `strix_runs\u002F\u003Crun>\u002F`. Merge them into a single list and rank by **proven impact**, not by scanner severity:\n\n1. Validated exploits reachable without authentication.\n2. Validated cross-tenant or privilege-escalation issues.\n3. Validated issues needing an authenticated account.\n4. Unproven observations (configuration, dependency, and hardening notes) — flag as such, and never present them as confirmed vulnerabilities.\n\nDeduplicate: the same root cause often surfaces in both the code review and the live pentest.\n\n## 4. Be honest about coverage\n\nState plainly what was *not* tested — assets with no staging environment, categories a black-box run cannot reach (logging and alerting, supply-chain integrity, insecure design), and any run that hit its budget or turn cap before finishing. Check `run.json` status and cost against `--max-budget` for each run. An empty result set from a truncated scan is not a clean bill of health.\n\nThen remediate with **fix-security-vulnerabilities-with-strix**, which re-runs Strix against each fix to prove the exploit no longer works.\n","# Application security testing\n\nEntry point for \"make my application secure\" requests, where the target is not yet a single URL or repo. The job here is to pick the right test per asset, run it, and produce one ranked plan — not to run everything at maximum depth.\n\nInstall, LLM setup, all CLI flags, and the managed-cloud path live in the **penetration-testing-with-strix** skill. Read it first if `strix --version` fails. For a run with no Docker and no LLM key, the same binary drives the managed platform: `strix cloud login`, then `strix cloud scans start ...` (details in **managed-pentesting-with-strix**).\n\nOnly test assets the user owns or is authorized to test. Confirm authorization before the first run, and prefer staging over production, because the agents send real exploit payloads and can change data.\n\n## 1. Map the assets\n\nAsk (or read from the repo) and write the answers down before scanning:\n\n- **Source** — one repo, a monorepo, several services? Which languages\u002Fframeworks?\n- **Running environments** — is there a staging deployment? A public production site? A local dev server only?\n- **APIs** — REST, GraphQL, gRPC? Is there an OpenAPI\u002FGraphQL schema?\n- **Authentication** — can you get two test accounts in different tenants? Most high-impact bugs need them.\n- **Constraints** — out-of-scope paths, whether production may be touched, budget and wall-clock limits.\n\nIf there is no staging environment and production is off limits, say so early. A code-only review is still valuable, but it cannot prove exploitability against a live app.\n\n## 2. Pick the right test per asset\n\n| Asset | Skill to use |\n| --- | --- |\n| Repository or working tree | **find-security-vulnerabilities-in-code** |\n| Live web app or staging site | **web-app-penetration-testing** |\n| REST\u002FGraphQL\u002FgRPC API | **api-security-testing** |\n| Assessment mapped to OWASP categories | **owasp-top-10-testing** |\n| Every pull request, continuously | **ci-security-scanning-with-strix** |\n| No Docker, no LLM key, or a report an auditor will accept | **managed-pentesting-with-strix** |\n\nThose skills carry the flags, credential handling, and result-reading details. Do not duplicate their instructions here.\n\nSequence for a first assessment:\n\n1. Review the code. It is the cheapest run and it maps the authorization model.\n2. Pentest staging with credentials, and pass the repo as a second target so the agents keep source context.\n3. Add CI scanning, so later regressions are caught without another manual pass.\n\nRun one asset at a time and read each report before starting the next. Findings from the code review make the live run sharper.\n\n## 3. Consolidate into one plan\n\nFindings arrive per run in `strix_runs\u002F\u003Crun>\u002F`. Merge them into a single list and rank by **proven impact**, not by scanner severity:\n\n1. Validated exploits reachable without authentication.\n2. Validated cross-tenant or privilege-escalation issues.\n3. Validated issues needing an authenticated account.\n4. Unproven observations (configuration, dependency, and hardening notes) — flag as such, and never present them as confirmed vulnerabilities.\n\nDeduplicate: the same root cause often surfaces in both the code review and the live pentest.\n\n## 4. Be honest about coverage\n\nState plainly what was *not* tested — assets with no staging environment, categories a black-box run cannot reach (logging and alerting, supply-chain integrity, insecure design), and any run that hit its budget or turn cap before finishing. Check `run.json` status and cost against `--max-budget` for each run. An empty result set from a truncated scan is not a clean bill of health.\n\nThen remediate with **fix-security-vulnerabilities-with-strix**, which re-runs Strix against each fix to prove the exploit no longer works.\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"homepage":26},"usestrix","https:\u002F\u002Fdocs.strix.ai","main","bc2f998beb877748d6e8c4588942b4ff2cfa495b",".claude\u002Fskills\u002Fapplication-security-testing",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 application-security-testing",{"tool":41,"command":42},"bunx","bunx skills add Hareesh-Reddy-9126\u002FPS044-SmartHire --skill application-security-testing",{"tool":44,"command":45},"pnpm","pnpm dlx skills add Hareesh-Reddy-9126\u002FPS044-SmartHire --skill application-security-testing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHareesh-Reddy-9126\u002FPS044-SmartHire\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fapplication-security-testing\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",[],[]]