[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FBKFJ6VJ83ARBC87HZA2QC":3,"skill-same:01M7FBKFJ6VJ83ARBC87HZA2QC":62},{"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":31,"commitSha":32,"skillDirectory":33,"forksCount":34,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":37,"updatedAt":38,"install":39,"resources":51},"01M7FBKFJ6VJ83ARBC87HZA2QC","qa",null,"Browser-based QA verification. Launches a real browser, navigates the app, clicks buttons, fills forms, and tests user flows. Works as a standalone skill or as a phase end condition in campaigns. Requires Playwright (optional dependency, graceful skip if not installed).","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Fqa\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: qa\nlicense: MIT\ndescription: >-\n  Browser-based QA verification. Launches a real browser, navigates the app,\n  clicks buttons, fills forms, and tests user flows. Works as a standalone\n  skill or as a phase end condition in campaigns. Requires Playwright\n  (optional dependency, graceful skip if not installed).\nuser-invocable: true\nauto-trigger: false\ntrigger_keywords:\n  - qa\n  - test the app\n  - click through\n  - does it work\n  - browser test\neffort: high\n---\n\n# \u002Fqa — Browser QA Verification\n\n## Dependency: Playwright\n\n\u002Fqa requires Playwright. It's an optional dependency.\n\n**If Playwright is installed:** full browser QA works.\n**If Playwright is NOT installed:** the skill offers to install it, or falls\nback to \u002Flive-preview (screenshot-only verification).\n\nDetection:\n```bash\nnpx playwright --version 2>\u002Fdev\u002Fnull\n```\n\nInstallation (if user agrees):\n```bash\nnpm install -D playwright\nnpx playwright install chromium\n```\n\nOnly installs Chromium (smallest download, ~150MB). Not Firefox or WebKit\nunless the user asks for cross-browser testing.\n\n**\u002Fdo setup integration:** During setup, if the project is a web app (has\nReact, Next.js, Vue, Svelte, or HTML files), offer to install Playwright:\n\"I see this is a web project. Want to enable browser QA testing? This installs\nPlaywright (~150MB) for interaction testing. (y\u002Fn)\"\n\nIf they say no, \u002Fqa falls back to \u002Flive-preview. No pressure.\n\n## When to Use\n\n- After building a feature (verify it actually works in a browser)\n- As a phase end condition: \"QA verification passes for [flow]\"\n- When \u002Fdo routes \"qa\", \"test the app\", \"does it work\", \"click through it\"\n- When \u002Fcreate-app campaigns reach the verification phase\n- After \u002Flive-preview shows something renders but you need to verify interactions\n\n## Protocol\n\n### Step 1: DISCOVER\n\nBefore testing, understand what to test:\n\n1. Read the project's routes\u002Fpages (from file tree, router config, or package.json scripts)\n2. Read the PRD or campaign file (if exists) for expected user flows\n3. Identify testable flows:\n   - Page loads and renders (baseline)\n   - Navigation between pages\n   - Form submissions\n   - Button click handlers\n   - Auth flows (login, logout, protected routes)\n   - CRUD operations (create, read, update, delete)\n   - Error states (invalid input, network errors)\n\nIf no PRD or campaign exists, ask: \"What should I test? Give me 1-3 user flows.\"\n\n### Step 2: START THE APP\n\nBefore testing, the app needs to be running:\n\n1. Check if a dev server is already running (try curl localhost:3000, 5173, 8080)\n2. If not running, check package.json for start\u002Fdev scripts\n3. Start it: `npm run dev` or equivalent, in background\n4. Wait for the server to be ready (poll the health endpoint or main URL)\n5. If the app won't start, report the error and stop. Don't test a broken app.\n\nTrack whether the agent started the server. If so, kill it on completion.\n\n### Step 3: TEST\n\nFor each flow identified in Step 1, write and run a Playwright script:\n\n```javascript\nconst { chromium } = require('playwright');\n\n(async () => {\n  const browser = await chromium.launch({ headless: true });\n  const page = await browser.newPage();\n\n  \u002F\u002F Navigate\n  await page.goto('http:\u002F\u002Flocalhost:3000');\n\n  \u002F\u002F Verify page loaded\n  const title = await page.title();\n\n  \u002F\u002F Test interactions\n  await page.click('button[data-testid=\"add-todo\"]');\n  await page.fill('input[name=\"title\"]', 'Test todo');\n  await page.click('button[type=\"submit\"]');\n\n  \u002F\u002F Verify result\n  const todoText = await page.textContent('.todo-item:last-child');\n\n  \u002F\u002F Screenshot for evidence\n  await page.screenshot({ path: '.planning\u002Fscreenshots\u002Fqa-flow-1.png' });\n\n  await browser.close();\n})();\n```\n\nFor each test:\n- Navigate to the relevant page\n- Perform the user action (click, fill, submit)\n- Verify the expected outcome (element appears, text changes, navigation occurs)\n- Take a screenshot as evidence\n- Log: PASS or FAIL with description\n\n### Step 4: REPORT\n\nWrite results to `.planning\u002Fqa-report-{date}.md`:\n\n```markdown\n# QA Report: {App Name or Feature}\n\n> Date: {ISO date}\n> Flows tested: {N}\n> Passed: {N}\n> Failed: {N}\n> Screenshots: .planning\u002Fscreenshots\u002Fqa-*.png\n\n## Results\n\n### Flow 1: {description}\n- Steps: {what was done}\n- Expected: {what should happen}\n- Actual: {what did happen}\n- Result: PASS \u002F FAIL\n- Screenshot: {path}\n- Notes: {any observations}\n\n### Flow 2: ...\n```\n\n### Step 5: CAMPAIGN INTEGRATION\n\nWhen running as a phase end condition:\n\nThe campaign file can specify QA conditions:\n```\n| 3 | qa_verify | \u002Fqa passes for: add todo, complete todo, delete todo |\n```\n\n\u002Fqa reads the condition, runs those specific flows, and reports pass\u002Ffail.\nThe phase is complete only if all specified flows pass.\n\n## Cookie and Auth Support\n\nFor apps with authentication:\n\n1. First run the auth flow: navigate to login, fill credentials, submit\n2. Save the browser context (cookies + localStorage state)\n3. Use the saved context for all subsequent tests\n4. This means authenticated flows work without re-logging-in per test\n\nTest credentials should come from `.env.example` or the campaign file.\nNEVER read from `.env` (protected by the hook). Use test accounts only.\n\n## Fallback: No Playwright\n\nIf Playwright isn't installed and the user declines installation:\n\n1. Fall back to \u002Flive-preview (screenshot-only)\n2. Report: \"Browser QA unavailable (Playwright not installed). Visual verification only.\"\n3. Take screenshots of each page that would have been tested\n4. Mark interaction tests as SKIPPED, visual tests as PASS\u002FFAIL\n\n## What \u002Fqa Does NOT Do\n\n- Install Playwright without asking\n- Test in production (localhost only, unless user explicitly provides a URL)\n- Replace unit\u002Fintegration tests (this is user-flow testing, not code testing)\n- Run on every edit (too expensive — invoked explicitly or as phase end condition)\n- Access .env files (uses .env.example or test credentials from campaign)\n\n## Quality Gates\n\n- Every tested flow has all fields filled (steps, expected, actual, result)\n- Screenshots are taken for every flow (pass or fail)\n- Failed flows have enough detail to reproduce the issue\n- The app is actually running before tests execute (not testing a dead server)\n\n## Fringe Cases\n\n**Playwright not installed and user declines**: Fall back to \u002Flive-preview. Mark all interaction tests as SKIPPED in the report. Visual-only verification still runs.\n\n**Dev server won't start**: Report the startup error and stop. Do not attempt to test a server that isn't running. Suggest the user fix the startup error first.\n\n**No routes or pages discoverable**: Ask the user for 1-3 flows to test. Do not guess at routes.\n\n**No UI (API-only project)**: Report \"No UI detected — \u002Fqa requires a browser-accessible interface. Use typecheck and unit tests for API verification.\" Then stop gracefully.\n\n**If .planning\u002Fscreenshots\u002F does not exist**: Create it before saving screenshots. If `.planning\u002F` doesn't exist, save screenshots to a `qa-screenshots\u002F` directory in the project root and note the path in the report.\n\n## Codex App Artifact Manifest\n\nAfter saving screenshots, videos, rendered PDFs, or QA reports in Codex, register each durable artifact so the Codex app\u002Fbrowser workflow can find it later:\n\n```bash\nnode scripts\u002Fcodex-app-artifacts.js record --workflow qa --kind screenshot --path \".planning\u002Fscreenshots\u002Fqa-flow-1.png\" --status pass\n```\n\nThe manifest lives at `.planning\u002Fartifacts\u002Fcodex-app-evidence.jsonl`.\n\nBefore reporting QA as complete in Codex, verify the manifest points at real files:\n\n```bash\nnode scripts\u002Fcodex-app-artifacts.js verify --require-artifacts\n```\n\n## Contextual Gates\n\n**Disclosure:** May start a dev server; saves screenshots and report to `.planning\u002F`. States server ownership before starting.\n**Reversibility:** amber — creates report and screenshots; dev server stopped only if this skill started it. Delete generated files to undo.\n**Trust gates:** Any. Familiar (5+) to run against external\u002Fproduction URLs.\n\n## Exit Protocol\n\n```\n---HANDOFF---\n- QA Report: .planning\u002Fqa-report-{date}.md\n- Flows tested: {N}\n- Passed: {N} | Failed: {N} | Skipped: {N}\n- Screenshots: .planning\u002Fscreenshots\u002Fqa-*.png\n- Server: {started by agent (killed) | was already running (left running)}\n- Reversibility: amber — delete `.planning\u002Fqa-report-{date}.md` and `screenshots\u002Fqa-*.png` to undo\n---\n```\n","# \u002Fqa — Browser QA Verification\n\n## Dependency: Playwright\n\n\u002Fqa requires Playwright. It's an optional dependency.\n\n**If Playwright is installed:** full browser QA works.\n**If Playwright is NOT installed:** the skill offers to install it, or falls\nback to \u002Flive-preview (screenshot-only verification).\n\nDetection:\n```bash\nnpx playwright --version 2>\u002Fdev\u002Fnull\n```\n\nInstallation (if user agrees):\n```bash\nnpm install -D playwright\nnpx playwright install chromium\n```\n\nOnly installs Chromium (smallest download, ~150MB). Not Firefox or WebKit\nunless the user asks for cross-browser testing.\n\n**\u002Fdo setup integration:** During setup, if the project is a web app (has\nReact, Next.js, Vue, Svelte, or HTML files), offer to install Playwright:\n\"I see this is a web project. Want to enable browser QA testing? This installs\nPlaywright (~150MB) for interaction testing. (y\u002Fn)\"\n\nIf they say no, \u002Fqa falls back to \u002Flive-preview. No pressure.\n\n## When to Use\n\n- After building a feature (verify it actually works in a browser)\n- As a phase end condition: \"QA verification passes for [flow]\"\n- When \u002Fdo routes \"qa\", \"test the app\", \"does it work\", \"click through it\"\n- When \u002Fcreate-app campaigns reach the verification phase\n- After \u002Flive-preview shows something renders but you need to verify interactions\n\n## Protocol\n\n### Step 1: DISCOVER\n\nBefore testing, understand what to test:\n\n1. Read the project's routes\u002Fpages (from file tree, router config, or package.json scripts)\n2. Read the PRD or campaign file (if exists) for expected user flows\n3. Identify testable flows:\n   - Page loads and renders (baseline)\n   - Navigation between pages\n   - Form submissions\n   - Button click handlers\n   - Auth flows (login, logout, protected routes)\n   - CRUD operations (create, read, update, delete)\n   - Error states (invalid input, network errors)\n\nIf no PRD or campaign exists, ask: \"What should I test? Give me 1-3 user flows.\"\n\n### Step 2: START THE APP\n\nBefore testing, the app needs to be running:\n\n1. Check if a dev server is already running (try curl localhost:3000, 5173, 8080)\n2. If not running, check package.json for start\u002Fdev scripts\n3. Start it: `npm run dev` or equivalent, in background\n4. Wait for the server to be ready (poll the health endpoint or main URL)\n5. If the app won't start, report the error and stop. Don't test a broken app.\n\nTrack whether the agent started the server. If so, kill it on completion.\n\n### Step 3: TEST\n\nFor each flow identified in Step 1, write and run a Playwright script:\n\n```javascript\nconst { chromium } = require('playwright');\n\n(async () => {\n  const browser = await chromium.launch({ headless: true });\n  const page = await browser.newPage();\n\n  \u002F\u002F Navigate\n  await page.goto('http:\u002F\u002Flocalhost:3000');\n\n  \u002F\u002F Verify page loaded\n  const title = await page.title();\n\n  \u002F\u002F Test interactions\n  await page.click('button[data-testid=\"add-todo\"]');\n  await page.fill('input[name=\"title\"]', 'Test todo');\n  await page.click('button[type=\"submit\"]');\n\n  \u002F\u002F Verify result\n  const todoText = await page.textContent('.todo-item:last-child');\n\n  \u002F\u002F Screenshot for evidence\n  await page.screenshot({ path: '.planning\u002Fscreenshots\u002Fqa-flow-1.png' });\n\n  await browser.close();\n})();\n```\n\nFor each test:\n- Navigate to the relevant page\n- Perform the user action (click, fill, submit)\n- Verify the expected outcome (element appears, text changes, navigation occurs)\n- Take a screenshot as evidence\n- Log: PASS or FAIL with description\n\n### Step 4: REPORT\n\nWrite results to `.planning\u002Fqa-report-{date}.md`:\n\n```markdown\n# QA Report: {App Name or Feature}\n\n> Date: {ISO date}\n> Flows tested: {N}\n> Passed: {N}\n> Failed: {N}\n> Screenshots: .planning\u002Fscreenshots\u002Fqa-*.png\n\n## Results\n\n### Flow 1: {description}\n- Steps: {what was done}\n- Expected: {what should happen}\n- Actual: {what did happen}\n- Result: PASS \u002F FAIL\n- Screenshot: {path}\n- Notes: {any observations}\n\n### Flow 2: ...\n```\n\n### Step 5: CAMPAIGN INTEGRATION\n\nWhen running as a phase end condition:\n\nThe campaign file can specify QA conditions:\n```\n| 3 | qa_verify | \u002Fqa passes for: add todo, complete todo, delete todo |\n```\n\n\u002Fqa reads the condition, runs those specific flows, and reports pass\u002Ffail.\nThe phase is complete only if all specified flows pass.\n\n## Cookie and Auth Support\n\nFor apps with authentication:\n\n1. First run the auth flow: navigate to login, fill credentials, submit\n2. Save the browser context (cookies + localStorage state)\n3. Use the saved context for all subsequent tests\n4. This means authenticated flows work without re-logging-in per test\n\nTest credentials should come from `.env.example` or the campaign file.\nNEVER read from `.env` (protected by the hook). Use test accounts only.\n\n## Fallback: No Playwright\n\nIf Playwright isn't installed and the user declines installation:\n\n1. Fall back to \u002Flive-preview (screenshot-only)\n2. Report: \"Browser QA unavailable (Playwright not installed). Visual verification only.\"\n3. Take screenshots of each page that would have been tested\n4. Mark interaction tests as SKIPPED, visual tests as PASS\u002FFAIL\n\n## What \u002Fqa Does NOT Do\n\n- Install Playwright without asking\n- Test in production (localhost only, unless user explicitly provides a URL)\n- Replace unit\u002Fintegration tests (this is user-flow testing, not code testing)\n- Run on every edit (too expensive — invoked explicitly or as phase end condition)\n- Access .env files (uses .env.example or test credentials from campaign)\n\n## Quality Gates\n\n- Every tested flow has all fields filled (steps, expected, actual, result)\n- Screenshots are taken for every flow (pass or fail)\n- Failed flows have enough detail to reproduce the issue\n- The app is actually running before tests execute (not testing a dead server)\n\n## Fringe Cases\n\n**Playwright not installed and user declines**: Fall back to \u002Flive-preview. Mark all interaction tests as SKIPPED in the report. Visual-only verification still runs.\n\n**Dev server won't start**: Report the startup error and stop. Do not attempt to test a server that isn't running. Suggest the user fix the startup error first.\n\n**No routes or pages discoverable**: Ask the user for 1-3 flows to test. Do not guess at routes.\n\n**No UI (API-only project)**: Report \"No UI detected — \u002Fqa requires a browser-accessible interface. Use typecheck and unit tests for API verification.\" Then stop gracefully.\n\n**If .planning\u002Fscreenshots\u002F does not exist**: Create it before saving screenshots. If `.planning\u002F` doesn't exist, save screenshots to a `qa-screenshots\u002F` directory in the project root and note the path in the report.\n\n## Codex App Artifact Manifest\n\nAfter saving screenshots, videos, rendered PDFs, or QA reports in Codex, register each durable artifact so the Codex app\u002Fbrowser workflow can find it later:\n\n```bash\nnode scripts\u002Fcodex-app-artifacts.js record --workflow qa --kind screenshot --path \".planning\u002Fscreenshots\u002Fqa-flow-1.png\" --status pass\n```\n\nThe manifest lives at `.planning\u002Fartifacts\u002Fcodex-app-evidence.jsonl`.\n\nBefore reporting QA as complete in Codex, verify the manifest points at real files:\n\n```bash\nnode scripts\u002Fcodex-app-artifacts.js verify --require-artifacts\n```\n\n## Contextual Gates\n\n**Disclosure:** May start a dev server; saves screenshots and report to `.planning\u002F`. States server ownership before starting.\n**Reversibility:** amber — creates report and screenshots; dev server stopped only if this skill started it. Delete generated files to undo.\n**Trust gates:** Any. Familiar (5+) to run against external\u002Fproduction URLs.\n\n## Exit Protocol\n\n```\n---HANDOFF---\n- QA Report: .planning\u002Fqa-report-{date}.md\n- Flows tested: {N}\n- Passed: {N} | Failed: {N} | Skipped: {N}\n- Screenshots: .planning\u002Fscreenshots\u002Fqa-*.png\n- Server: {started by agent (killed) | was already running (left running)}\n- Reversibility: amber — delete `.planning\u002Fqa-report-{date}.md` and `screenshots\u002Fqa-*.png` to undo\n---\n```\n",{"name":5,"effort":24,"license":15,"description":7,"auto-trigger":20,"user-invocable":25,"trigger_keywords":26},"high",true,[5,27,28,29,30],"test the app","click through","does it work","browser test","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","06-前端与设计\u002Fqa",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":25},[41,44,47],{"tool":42,"command":43},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill qa",{"tool":45,"command":46},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill qa",{"tool":48,"command":49},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill qa","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Fqa\u002FSKILL.md",[52,58],{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"__benchmarks__\u002Fno-playwright.md","REFERENCE","参考文档",797,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Fqa\u002F__benchmarks__\u002Fno-playwright.md",{"path":59,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":60,"sourceHtmlUrl":61},"__benchmarks__\u002Fno-server.md",826,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Fqa\u002F__benchmarks__\u002Fno-server.md",[63,70,75,82,89,96],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],{"skillNo":71,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]