[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78DR79Q0SWV2V4VBMV3KM4Z":3,"skill-same:01M78DR79Q0SWV2V4VBMV3KM4Z":45},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M78DR79Q0SWV2V4VBMV3KM4Z","review-security",null,"Review code changes with Security Review subagent.","P-Core-System\u002Fpcore-orchestra","P-Core-System","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F316099351?v=4","01M78DJ0920WA62RQ0Q00B81HQ","P Core System","01M78DJ09XWRZS3VDK927QW72Z",0,"MIT","https:\u002F\u002Fgithub.com\u002FP-Core-System\u002Fpcore-orchestra\u002Fblob\u002Fmain\u002Fbundle\u002Fskills-cursor\u002Freview-security\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: review-security\ndescription: Review code changes with Security Review subagent.\n---\n# Review Security\n\nUse this skill when the user asks to run `\u002Freview-security`.\n\nLaunch exactly one `security-review` subagent with:\n\n- `readonly: true`\n- `run_in_background: false` unless explicitly asked to run in background\n- `description: \"Security Review\"`\n- `subagent_type: \"security-review\"`\n\nThe review subagent computes the local diff from the repository path, so do not compute the diff yourself before launching it. The repository path should be the active workspace or repository root for the code the user wants reviewed.\n\nBy default, the review subagent infers the repository's actual base branch, such as `main`, when computing `branch changes`. In most cases, do not provide `Base Branch`. Only provide it if you know the current branch or PR should be compared against a specific branch other than the repository's default base branch, such as when you created the current branch from another branch.\n\nSpecial case: if the user explicitly asks to review a specific PR or branch, make sure that target is checked out before launching the subagent:\n- Examples include `github.com\u002F... \u002Freview`, `review {link}`, or `review {branch-name}`.\n- Resolve the provided PR link, PR number, or branch name to the PR head branch or named branch.\n- Check whether the target branch is already the currently checked out local branch. If it is, continue.\n- If a different branch is currently checked out, try to switch to the target branch.\n- If Git refuses to switch because local files would be overwritten, conflicts need resolution, or another checkout blocker occurs, explain the blocker and ask whether the user wants to stash local changes before retrying.\n- Only stash after the user confirms. If the stash succeeds, retry switching to the target branch.\n- Launch the review subagent only after the target branch is checked out locally.\n\nUse this exact prompt shape:\n\n```text\nFull Repository Path: \u003Cabsolute repository path>\nDiff: \u003Cone of: \"branch changes\", \"uncommitted changes\">\nBase Branch: \u003Conly include this line when reviewing branch changes against a known specific base branch>\nCustom Instructions: \u003Conly include this line when the user gave specific review instructions>\n```\n\nDefault to `branch changes`, which reviews branch changes against the merge-base with the default\u002Fbase branch, including committed, staged, and unstaged changes. If the user asks to review only uncommitted, local working tree, dirty, or not-yet-committed changes, use `uncommitted changes`.\n\nIf the review subagent fails before producing findings, inspect the failure text.\n\n- If the failure is caused by calling the subagent incorrectly, such as a missing `Full Repository Path`, missing `Diff`, wrong prompt shape, or wrong subagent type, correct the invocation and retry it once immediately.\n- For any other subagent failure, retry once with the same prompt shape.\n- If the same failure persists after the retry, stop. Briefly tell the user that the review subagent could not complete and include the short error or blocker. Do not keep retrying.\n\nAfter the subagent finishes, summarize the result:\n\n- If it reports that no diff was found or the diff is empty, tell the user in one sentence that there was no diff to review.\n- If it found no issues, give a one-line status such as \"Security review found 2 findings \u002F Security review found no issues\".\n- If it found issues, print a compact markdown table with one row per finding, sorted by severity (highest first), using exactly these columns: Severity, Location (file:line), Finding. Put the file and line in the location column as `file:line`.\n\nDo not fix findings or rerun review unless the user explicitly asks for that next step.\n","# Review Security\n\nUse this skill when the user asks to run `\u002Freview-security`.\n\nLaunch exactly one `security-review` subagent with:\n\n- `readonly: true`\n- `run_in_background: false` unless explicitly asked to run in background\n- `description: \"Security Review\"`\n- `subagent_type: \"security-review\"`\n\nThe review subagent computes the local diff from the repository path, so do not compute the diff yourself before launching it. The repository path should be the active workspace or repository root for the code the user wants reviewed.\n\nBy default, the review subagent infers the repository's actual base branch, such as `main`, when computing `branch changes`. In most cases, do not provide `Base Branch`. Only provide it if you know the current branch or PR should be compared against a specific branch other than the repository's default base branch, such as when you created the current branch from another branch.\n\nSpecial case: if the user explicitly asks to review a specific PR or branch, make sure that target is checked out before launching the subagent:\n- Examples include `github.com\u002F... \u002Freview`, `review {link}`, or `review {branch-name}`.\n- Resolve the provided PR link, PR number, or branch name to the PR head branch or named branch.\n- Check whether the target branch is already the currently checked out local branch. If it is, continue.\n- If a different branch is currently checked out, try to switch to the target branch.\n- If Git refuses to switch because local files would be overwritten, conflicts need resolution, or another checkout blocker occurs, explain the blocker and ask whether the user wants to stash local changes before retrying.\n- Only stash after the user confirms. If the stash succeeds, retry switching to the target branch.\n- Launch the review subagent only after the target branch is checked out locally.\n\nUse this exact prompt shape:\n\n```text\nFull Repository Path: \u003Cabsolute repository path>\nDiff: \u003Cone of: \"branch changes\", \"uncommitted changes\">\nBase Branch: \u003Conly include this line when reviewing branch changes against a known specific base branch>\nCustom Instructions: \u003Conly include this line when the user gave specific review instructions>\n```\n\nDefault to `branch changes`, which reviews branch changes against the merge-base with the default\u002Fbase branch, including committed, staged, and unstaged changes. If the user asks to review only uncommitted, local working tree, dirty, or not-yet-committed changes, use `uncommitted changes`.\n\nIf the review subagent fails before producing findings, inspect the failure text.\n\n- If the failure is caused by calling the subagent incorrectly, such as a missing `Full Repository Path`, missing `Diff`, wrong prompt shape, or wrong subagent type, correct the invocation and retry it once immediately.\n- For any other subagent failure, retry once with the same prompt shape.\n- If the same failure persists after the retry, stop. Briefly tell the user that the review subagent could not complete and include the short error or blocker. Do not keep retrying.\n\nAfter the subagent finishes, summarize the result:\n\n- If it reports that no diff was found or the diff is empty, tell the user in one sentence that there was no diff to review.\n- If it found no issues, give a one-line status such as \"Security review found 2 findings \u002F Security review found no issues\".\n- If it found issues, print a compact markdown table with one row per finding, sorted by severity (highest first), using exactly these columns: Severity, Location (file:line), Finding. Put the file and line in the location column as `file:line`.\n\nDo not fix findings or rerun review unless the user explicitly asks for that next step.\n",{"name":5,"description":7},"main","5a348537f6ee031f76c168e397c0d023f35ef333","bundle\u002Fskills-cursor\u002Freview-security","https:\u002F\u002Fgithub.com\u002FP-Core-System\u002Fpcore-orchestra","https:\u002F\u002Fgithub.com\u002FP-Core-System","P Core System — the P-Core family: trading, AI brain, assistant, orchestration, and web AI server.","2026-11-13 11:33:11",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add P-Core-System\u002Fpcore-orchestra --skill review-security",{"tool":37,"command":38},"bunx","bunx skills add P-Core-System\u002Fpcore-orchestra --skill review-security",{"tool":40,"command":41},"pnpm","pnpm dlx skills add P-Core-System\u002Fpcore-orchestra --skill review-security","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FP-Core-System\u002Fpcore-orchestra\u002Fblob\u002Fmain\u002Fbundle\u002Fskills-cursor\u002Freview-security\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M78DYATRNCN2NFKA4YRBG0T9","wrangler","Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002FP-Core-System\u002Fpcore-orchestra\u002Fblob\u002Fmain\u002Fbundle\u002Fskills\u002Fwrangler\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M78DY6XPJ7B09HWH01PGQTJZ","workers-best-practices","Reviews and authors Cloudflare Workers code against production best practices. Load when writing new Workers, reviewing Worker code, configuring wrangler.jsonc, or checking for common Workers anti-patterns (streaming, floating promises, global state, secrets, bindings, observability). Biases towards retrieval from Cloudflare docs over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002FP-Core-System\u002Fpcore-orchestra\u002Fblob\u002Fmain\u002Fbundle\u002Fskills\u002Fworkers-best-practices\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M78DY267V5PK9KD65ENG451F","web-perf","Analyzes web performance using Chrome DevTools MCP. Measures Core Web Vitals (LCP, INP, CLS) and supplementary metrics (FCP, TBT, Speed Index), identifies render-blocking resources, network dependency chains, layout shifts, caching issues, and accessibility gaps. Use when asked to audit, profile, debug, or optimize page load performance, Lighthouse scores, or site speed. Biases towards retrieval from current documentation over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002FP-Core-System\u002Fpcore-orchestra\u002Fblob\u002Fmain\u002Fbundle\u002Fskills\u002Fweb-perf\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M78DXXT4TWE2K8M0E9V417J9","web-design-master","Professional web design standard (\"AI Professional Web Design Master Prompt\") covering page\u002Fsection\u002Flayout design, visual hierarchy, color systems, typography scales, 8-point grid spacing, responsive breakpoints, accessibility, and design QA review. Use when designing or building any page, section, or layout so it looks deliberately designed by a professional product team rather than a generic AI template.","https:\u002F\u002Fgithub.com\u002FP-Core-System\u002Fpcore-orchestra\u002Fblob\u002Fmain\u002Fbundle\u002Fskills\u002Fweb-design-master\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M78DXTPQ1XARW18D46JFY5AP","verification-before-completion","Require command evidence before claiming done. Use proactively before VERIFY_PASS, ORCHESTRA_COMPLETE, or \"all fixed\" statements. Run tests, lint, health, or git checks — never trust claims without output.","https:\u002F\u002Fgithub.com\u002FP-Core-System\u002Fpcore-orchestra\u002Fblob\u002Fmain\u002Fbundle\u002Fskills\u002Fverification-before-completion\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":15,"licenseFileUrl":85,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M78DXKFTZ00TJRWK84FNHGVH","ui-ux-pro-max","UI\u002FUX design intelligence for web and mobile. Searchable local database with 84 styles, 192 color palettes, 74 font pairings, 192 product types, 98 UX guidelines, 104 icon entries, 16 GSAP motion presets, and 25 chart types across 22 stacks (React, Next.js, Vue, Nuxt, Svelte, Astro, SwiftUI, React Native, Flutter, Tailwind, shadcn\u002Fui, Jetpack Compose, Angular, Laravel, JavaFX, WPF, WinUI, Avalonia, Uno Platform, UWP, Three.js, and HTML\u002FCSS). Use when designing, building, or reviewing UI: pages, components, color schemes, typography, layout, accessibility, animation, or data visualization.","https:\u002F\u002Fgithub.com\u002FP-Core-System\u002Fpcore-orchestra\u002Fblob\u002Fmain\u002Fbundle\u002Fskills\u002Fui-ux-pro-max\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FP-Core-System\u002Fpcore-orchestra\u002Fblob\u002Fmain\u002Fbundle\u002Fskills\u002Fui-ux-pro-max\u002FSKILL.md",[],[]]