[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CSEVMHCDS727XMDG523443":3,"skill-same:01M7CSEVMHCDS727XMDG523443":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},"01M7CSEVMHCDS727XMDG523443","managed-pentesting-with-strix",null,"Run a managed pentest of a web app, API, repository, or local workspace on the app.strix.ai platform with the `strix cloud` CLI or REST API — no local Docker or LLM key needed. Safely review and upload local source, register assets, launch and poll scans, triage vulnerabilities, export SARIF, download compliance reports, start PR reviews, buy credits, and set up schedules or webhooks. Use for managed, continuous, scheduled, team-tracked, or sandboxed-agent security testing.","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\u002Fmanaged-pentesting-with-strix\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: managed-pentesting-with-strix\ndescription: Run a managed pentest of a web app, API, repository, or local workspace on the app.strix.ai platform with the `strix cloud` CLI or REST API — no local Docker or LLM key needed. Safely review and upload local source, register assets, launch and poll scans, triage vulnerabilities, export SARIF, download compliance reports, start PR reviews, buy credits, and set up schedules or webhooks. Use for managed, continuous, scheduled, team-tracked, or sandboxed-agent security testing.\nlicense: Apache-2.0\nmetadata:\n  author: usestrix\n  homepage: https:\u002F\u002Fdocs.app.strix.ai\n---\n\n# Strix Cloud (managed, no local infra)\n\nUse this when you want Strix's autonomous pentesting **without running Docker or an LLM yourself** — the scan runs on Strix's infrastructure and results are tracked in a team dashboard. This is the right choice in sandboxed\u002Fhosted agent and CI environments, for teams, and for scheduled\u002Fcontinuous testing (downloadable PDF\u002FDOCX reports are an Enterprise-plan feature). For fully local, free, air-gapped, or BYO-LLM runs, use the open-source CLI in the **penetration-testing-with-strix** skill instead — both share the same engine and SARIF output, so you can mix them.\n\nThere are two equivalent interfaces. Prefer the CLI:\n\n- **`strix cloud` CLI** — every REST operation has a command in the form `strix cloud \u003Cresource> \u003Cverb>`. Install with `curl -sSL https:\u002F\u002Fstrix.ai\u002Finstall | bash`. Run `strix cloud` to list all resources and `strix cloud \u003Cresource> help` (or `-h`) to list a resource's verbs; a bare resource with a safe read operation runs its documented default.\n- **REST API** — base URL `https:\u002F\u002Fapp.strix.ai\u002Fapi\u002Fv1`, `Authorization: Bearer \u003Ctoken>` on every request. Full reference: **[docs.app.strix.ai](https:\u002F\u002Fdocs.app.strix.ai)** · agent index: `https:\u002F\u002Fdocs.app.strix.ai\u002Fllms.txt` · OpenAPI: `https:\u002F\u002Fdocs.app.strix.ai\u002Fopenapi.json`.\n\nThe CLI is equally usable by agents and people. Output is complete JSON when stdout is not a terminal, or when you pass `--json`; terminal tables favor names, branches, lifecycle states, and numbered selectors. Human lists retain the selectors needed by follow-up commands but omit internal organization\u002Fuser IDs; a selector too long for the compact table is repeated losslessly in a copyable block. Paginated lists print the next `--page` or `--offset`, and detail views preserve useful prose within a safe terminal bound; use `--json` for the complete record. Token lists label credentials as active, expired, or revoked. Binary downloads are the exception: redirect raw bytes intentionally, or use `--output FILE --json` to write the file and receive structured metadata. There are no interactive prompts when stdin is not a terminal. Exit codes: `0` success, `1` request\u002Fruntime error, `2` invalid usage, `4` authentication or plan limit, `5` payment required.\n\nEvery resource group with a safe read operation has a useful default action, and `-h` or `help` always shows its verbs. Native tab completion includes resources, verbs, flags, workspace commands, and local paths:\n\n```bash\nsource \u003C(strix completions zsh)       # current zsh session\nsource \u003C(strix completions bash)      # current bash session\nstrix completions fish | source       # current fish session\n```\n\nWrite commands take request fields as flags. Every write command also accepts one JSON object with `--data`, which is the way to send fields that have no flag:\n\n```bash\nstrix cloud scans start --data '{\"engagement_type\":\"code_review\"}'   # literal JSON\nstrix cloud scans start --data @request.json                         # read a file\ncat request.json | strix cloud scans start --data -                  # read standard input\n```\n\nThe platform enforces plan and role limits, and the CLI passes the platform message through. Report downloads need the Enterprise plan. Schedules need the Pro plan. Billing writes need an admin token. A blocked command exits with code `4`.\n\n## Setup: sign in\n\nRun the device sign-in. It creates the user's account and workspace on first use and stores a personal API token in `~\u002F.strix\u002Fplatform-auth.json`:\n\n```bash\nstrix cloud login\n# Non-interactive least-privilege example:\nstrix cloud login --scopes scans:read scans:write uploads:write billing:read vulnerabilities:read assets:read assets:write\n# Or use a stable named profile:\nstrix cloud login --scope-profile recommended\n```\n\nThe user approves the sign-in in the browser. With `--scopes` (and optionally `--workspace \u003Cname-or-id>`) there are no terminal prompts, so the command works from a non-interactive agent shell. In an interactive terminal without flags, the CLI offers a workspace picker and scope presets (Recommended, Full access, Minimal, Custom). Recommended covers ordinary scans, source uploads, workspace switching, and user-approved credit top-ups; it excludes `tokens:write`, which must be requested explicitly when credential management is required. Use explicit scopes for a narrower automation token.\n\n- `strix cloud whoami` is the fast local status. `strix cloud session --json` verifies the remote device session; `strix cloud session scopes` shows both effective access and the immutable login ceiling.\n- `strix cloud logout` revokes the remote session before removing the local token. On a network or server failure it keeps the token so the user can retry; `--local-only` deliberately skips revocation.\n- Every other `strix cloud` command uses the stored token automatically. `--token \u003Ctoken>` or `STRIX_API_TOKEN` is a stateless per-command override and never overwrites the stored account. For an override that is itself a CLI session, also pass `--workspace-id` or set `STRIX_WORKSPACE_ID`.\n- Never hardcode, log, or commit the token. Store it in an env var or the CI secret store.\n- **Scopes (least-privilege):** assign only what the integration needs and rotate regularly:\n\n  | Scope | Grants |\n  |---|---|\n  | `scans:read` \u002F `scans:write` | list\u002Fread\u002Freport scans · create\u002Frerun\u002Fcancel scans |\n  | `vulnerabilities:read` \u002F `:write` | read findings · update status & notes |\n  | `assets:read` \u002F `:write` | read domains\u002Frepos · register\u002Fupdate them |\n  | `schedules:read` \u002F `:write` | read schedules · create\u002Ftrigger recurring scans |\n  | `pr_reviews:write` | trigger PR security reviews |\n  | `webhooks:read` \u002F `:write` | manage webhook subscriptions |\n  | `uploads:write` | upload local source or documents for a scan |\n  | `organizations:read` | read organization details (listing\u002Fswitching the signed-in user's workspaces needs no API scope) |\n  | `organizations:write` | create\u002Fupdate workspaces (admin) |\n  | `tokens:write` | create\u002Frevoke ordinary API tokens (not needed to manage the current CLI session) |\n  | `knowledge:read` \u002F `:write` | read\u002Fupdate organization knowledge |\n  | `audit:read` | read\u002Fexport the Enterprise audit log |\n  | `billing:read` \u002F `billing:write` | read credit balance & auto top-up settings · buy credits (admin) |\n\nHTTP errors map to messages and exit codes: `401` bad\u002Fexpired token (exit `4`), `402` out of credits (exit `5`), `403` scope\u002Fplan-tier limit (exit `4`), `422` validation error (exit `1`).\n\nCreate a time-limited automation token with `strix cloud tokens create`. Use\n`--rbac-scopes` to restrict it to target IDs, tags, or business units; the value is a\nJSON array of `{ \"type\": \"target|tag|business_unit\", \"value\": \"...\" }` objects:\n\n```bash\nstrix cloud tokens create --type service --name staging-ci \\\n  --expires-at 2026-12-31T23:59:59Z \\\n  --scopes scans:read scans:write \\\n  --rbac-scopes '[{\"type\":\"tag\",\"value\":\"staging\"}]'\n```\n\nThe token secret is returned once. Store it directly in a secret manager and do not\nprint or commit it. `--expires-at` and `--expires-in-days` are mutually exclusive.\n\n## 0. Credits & top-ups\n\nNon-Enterprise scans consume org credits. Enterprise engagements are plan-included and do not debit the wallet. Check the balance before a scan (`billing:read`):\n\n```bash\nstrix cloud credits\n```\n\nWhen the balance is too low, buy credits with `strix cloud billing topup` (`billing:write`, admin token). The server answers the first request with **HTTP 402 and a machine-payment challenge** (Stripe Machine Payments Protocol). The CLI pays the challenge with the Stripe Link wallet client when Node.js is available — the user approves the spend in the [Link app](https:\u002F\u002Flink.com\u002Fagents). The response returns the receipt (`credits_granted`, `duplicate`, `reference`) and the new balance.\n\nA default-tier source-only code review currently starts at 60 credits. Source uploads are not free: they launch an ordinary `code_review` and use the same deterministic scope estimator. The service checks the full balance before launch, reserves credits atomically only after validation succeeds, and does not create or charge a rejected scan. Retests and Enterprise scans are exempt.\n\n```bash\nstrix cloud billing topup --credits 20 --yes   # explicit approval; skips the TTY prompt\nstrix cloud billing topup --credits 20 --no-pay   # print the 402 challenge without paying\n```\n\nThe default payment path is the Stripe Link wallet. When no wallet is connected, an interactive `strix cloud billing topup` starts the Link sign-in for the user and prints the verification link. The user approves the connection one time in the Link app, and then approves each payment there. No keys or variables are necessary. In a non-interactive process, the command stops and tells the user to connect the wallet at [link.com\u002Fagents](https:\u002F\u002Flink.com\u002Fagents) or to use the hosted checkout link.\n\nIn a non-interactive agent or CI process, payment never proceeds unless the command includes `--yes`. Show the challenge or estimated spend to the user and obtain approval before adding it. `--no-pay` always stops after printing the challenge.\n\nIf the user does not want a wallet, create a hosted checkout link with `strix cloud billing subscribe --plan strix_top_up` and give the link to the user. The user pays in the browser.\n\nAutomatic top-ups (admin): `strix cloud billing auto-topup` shows the setting. Enable it with:\n\n```bash\nstrix cloud billing auto-topup update --enabled --topup-credits 20 --monthly-cap-credits 200\n```\n\nAn omitted `--monthly-cap-credits` keeps the stored cap. Pass `--no-monthly-cap` to remove the cap.\n\n### Workspaces and account setup\n\nManage workspaces with a personal token from `strix cloud login`:\n\n```bash\nstrix cloud workspaces list                    # numbered name\u002Frole\u002Fcurrent list\nstrix cloud workspaces create --name \"My Team\"  # admin + organizations:write\nstrix cloud workspaces use 2                   # displayed number, exact name, or ID\nstrix cloud workspace use \"My Team\"            # singular `workspace` alias also works\nstrix cloud session scopes                     # effective scopes + consent ceiling\nstrix cloud session scopes set minimal         # narrow the session\nstrix cloud org members invite --email dev@example.com --role analyst\n```\n\n`workspaces use` retargets the current personal token to a workspace the user already belongs to and stores the updated workspace metadata; the bearer secret and expiry stay unchanged. It does not reprompt during ordinary switches: the server preserves the chosen profile, enforces the immutable login ceiling, and caps effective scopes by the target role. Use `--scope-profile` or `--scopes` to narrow within that ceiling; broader consent requires `strix cloud login` again. The CLI pins each process to the workspace it started in, so concurrent shells fail with a recoverable conflict instead of silently crossing organizations.\n\n### Handoffs a person must finish\n\nFour steps end at the user. The command creates the link or the record and prints it. Strix opens the browser only in an interactive terminal. Pass `--no-browser` to print the URL only.\n\n```bash\nstrix cloud billing subscribe --plan strix_cloud # hosted checkout page for the Cloud plan\nstrix cloud billing portal                       # billing portal for the card and the plan\nstrix cloud integrations install github          # GitHub App or Slack installation page\nstrix cloud domains verify \u003Cdomain-id>           # DNS record to add, then run it again\n```\n\nGive the printed URL or DNS record to the user and wait. Do not claim that the payment, the installation, or the DNS change is complete. Confirm the result afterwards with `strix cloud credits`, `strix cloud integrations list`, or `strix cloud domains list`. All four commands need an admin token, except `domains verify`, which needs `assets:write`.\n\n### Organization knowledge\n\nAgents can manage the organization knowledge base without the dashboard (`knowledge:read` \u002F `knowledge:write`):\n\n```bash\nstrix cloud knowledge list --search authentication\nstrix cloud knowledge add --title \"Authentication\" --content \"Staging uses SSO.\"\nstrix cloud knowledge update \u003Cdocument-id> --content \"Staging uses SSO and TOTP.\"\nstrix cloud knowledge delete \u003Cdocument-id>\nstrix cloud knowledge policies add --key staging-only --content \"Never test production.\"\nstrix cloud knowledge policies delete staging-only\nstrix cloud knowledge repos entries usestrix\u002Fstrix\n```\n\nKnowledge policy writes require an admin token. Repository names are passed as normal `owner\u002Fname` values; the CLI handles URL encoding. The `costs` and `llm-settings` commands target on-prem installations and return `404` on app.strix.ai.\n\n## 1. Register the target as an asset\n\nScans run against **registered assets**, not raw URLs. Register once, then reuse the returned UUID.\n\n```bash\n# Domain (black-box \u002F live target). Requires domain verification before external scanning.\n# --asset-type must be one of: web_app | api | attack_surface.\nstrix cloud domains add --domain staging.example.com --asset-type web_app\n\n# Repository (white-box \u002F code review). `full_name` is \"owner\u002Fname\".\nstrix cloud repos add --data '{\"full_name\":\"org\u002Fapp\",\"provider\":\"github\"}'\n```\n\nLook up existing assets instead of re-adding: `strix cloud domains list`, `strix cloud repos list` (both `assets:read`).\n\n## 2. Launch a scan\n\n`strix cloud scans start` (`scans:write`). Provide at least one target with `--domain-ids`, `--repository-ids`, or `--internal-targets` (internal infra needs a network connector — see docs).\n\n```bash\nstrix cloud scans start \\\n  --engagement-type live_test \\\n  --domain-ids \u003Cdomain-uuid> \\\n  --focus \"IDOR, auth bypass, SSRF\" \\\n  --context \"Staging. Test account creds are configured as a test user.\" \\\n  --notify-on-completion\n```\n\nUseful flags (each maps to a `CreateScanRequest` field):\n\n| Flag | Purpose |\n|---|---|\n| `--engagement-type` | `live_test` (default), `code_review`, `internal_infra`, `compliance_pentest` |\n| `--domain-ids` \u002F `--repository-ids` \u002F `--internal-targets` | targets (at least one) |\n| `--domain-paths` \u002F `--repository-branches` | narrow to specific paths \u002F branches (JSON maps) |\n| `--credentials` | authenticated scanning, incl. `mfa_method` (`totp`\u002F`email_otp`\u002F…) + `totp_secret` (JSON list) |\n| `--headers` | extra target HTTP headers as a JSON array of header objects |\n| `--focus` \u002F `--concerns` \u002F `--context` | free-form strings that steer the agents |\n| `--upload-ids` | attach uploaded source\u002Fdocs archives for white-box context |\n| `--notify-on-completion` \u002F `--notification-emails` | email when done |\n\nWithout `--source`, the response is `{ scan_id, title, status }` with `status` = `pending`.\nLocal-source success wraps that platform response as\n`{ source, upload_id, scan: { scan_id, title, status } }`, so automation can retain the exact\napproved manifest and staged-upload identifier alongside the created scan.\n\n### Scan a local workspace in the cloud\n\nFor an agent or CI workflow, bind approval to the exact source snapshot that was reviewed. Run\nthe dry run with the intended source-selection flags, review the manifest and selected paths,\nand capture `source.archive_sha256`. Then repeat the same `--source`, every `--exclude`, and\nany `--include-hidden`, `--include-sensitive`, or `--include-archives` flags with\n`--approve-sha256`:\n\n```bash\nstrix cloud scans start --source . --exclude 'private\u002F' --dry-run --show-files --json\n# After reviewing the output, capture its source.archive_sha256 value:\nSOURCE_SHA256=\"\u003Creviewed source.archive_sha256>\"\n# Repeat every source-selection flag unchanged; a source-only scan infers code_review.\nstrix cloud scans start --source . --exclude 'private\u002F' \\\n  --approve-sha256 \"$SOURCE_SHA256\" --wait\n```\n\nThe CLI rebuilds the archive and refuses the upload if its SHA-256 no longer matches. `--yes`\nhas deliberately narrower semantics: it approves only the snapshot built during that one\ninvocation. Use it for a deliberate human or one-shot approval, not as the second half of a\ndigest-bound agent\u002FCI review. Without a TTY, a source upload requires either matching\n`--approve-sha256` approval or `--yes`; an interactive terminal can instead show the summary,\nthe selected filenames when `--show-files` is set, and a `[y\u002FN]` confirmation for its current\nsnapshot.\n\nThe default selection is privacy-conscious: in a Git worktree it includes tracked files plus untracked files that are not ignored; it honors `.gitignore`, excludes every hidden path component, always excludes `.git`, symlinks, dependencies\u002Fbuild output, secret-like filenames, and nested archives. Add project exclusions to `.strixignore` (one exclude glob per line) or repeat `--exclude GLOB`; a trailing slash such as `private\u002F` excludes that directory subtree.\n\nThe client refuses more than 20,000 files, a file over 25 MiB, more than 250 MiB expanded, or a ZIP over 50 MiB. The service then stream-inflates the ZIP and independently rejects malformed or unsupported entries, unsafe paths, too many entries, oversized entries, excessive expanded data, and oversized compressed input, so an untrusted client cannot bypass the ZIP-bomb controls by forging metadata.\n\nOnly use `--include-hidden`, `--include-sensitive`, or `--include-archives` after the dry-run manifest shows that the scan needs them. Hidden and sensitive files are separate opt-ins: for example, including `.env` requires both `--include-hidden` and `--include-sensitive`.\n\nThe CLI removes its private temporary local archive after every invocation. Once a remote\nupload is staged, a definitive scan rejection causes the CLI to delete it. A network failure,\n`5xx` response, malformed success response, or interruption after scan launch begins is\nambiguous—the platform may have accepted the scan—so the CLI retains the upload and returns\nits `upload_id` with `launch_outcome_unknown: true`. If an automatic deletion attempt cannot\nbe confirmed, it instead returns the retained `upload_id` with `cleanup_unknown: true`.\nBefore retrying, run `strix cloud scans list` to avoid a duplicate scan or charge. If no scan\nis linked to the retained upload, remove it with `strix cloud uploads delete UPLOAD_ID`;\nlinked uploads cannot be deleted.\n\nWith no explicit type, source alone infers `code_review`. Any domain target wins and infers `live_test`, so source plus a deployed domain is the normal white-box live-test workflow. Pass `--engagement-type` when you need to override the inference.\n\n## 3. Wait for completion\n\nPass `--wait` to `scans start` to poll until the scan reaches a final state, or poll yourself with `strix cloud scans get \u003Cscan-id>` (`scans:read`). Bound automation with `--wait-timeout SECONDS`; timeout exits cleanly without cancelling the remote scan. Status flow: `pending → running → completed` (or `failed` \u002F `cancelled`). Scans take minutes to hours — poll on an interval, do not block indefinitely.\n\n## 4. Read findings\n\nThe scan-detail response includes `executive_summary`, `methodology`, `recommendations`, a `findings` severity roll-up, and a `vulnerabilities[]` array. Each vulnerability carries `title, severity, status, cvss, 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`.\n\n```bash\nstrix cloud scans get \u003Cscan-id> --json \\\n  | jq '[\"critical\",\"high\",\"medium\",\"low\",\"info\"] as $order\n       | .vulnerabilities\n       | sort_by(.severity as $s | $order | index($s))\n       | .[] | {title, severity, endpoint, cwe}'\n```\n\nCloud severities are `critical | high | medium | low` and statuses are `open | in_progress | snoozed | fixed | ignored | not_affected`. Sort by an explicit severity order rather than `sort_by(.severity)`, which sorts alphabetically (critical, high, low, medium).\n\nOrg-wide triage across scans: `strix cloud vulns list --severity critical` (`vulnerabilities:read`, and it also filters by `--status`, `--scan-id`, and more). Update triage state with `strix cloud vulns update \u003Cid> --status fixed`. To remediate, hand off to the **fix-security-vulnerabilities-with-strix** skill.\n\n## 5. Export & report\n\n```bash\n# SARIF 2.1.0 for GitHub code scanning \u002F ASPM ingestion\nstrix cloud scans sarif \u003Cscan-id> --output findings.sarif\n\n# Report. Formats: technical (default) | retest | attestation | executive_summary\n# Types: pdf (default) | docx\n# Any report download requires the Enterprise plan. Formats beyond `technical`,\n# DOCX, and white-label branding are Enterprise-only too. Scan must be completed.\nstrix cloud scans report \u003Cscan-id> --format technical --type pdf --output strix-report.pdf\n```\n\nDownloads refuse to replace a file unless `--force` is explicit. Enterprise audit logs can be streamed as JSON or exported without trying to JSON-decode the body:\n\n```bash\nstrix cloud audit list --format csv --all --output audit.csv\nstrix cloud audit list --format ndjson --all --output audit.ndjson\n```\n\n## 6. PR reviews\n\nTrigger an automated security review of a pull request (`pr_reviews:write`). Read the repository's `provider` and `installation_id` with `strix cloud repos list`; both identify the installed source-control integration. The results appear as PR comments and in the dashboard:\n\n```bash\nstrix cloud pr-reviews start \\\n  --provider github \\\n  --installation-id \u003Cinstallation-id> \\\n  --repository-full-name org\u002Fapp \\\n  --pr-number 123\n```\n\nList\u002Finspect with `strix cloud pr-reviews list` and `strix cloud pr-reviews get \u003Cid>`. Repo-level PR-review behavior is configured with `strix cloud pr-reviews settings`.\n\n## 7. Continuous testing (schedules & webhooks)\n\n- **Schedules** (`schedules:write`, Pro plan): `strix cloud schedules create` makes recurring scans, and `strix cloud schedules trigger \u003Cid>` runs one on demand — the managed equivalent of a cron-driven CLI loop.\n- **Webhooks** (`webhooks:write`): `strix cloud webhooks create` subscribes to pentest\u002Fvulnerability lifecycle events such as `scan.completed` and `vulnerability.created` to push results into Slack, ticketing, or your own pipeline instead of polling.\n\nSee the schedules and webhooks sections at [docs.app.strix.ai](https:\u002F\u002Fdocs.app.strix.ai) for payloads.\n\nNetwork connectors are Enterprise-only. `strix cloud connectors create` may return a one-time enrollment command containing credentials; do not paste it into logs, and request it with `--include-command` only when the user is ready to install it. Browser checkout, source-control installation, DNS verification, connector installation, chat sharing, and publishing SARIF to an external provider are user handoffs or explicit external mutations—prepare the command\u002Flink, then obtain the appropriate approval before completing them.\n\n## Safety\n\nOnly scan assets the user's organization owns or is authorized to test. External domain scans require verification (DNS\u002Ffile\u002Fmeta-tag) enforced by the platform — do not try to bypass it.\n","# Strix Cloud (managed, no local infra)\n\nUse this when you want Strix's autonomous pentesting **without running Docker or an LLM yourself** — the scan runs on Strix's infrastructure and results are tracked in a team dashboard. This is the right choice in sandboxed\u002Fhosted agent and CI environments, for teams, and for scheduled\u002Fcontinuous testing (downloadable PDF\u002FDOCX reports are an Enterprise-plan feature). For fully local, free, air-gapped, or BYO-LLM runs, use the open-source CLI in the **penetration-testing-with-strix** skill instead — both share the same engine and SARIF output, so you can mix them.\n\nThere are two equivalent interfaces. Prefer the CLI:\n\n- **`strix cloud` CLI** — every REST operation has a command in the form `strix cloud \u003Cresource> \u003Cverb>`. Install with `curl -sSL https:\u002F\u002Fstrix.ai\u002Finstall | bash`. Run `strix cloud` to list all resources and `strix cloud \u003Cresource> help` (or `-h`) to list a resource's verbs; a bare resource with a safe read operation runs its documented default.\n- **REST API** — base URL `https:\u002F\u002Fapp.strix.ai\u002Fapi\u002Fv1`, `Authorization: Bearer \u003Ctoken>` on every request. Full reference: **[docs.app.strix.ai](https:\u002F\u002Fdocs.app.strix.ai)** · agent index: `https:\u002F\u002Fdocs.app.strix.ai\u002Fllms.txt` · OpenAPI: `https:\u002F\u002Fdocs.app.strix.ai\u002Fopenapi.json`.\n\nThe CLI is equally usable by agents and people. Output is complete JSON when stdout is not a terminal, or when you pass `--json`; terminal tables favor names, branches, lifecycle states, and numbered selectors. Human lists retain the selectors needed by follow-up commands but omit internal organization\u002Fuser IDs; a selector too long for the compact table is repeated losslessly in a copyable block. Paginated lists print the next `--page` or `--offset`, and detail views preserve useful prose within a safe terminal bound; use `--json` for the complete record. Token lists label credentials as active, expired, or revoked. Binary downloads are the exception: redirect raw bytes intentionally, or use `--output FILE --json` to write the file and receive structured metadata. There are no interactive prompts when stdin is not a terminal. Exit codes: `0` success, `1` request\u002Fruntime error, `2` invalid usage, `4` authentication or plan limit, `5` payment required.\n\nEvery resource group with a safe read operation has a useful default action, and `-h` or `help` always shows its verbs. Native tab completion includes resources, verbs, flags, workspace commands, and local paths:\n\n```bash\nsource \u003C(strix completions zsh)       # current zsh session\nsource \u003C(strix completions bash)      # current bash session\nstrix completions fish | source       # current fish session\n```\n\nWrite commands take request fields as flags. Every write command also accepts one JSON object with `--data`, which is the way to send fields that have no flag:\n\n```bash\nstrix cloud scans start --data '{\"engagement_type\":\"code_review\"}'   # literal JSON\nstrix cloud scans start --data @request.json                         # read a file\ncat request.json | strix cloud scans start --data -                  # read standard input\n```\n\nThe platform enforces plan and role limits, and the CLI passes the platform message through. Report downloads need the Enterprise plan. Schedules need the Pro plan. Billing writes need an admin token. A blocked command exits with code `4`.\n\n## Setup: sign in\n\nRun the device sign-in. It creates the user's account and workspace on first use and stores a personal API token in `~\u002F.strix\u002Fplatform-auth.json`:\n\n```bash\nstrix cloud login\n# Non-interactive least-privilege example:\nstrix cloud login --scopes scans:read scans:write uploads:write billing:read vulnerabilities:read assets:read assets:write\n# Or use a stable named profile:\nstrix cloud login --scope-profile recommended\n```\n\nThe user approves the sign-in in the browser. With `--scopes` (and optionally `--workspace \u003Cname-or-id>`) there are no terminal prompts, so the command works from a non-interactive agent shell. In an interactive terminal without flags, the CLI offers a workspace picker and scope presets (Recommended, Full access, Minimal, Custom). Recommended covers ordinary scans, source uploads, workspace switching, and user-approved credit top-ups; it excludes `tokens:write`, which must be requested explicitly when credential management is required. Use explicit scopes for a narrower automation token.\n\n- `strix cloud whoami` is the fast local status. `strix cloud session --json` verifies the remote device session; `strix cloud session scopes` shows both effective access and the immutable login ceiling.\n- `strix cloud logout` revokes the remote session before removing the local token. On a network or server failure it keeps the token so the user can retry; `--local-only` deliberately skips revocation.\n- Every other `strix cloud` command uses the stored token automatically. `--token \u003Ctoken>` or `STRIX_API_TOKEN` is a stateless per-command override and never overwrites the stored account. For an override that is itself a CLI session, also pass `--workspace-id` or set `STRIX_WORKSPACE_ID`.\n- Never hardcode, log, or commit the token. Store it in an env var or the CI secret store.\n- **Scopes (least-privilege):** assign only what the integration needs and rotate regularly:\n\n  | Scope | Grants |\n  |---|---|\n  | `scans:read` \u002F `scans:write` | list\u002Fread\u002Freport scans · create\u002Frerun\u002Fcancel scans |\n  | `vulnerabilities:read` \u002F `:write` | read findings · update status & notes |\n  | `assets:read` \u002F `:write` | read domains\u002Frepos · register\u002Fupdate them |\n  | `schedules:read` \u002F `:write` | read schedules · create\u002Ftrigger recurring scans |\n  | `pr_reviews:write` | trigger PR security reviews |\n  | `webhooks:read` \u002F `:write` | manage webhook subscriptions |\n  | `uploads:write` | upload local source or documents for a scan |\n  | `organizations:read` | read organization details (listing\u002Fswitching the signed-in user's workspaces needs no API scope) |\n  | `organizations:write` | create\u002Fupdate workspaces (admin) |\n  | `tokens:write` | create\u002Frevoke ordinary API tokens (not needed to manage the current CLI session) |\n  | `knowledge:read` \u002F `:write` | read\u002Fupdate organization knowledge |\n  | `audit:read` | read\u002Fexport the Enterprise audit log |\n  | `billing:read` \u002F `billing:write` | read credit balance & auto top-up settings · buy credits (admin) |\n\nHTTP errors map to messages and exit codes: `401` bad\u002Fexpired token (exit `4`), `402` out of credits (exit `5`), `403` scope\u002Fplan-tier limit (exit `4`), `422` validation error (exit `1`).\n\nCreate a time-limited automation token with `strix cloud tokens create`. Use\n`--rbac-scopes` to restrict it to target IDs, tags, or business units; the value is a\nJSON array of `{ \"type\": \"target|tag|business_unit\", \"value\": \"...\" }` objects:\n\n```bash\nstrix cloud tokens create --type service --name staging-ci \\\n  --expires-at 2026-12-31T23:59:59Z \\\n  --scopes scans:read scans:write \\\n  --rbac-scopes '[{\"type\":\"tag\",\"value\":\"staging\"}]'\n```\n\nThe token secret is returned once. Store it directly in a secret manager and do not\nprint or commit it. `--expires-at` and `--expires-in-days` are mutually exclusive.\n\n## 0. Credits & top-ups\n\nNon-Enterprise scans consume org credits. Enterprise engagements are plan-included and do not debit the wallet. Check the balance before a scan (`billing:read`):\n\n```bash\nstrix cloud credits\n```\n\nWhen the balance is too low, buy credits with `strix cloud billing topup` (`billing:write`, admin token). The server answers the first request with **HTTP 402 and a machine-payment challenge** (Stripe Machine Payments Protocol). The CLI pays the challenge with the Stripe Link wallet client when Node.js is available — the user approves the spend in the [Link app](https:\u002F\u002Flink.com\u002Fagents). The response returns the receipt (`credits_granted`, `duplicate`, `reference`) and the new balance.\n\nA default-tier source-only code review currently starts at 60 credits. Source uploads are not free: they launch an ordinary `code_review` and use the same deterministic scope estimator. The service checks the full balance before launch, reserves credits atomically only after validation succeeds, and does not create or charge a rejected scan. Retests and Enterprise scans are exempt.\n\n```bash\nstrix cloud billing topup --credits 20 --yes   # explicit approval; skips the TTY prompt\nstrix cloud billing topup --credits 20 --no-pay   # print the 402 challenge without paying\n```\n\nThe default payment path is the Stripe Link wallet. When no wallet is connected, an interactive `strix cloud billing topup` starts the Link sign-in for the user and prints the verification link. The user approves the connection one time in the Link app, and then approves each payment there. No keys or variables are necessary. In a non-interactive process, the command stops and tells the user to connect the wallet at [link.com\u002Fagents](https:\u002F\u002Flink.com\u002Fagents) or to use the hosted checkout link.\n\nIn a non-interactive agent or CI process, payment never proceeds unless the command includes `--yes`. Show the challenge or estimated spend to the user and obtain approval before adding it. `--no-pay` always stops after printing the challenge.\n\nIf the user does not want a wallet, create a hosted checkout link with `strix cloud billing subscribe --plan strix_top_up` and give the link to the user. The user pays in the browser.\n\nAutomatic top-ups (admin): `strix cloud billing auto-topup` shows the setting. Enable it with:\n\n```bash\nstrix cloud billing auto-topup update --enabled --topup-credits 20 --monthly-cap-credits 200\n```\n\nAn omitted `--monthly-cap-credits` keeps the stored cap. Pass `--no-monthly-cap` to remove the cap.\n\n### Workspaces and account setup\n\nManage workspaces with a personal token from `strix cloud login`:\n\n```bash\nstrix cloud workspaces list                    # numbered name\u002Frole\u002Fcurrent list\nstrix cloud workspaces create --name \"My Team\"  # admin + organizations:write\nstrix cloud workspaces use 2                   # displayed number, exact name, or ID\nstrix cloud workspace use \"My Team\"            # singular `workspace` alias also works\nstrix cloud session scopes                     # effective scopes + consent ceiling\nstrix cloud session scopes set minimal         # narrow the session\nstrix cloud org members invite --email dev@example.com --role analyst\n```\n\n`workspaces use` retargets the current personal token to a workspace the user already belongs to and stores the updated workspace metadata; the bearer secret and expiry stay unchanged. It does not reprompt during ordinary switches: the server preserves the chosen profile, enforces the immutable login ceiling, and caps effective scopes by the target role. Use `--scope-profile` or `--scopes` to narrow within that ceiling; broader consent requires `strix cloud login` again. The CLI pins each process to the workspace it started in, so concurrent shells fail with a recoverable conflict instead of silently crossing organizations.\n\n### Handoffs a person must finish\n\nFour steps end at the user. The command creates the link or the record and prints it. Strix opens the browser only in an interactive terminal. Pass `--no-browser` to print the URL only.\n\n```bash\nstrix cloud billing subscribe --plan strix_cloud # hosted checkout page for the Cloud plan\nstrix cloud billing portal                       # billing portal for the card and the plan\nstrix cloud integrations install github          # GitHub App or Slack installation page\nstrix cloud domains verify \u003Cdomain-id>           # DNS record to add, then run it again\n```\n\nGive the printed URL or DNS record to the user and wait. Do not claim that the payment, the installation, or the DNS change is complete. Confirm the result afterwards with `strix cloud credits`, `strix cloud integrations list`, or `strix cloud domains list`. All four commands need an admin token, except `domains verify`, which needs `assets:write`.\n\n### Organization knowledge\n\nAgents can manage the organization knowledge base without the dashboard (`knowledge:read` \u002F `knowledge:write`):\n\n```bash\nstrix cloud knowledge list --search authentication\nstrix cloud knowledge add --title \"Authentication\" --content \"Staging uses SSO.\"\nstrix cloud knowledge update \u003Cdocument-id> --content \"Staging uses SSO and TOTP.\"\nstrix cloud knowledge delete \u003Cdocument-id>\nstrix cloud knowledge policies add --key staging-only --content \"Never test production.\"\nstrix cloud knowledge policies delete staging-only\nstrix cloud knowledge repos entries usestrix\u002Fstrix\n```\n\nKnowledge policy writes require an admin token. Repository names are passed as normal `owner\u002Fname` values; the CLI handles URL encoding. The `costs` and `llm-settings` commands target on-prem installations and return `404` on app.strix.ai.\n\n## 1. Register the target as an asset\n\nScans run against **registered assets**, not raw URLs. Register once, then reuse the returned UUID.\n\n```bash\n# Domain (black-box \u002F live target). Requires domain verification before external scanning.\n# --asset-type must be one of: web_app | api | attack_surface.\nstrix cloud domains add --domain staging.example.com --asset-type web_app\n\n# Repository (white-box \u002F code review). `full_name` is \"owner\u002Fname\".\nstrix cloud repos add --data '{\"full_name\":\"org\u002Fapp\",\"provider\":\"github\"}'\n```\n\nLook up existing assets instead of re-adding: `strix cloud domains list`, `strix cloud repos list` (both `assets:read`).\n\n## 2. Launch a scan\n\n`strix cloud scans start` (`scans:write`). Provide at least one target with `--domain-ids`, `--repository-ids`, or `--internal-targets` (internal infra needs a network connector — see docs).\n\n```bash\nstrix cloud scans start \\\n  --engagement-type live_test \\\n  --domain-ids \u003Cdomain-uuid> \\\n  --focus \"IDOR, auth bypass, SSRF\" \\\n  --context \"Staging. Test account creds are configured as a test user.\" \\\n  --notify-on-completion\n```\n\nUseful flags (each maps to a `CreateScanRequest` field):\n\n| Flag | Purpose |\n|---|---|\n| `--engagement-type` | `live_test` (default), `code_review`, `internal_infra`, `compliance_pentest` |\n| `--domain-ids` \u002F `--repository-ids` \u002F `--internal-targets` | targets (at least one) |\n| `--domain-paths` \u002F `--repository-branches` | narrow to specific paths \u002F branches (JSON maps) |\n| `--credentials` | authenticated scanning, incl. `mfa_method` (`totp`\u002F`email_otp`\u002F…) + `totp_secret` (JSON list) |\n| `--headers` | extra target HTTP headers as a JSON array of header objects |\n| `--focus` \u002F `--concerns` \u002F `--context` | free-form strings that steer the agents |\n| `--upload-ids` | attach uploaded source\u002Fdocs archives for white-box context |\n| `--notify-on-completion` \u002F `--notification-emails` | email when done |\n\nWithout `--source`, the response is `{ scan_id, title, status }` with `status` = `pending`.\nLocal-source success wraps that platform response as\n`{ source, upload_id, scan: { scan_id, title, status } }`, so automation can retain the exact\napproved manifest and staged-upload identifier alongside the created scan.\n\n### Scan a local workspace in the cloud\n\nFor an agent or CI workflow, bind approval to the exact source snapshot that was reviewed. Run\nthe dry run with the intended source-selection flags, review the manifest and selected paths,\nand capture `source.archive_sha256`. Then repeat the same `--source`, every `--exclude`, and\nany `--include-hidden`, `--include-sensitive`, or `--include-archives` flags with\n`--approve-sha256`:\n\n```bash\nstrix cloud scans start --source . --exclude 'private\u002F' --dry-run --show-files --json\n# After reviewing the output, capture its source.archive_sha256 value:\nSOURCE_SHA256=\"\u003Creviewed source.archive_sha256>\"\n# Repeat every source-selection flag unchanged; a source-only scan infers code_review.\nstrix cloud scans start --source . --exclude 'private\u002F' \\\n  --approve-sha256 \"$SOURCE_SHA256\" --wait\n```\n\nThe CLI rebuilds the archive and refuses the upload if its SHA-256 no longer matches. `--yes`\nhas deliberately narrower semantics: it approves only the snapshot built during that one\ninvocation. Use it for a deliberate human or one-shot approval, not as the second half of a\ndigest-bound agent\u002FCI review. Without a TTY, a source upload requires either matching\n`--approve-sha256` approval or `--yes`; an interactive terminal can instead show the summary,\nthe selected filenames when `--show-files` is set, and a `[y\u002FN]` confirmation for its current\nsnapshot.\n\nThe default selection is privacy-conscious: in a Git worktree it includes tracked files plus untracked files that are not ignored; it honors `.gitignore`, excludes every hidden path component, always excludes `.git`, symlinks, dependencies\u002Fbuild output, secret-like filenames, and nested archives. Add project exclusions to `.strixignore` (one exclude glob per line) or repeat `--exclude GLOB`; a trailing slash such as `private\u002F` excludes that directory subtree.\n\nThe client refuses more than 20,000 files, a file over 25 MiB, more than 250 MiB expanded, or a ZIP over 50 MiB. The service then stream-inflates the ZIP and independently rejects malformed or unsupported entries, unsafe paths, too many entries, oversized entries, excessive expanded data, and oversized compressed input, so an untrusted client cannot bypass the ZIP-bomb controls by forging metadata.\n\nOnly use `--include-hidden`, `--include-sensitive`, or `--include-archives` after the dry-run manifest shows that the scan needs them. Hidden and sensitive files are separate opt-ins: for example, including `.env` requires both `--include-hidden` and `--include-sensitive`.\n\nThe CLI removes its private temporary local archive after every invocation. Once a remote\nupload is staged, a definitive scan rejection causes the CLI to delete it. A network failure,\n`5xx` response, malformed success response, or interruption after scan launch begins is\nambiguous—the platform may have accepted the scan—so the CLI retains the upload and returns\nits `upload_id` with `launch_outcome_unknown: true`. If an automatic deletion attempt cannot\nbe confirmed, it instead returns the retained `upload_id` with `cleanup_unknown: true`.\nBefore retrying, run `strix cloud scans list` to avoid a duplicate scan or charge. If no scan\nis linked to the retained upload, remove it with `strix cloud uploads delete UPLOAD_ID`;\nlinked uploads cannot be deleted.\n\nWith no explicit type, source alone infers `code_review`. Any domain target wins and infers `live_test`, so source plus a deployed domain is the normal white-box live-test workflow. Pass `--engagement-type` when you need to override the inference.\n\n## 3. Wait for completion\n\nPass `--wait` to `scans start` to poll until the scan reaches a final state, or poll yourself with `strix cloud scans get \u003Cscan-id>` (`scans:read`). Bound automation with `--wait-timeout SECONDS`; timeout exits cleanly without cancelling the remote scan. Status flow: `pending → running → completed` (or `failed` \u002F `cancelled`). Scans take minutes to hours — poll on an interval, do not block indefinitely.\n\n## 4. Read findings\n\nThe scan-detail response includes `executive_summary`, `methodology`, `recommendations`, a `findings` severity roll-up, and a `vulnerabilities[]` array. Each vulnerability carries `title, severity, status, cvss, 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`.\n\n```bash\nstrix cloud scans get \u003Cscan-id> --json \\\n  | jq '[\"critical\",\"high\",\"medium\",\"low\",\"info\"] as $order\n       | .vulnerabilities\n       | sort_by(.severity as $s | $order | index($s))\n       | .[] | {title, severity, endpoint, cwe}'\n```\n\nCloud severities are `critical | high | medium | low` and statuses are `open | in_progress | snoozed | fixed | ignored | not_affected`. Sort by an explicit severity order rather than `sort_by(.severity)`, which sorts alphabetically (critical, high, low, medium).\n\nOrg-wide triage across scans: `strix cloud vulns list --severity critical` (`vulnerabilities:read`, and it also filters by `--status`, `--scan-id`, and more). Update triage state with `strix cloud vulns update \u003Cid> --status fixed`. To remediate, hand off to the **fix-security-vulnerabilities-with-strix** skill.\n\n## 5. Export & report\n\n```bash\n# SARIF 2.1.0 for GitHub code scanning \u002F ASPM ingestion\nstrix cloud scans sarif \u003Cscan-id> --output findings.sarif\n\n# Report. Formats: technical (default) | retest | attestation | executive_summary\n# Types: pdf (default) | docx\n# Any report download requires the Enterprise plan. Formats beyond `technical`,\n# DOCX, and white-label branding are Enterprise-only too. Scan must be completed.\nstrix cloud scans report \u003Cscan-id> --format technical --type pdf --output strix-report.pdf\n```\n\nDownloads refuse to replace a file unless `--force` is explicit. Enterprise audit logs can be streamed as JSON or exported without trying to JSON-decode the body:\n\n```bash\nstrix cloud audit list --format csv --all --output audit.csv\nstrix cloud audit list --format ndjson --all --output audit.ndjson\n```\n\n## 6. PR reviews\n\nTrigger an automated security review of a pull request (`pr_reviews:write`). Read the repository's `provider` and `installation_id` with `strix cloud repos list`; both identify the installed source-control integration. The results appear as PR comments and in the dashboard:\n\n```bash\nstrix cloud pr-reviews start \\\n  --provider github \\\n  --installation-id \u003Cinstallation-id> \\\n  --repository-full-name org\u002Fapp \\\n  --pr-number 123\n```\n\nList\u002Finspect with `strix cloud pr-reviews list` and `strix cloud pr-reviews get \u003Cid>`. Repo-level PR-review behavior is configured with `strix cloud pr-reviews settings`.\n\n## 7. Continuous testing (schedules & webhooks)\n\n- **Schedules** (`schedules:write`, Pro plan): `strix cloud schedules create` makes recurring scans, and `strix cloud schedules trigger \u003Cid>` runs one on demand — the managed equivalent of a cron-driven CLI loop.\n- **Webhooks** (`webhooks:write`): `strix cloud webhooks create` subscribes to pentest\u002Fvulnerability lifecycle events such as `scan.completed` and `vulnerability.created` to push results into Slack, ticketing, or your own pipeline instead of polling.\n\nSee the schedules and webhooks sections at [docs.app.strix.ai](https:\u002F\u002Fdocs.app.strix.ai) for payloads.\n\nNetwork connectors are Enterprise-only. `strix cloud connectors create` may return a one-time enrollment command containing credentials; do not paste it into logs, and request it with `--include-command` only when the user is ready to install it. Browser checkout, source-control installation, DNS verification, connector installation, chat sharing, and publishing SARIF to an external provider are user handoffs or explicit external mutations—prepare the command\u002Flink, then obtain the appropriate approval before completing them.\n\n## Safety\n\nOnly scan assets the user's organization owns or is authorized to test. External domain scans require verification (DNS\u002Ffile\u002Fmeta-tag) enforced by the platform — do not try to bypass it.\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"homepage":26},"usestrix","https:\u002F\u002Fdocs.app.strix.ai","main","bc2f998beb877748d6e8c4588942b4ff2cfa495b",".agents\u002Fskills\u002Fmanaged-pentesting-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 managed-pentesting-with-strix",{"tool":41,"command":42},"bunx","bunx skills add Hareesh-Reddy-9126\u002FPS044-SmartHire --skill managed-pentesting-with-strix",{"tool":44,"command":45},"pnpm","pnpm dlx skills add Hareesh-Reddy-9126\u002FPS044-SmartHire --skill managed-pentesting-with-strix","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHareesh-Reddy-9126\u002FPS044-SmartHire\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmanaged-pentesting-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",[],[]]