[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CSKCG2P55RJN4B82NJ9RDT":3,"skill-same:01M7CSKCG2P55RJN4B82NJ9RDT":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},"01M7CSKCG2P55RJN4B82NJ9RDT","api-security-testing",null,"Security-test a REST, GraphQL, or gRPC API with Strix — autonomous agents that enumerate endpoints from an OpenAPI\u002FGraphQL schema (or by crawling), then actually exploit the API-specific vulnerability classes in the OWASP API Security Top 10 (2023) — broken object-level authorization (BOLA\u002FIDOR), broken object property level authorization (excessive data exposure and mass assignment), broken function-level authorization, unrestricted resource consumption, SSRF, injection, and auth\u002Ftoken flaws. Every finding comes with a working proof-of-concept request. Use when the user asks to pentest, security-test, audit, or find vulnerabilities in an API, endpoint, or backend service.","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\u002Fapi-security-testing\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: api-security-testing\ndescription: Security-test a REST, GraphQL, or gRPC API with Strix — autonomous agents that enumerate endpoints from an OpenAPI\u002FGraphQL schema (or by crawling), then actually exploit the API-specific vulnerability classes in the OWASP API Security Top 10 (2023) — broken object-level authorization (BOLA\u002FIDOR), broken object property level authorization (excessive data exposure and mass assignment), broken function-level authorization, unrestricted resource consumption, SSRF, injection, and auth\u002Ftoken flaws. Every finding comes with a working proof-of-concept request. Use when the user asks to pentest, security-test, audit, or find vulnerabilities in an API, endpoint, or backend service.\nlicense: Apache-2.0\nmetadata:\n  author: usestrix\n  homepage: https:\u002F\u002Fdocs.strix.ai\n---\n\n# Security-test an API\n\nAPIs fail differently from web UIs: there is no rendered surface to crawl, the interesting bugs are authorization-shaped rather than injection-shaped, and the same endpoint behaves differently per token. This workflow targets those specifics with Strix's autonomous agents, using the current [OWASP API Security Top 10 (2023)](https:\u002F\u002Fowasp.org\u002FAPI-Security\u002Feditions\u002F2023\u002Fen\u002F0x11-t10\u002F) as the coverage checklist. For the web-app equivalent, the current edition is the OWASP Top 10:2025 — see **owasp-top-10-testing**.\n\nInstall, LLM setup, full CLI flags, and the managed-cloud path are in the **penetration-testing-with-strix** skill. Read it if `strix --version` fails or the target is not an API. 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\n## 1. Gather what the agents need\n\nAPIs are near-impossible to test blind, so collect first:\n\n| Input | Why it matters |\n|---|---|\n| **Schema** — OpenAPI\u002FSwagger file, Postman collection, GraphQL endpoint (introspection), or a gRPC `.proto` | Turns guesswork into full endpoint enumeration. Biggest single win in coverage. An OpenAPI\u002FSwagger or Postman spec (`.json`\u002F`.yaml`\u002F`.yml`) is a target Strix takes directly; a `.proto` is not, so pass it with `--workspace-file`. |\n| **Two sets of credentials\u002Ftokens**, ideally in different tenants | BOLA\u002FIDOR — API1:2023, still the #1 API risk — can only be *proven* by accessing tenant A's objects with tenant B's token. |\n| **A low-privilege and a high-privilege token** | Required to prove broken function-level authorization (API5:2023 — a `user` calling admin-only routes). |\n| **Example object IDs** | Lets agents test ID tampering immediately instead of hunting for valid identifiers. |\n| **Out-of-scope routes** | Payments, mass notification, destructive admin endpoints. |\n| **Rate limits \u002F WAF** in front of the API | Avoids agents burning budget on throttled requests; mention them so testing adapts. |\n\nAsk the user for anything missing — do not fabricate tokens or scan an API they do not own.\n\n## 2. Run the scan\n\nPass the spec as a **target**, not as prose in the instruction — Strix parses OpenAPI\u002FSwagger (`.json`\u002F`.yaml`) and Postman collection exports directly, so the agents start from the real endpoint list:\n\n```bash\nstrix -n -t .\u002Fopenapi.yaml -t https:\u002F\u002Fapi.staging.example.com --max-budget 20 \\\n  --instruction \"Tenant A token: \u003CtokenA> (org 1111, user id 11, order id 501).\nTenant B token: \u003CtokenB> (org 2222, user id 22).\nAdmin token: \u003CtokenAdmin>.\nFocus: BOLA across orgs (API1), function-level authz on \u002Fadmin\u002F* (API5), object property level authz on PATCH \u002Fusers\u002F{id} — both mass assignment and over-exposed fields in list responses (API3), unrestricted resource consumption (API4).\nOut of scope: POST \u002Fbilling\u002F*, POST \u002Fnotifications\u002Fbroadcast.\"\n```\n\n- **Postman instead of OpenAPI:** a collection export works as a target (`-t .\u002Fcollection.postman_collection.json`), or pull one live with `-t postman:\u002F\u002F\u003Ccollection-uuid>` (optionally `\"postman:\u002F\u002F\u003Ccollection-uuid>?env=\u003Cenvironment-uuid>\"`), which needs `POSTMAN_API_KEY` in the environment.\n- **Many services at once:** put one target per line in a file and pass `--target-list .\u002Ftargets.txt`, repeatable and combinable with `-t`.\n- **Add the backend source for depth:** `-t .\u002Fservices\u002Fapi -t https:\u002F\u002Fapi.staging.example.com`. With code access the agents can reason about authorization checks and object ownership rather than inferring them from responses.\n- **gRPC:** target the endpoint and pass the definition as a workspace file, `-t https:\u002F\u002Fgrpc.staging.example.com --workspace-file .\u002Fservice.proto`. Only `.json`, `.yaml`, and `.yml` specs are recognized as targets, so `-t .\u002Fservice.proto` fails with \"Path exists but is not a directory\".\n- **GraphQL:** point at the GraphQL endpoint and say whether introspection is enabled; call out that you want batching\u002Faliasing abuse, depth\u002Fcomplexity limits, and per-field authorization tested.\n- **Internal\u002Fprivate APIs** unreachable from your machine: use the managed platform's network connector — see **managed-pentesting-with-strix**.\n- Use `--instruction-file` when the credential\u002Fcontext block gets long, and keep tokens out of shell history and out of committed files.\n- **Supporting files** the agents should read but not test, such as an endpoint wordlist or handwritten notes about the tenancy model: pass `--workspace-file .\u002Fnotes.md`. The file lands read-only in `\u002Fworkspace`. Add `:DEST` to choose the path, for example `--workspace-file .\u002Fwordlist.txt:lists\u002Fwordlist.txt`.\n\n## 3. Verify findings\n\n`strix_runs\u002F\u003Crun>\u002Fpenetration_test_report.md` first, then `vulnerabilities\u002F*.md` — each contains the exact request that proved the issue. Replay it (for example, with `curl`) before reporting; for authorization findings, confirm the response really contains the other tenant's data rather than an empty 200.\n\n`findings.sarif` uploads to GitHub code scanning; `vulnerabilities.json` is the structured index for ticketing.\n\n## 4. Fix, re-test, and keep it tested\n\nRemediate with **fix-security-vulnerabilities-with-strix** (fix the authorization check, not the single endpoint), then re-run against the same target to prove the exploit is dead. Wire it into pull-request CI with **ci-security-scanning-with-strix** so new endpoints get tested as they ship.\n","# Security-test an API\n\nAPIs fail differently from web UIs: there is no rendered surface to crawl, the interesting bugs are authorization-shaped rather than injection-shaped, and the same endpoint behaves differently per token. This workflow targets those specifics with Strix's autonomous agents, using the current [OWASP API Security Top 10 (2023)](https:\u002F\u002Fowasp.org\u002FAPI-Security\u002Feditions\u002F2023\u002Fen\u002F0x11-t10\u002F) as the coverage checklist. For the web-app equivalent, the current edition is the OWASP Top 10:2025 — see **owasp-top-10-testing**.\n\nInstall, LLM setup, full CLI flags, and the managed-cloud path are in the **penetration-testing-with-strix** skill. Read it if `strix --version` fails or the target is not an API. 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\n## 1. Gather what the agents need\n\nAPIs are near-impossible to test blind, so collect first:\n\n| Input | Why it matters |\n|---|---|\n| **Schema** — OpenAPI\u002FSwagger file, Postman collection, GraphQL endpoint (introspection), or a gRPC `.proto` | Turns guesswork into full endpoint enumeration. Biggest single win in coverage. An OpenAPI\u002FSwagger or Postman spec (`.json`\u002F`.yaml`\u002F`.yml`) is a target Strix takes directly; a `.proto` is not, so pass it with `--workspace-file`. |\n| **Two sets of credentials\u002Ftokens**, ideally in different tenants | BOLA\u002FIDOR — API1:2023, still the #1 API risk — can only be *proven* by accessing tenant A's objects with tenant B's token. |\n| **A low-privilege and a high-privilege token** | Required to prove broken function-level authorization (API5:2023 — a `user` calling admin-only routes). |\n| **Example object IDs** | Lets agents test ID tampering immediately instead of hunting for valid identifiers. |\n| **Out-of-scope routes** | Payments, mass notification, destructive admin endpoints. |\n| **Rate limits \u002F WAF** in front of the API | Avoids agents burning budget on throttled requests; mention them so testing adapts. |\n\nAsk the user for anything missing — do not fabricate tokens or scan an API they do not own.\n\n## 2. Run the scan\n\nPass the spec as a **target**, not as prose in the instruction — Strix parses OpenAPI\u002FSwagger (`.json`\u002F`.yaml`) and Postman collection exports directly, so the agents start from the real endpoint list:\n\n```bash\nstrix -n -t .\u002Fopenapi.yaml -t https:\u002F\u002Fapi.staging.example.com --max-budget 20 \\\n  --instruction \"Tenant A token: \u003CtokenA> (org 1111, user id 11, order id 501).\nTenant B token: \u003CtokenB> (org 2222, user id 22).\nAdmin token: \u003CtokenAdmin>.\nFocus: BOLA across orgs (API1), function-level authz on \u002Fadmin\u002F* (API5), object property level authz on PATCH \u002Fusers\u002F{id} — both mass assignment and over-exposed fields in list responses (API3), unrestricted resource consumption (API4).\nOut of scope: POST \u002Fbilling\u002F*, POST \u002Fnotifications\u002Fbroadcast.\"\n```\n\n- **Postman instead of OpenAPI:** a collection export works as a target (`-t .\u002Fcollection.postman_collection.json`), or pull one live with `-t postman:\u002F\u002F\u003Ccollection-uuid>` (optionally `\"postman:\u002F\u002F\u003Ccollection-uuid>?env=\u003Cenvironment-uuid>\"`), which needs `POSTMAN_API_KEY` in the environment.\n- **Many services at once:** put one target per line in a file and pass `--target-list .\u002Ftargets.txt`, repeatable and combinable with `-t`.\n- **Add the backend source for depth:** `-t .\u002Fservices\u002Fapi -t https:\u002F\u002Fapi.staging.example.com`. With code access the agents can reason about authorization checks and object ownership rather than inferring them from responses.\n- **gRPC:** target the endpoint and pass the definition as a workspace file, `-t https:\u002F\u002Fgrpc.staging.example.com --workspace-file .\u002Fservice.proto`. Only `.json`, `.yaml`, and `.yml` specs are recognized as targets, so `-t .\u002Fservice.proto` fails with \"Path exists but is not a directory\".\n- **GraphQL:** point at the GraphQL endpoint and say whether introspection is enabled; call out that you want batching\u002Faliasing abuse, depth\u002Fcomplexity limits, and per-field authorization tested.\n- **Internal\u002Fprivate APIs** unreachable from your machine: use the managed platform's network connector — see **managed-pentesting-with-strix**.\n- Use `--instruction-file` when the credential\u002Fcontext block gets long, and keep tokens out of shell history and out of committed files.\n- **Supporting files** the agents should read but not test, such as an endpoint wordlist or handwritten notes about the tenancy model: pass `--workspace-file .\u002Fnotes.md`. The file lands read-only in `\u002Fworkspace`. Add `:DEST` to choose the path, for example `--workspace-file .\u002Fwordlist.txt:lists\u002Fwordlist.txt`.\n\n## 3. Verify findings\n\n`strix_runs\u002F\u003Crun>\u002Fpenetration_test_report.md` first, then `vulnerabilities\u002F*.md` — each contains the exact request that proved the issue. Replay it (for example, with `curl`) before reporting; for authorization findings, confirm the response really contains the other tenant's data rather than an empty 200.\n\n`findings.sarif` uploads to GitHub code scanning; `vulnerabilities.json` is the structured index for ticketing.\n\n## 4. Fix, re-test, and keep it tested\n\nRemediate with **fix-security-vulnerabilities-with-strix** (fix the authorization check, not the single endpoint), then re-run against the same target to prove the exploit is dead. Wire it into pull-request CI with **ci-security-scanning-with-strix** so new endpoints get tested as they ship.\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"homepage":26},"usestrix","https:\u002F\u002Fdocs.strix.ai","main","bc2f998beb877748d6e8c4588942b4ff2cfa495b",".claude\u002Fskills\u002Fapi-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 api-security-testing",{"tool":41,"command":42},"bunx","bunx skills add Hareesh-Reddy-9126\u002FPS044-SmartHire --skill api-security-testing",{"tool":44,"command":45},"pnpm","pnpm dlx skills add Hareesh-Reddy-9126\u002FPS044-SmartHire --skill api-security-testing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHareesh-Reddy-9126\u002FPS044-SmartHire\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fapi-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",[],[]]