[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75K6DFGPTZ1HKJATX651JAM":3,"skill-same:01M75K6DFGPTZ1HKJATX651JAM":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M75K6DFGPTZ1HKJATX651JAM","testrail",null,"Sync tests with TestRail. Use when user mentions \"testrail\", \"test management\", \"test cases\", \"test run\", \"sync test cases\", \"push results to testrail\", or \"import from testrail\".","agisota\u002Fold-one","agisota","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F121413592?v=4","01M75B4BRNT67EC1NDRT8QZEP2","01M75B4BS7QR9VP580MSCPTS3X",3,"MIT","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Ftestrail\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: \"testrail\"\ndescription: >-\n  Sync tests with TestRail. Use when user mentions \"testrail\", \"test management\",\n  \"test cases\", \"test run\", \"sync test cases\", \"push results to testrail\",\n  or \"import from testrail\".\n---\n\n# TestRail Integration\n\nBidirectional sync between Playwright tests and TestRail test management.\n\n## Prerequisites\n\nEnvironment variables must be set:\n- `TESTRAIL_URL` — e.g., `https:\u002F\u002Fyour-instance.testrail.io`\n- `TESTRAIL_USER` — your email\n- `TESTRAIL_API_KEY` — API key from TestRail\n\nIf not set, inform the user how to configure them and stop.\n\n## Capabilities\n\n### 1. Import Test Cases → Generate Playwright Tests\n\n```\n\u002Fpw:testrail import --project \u003Cid> --suite \u003Cid>\n```\n\nSteps:\n1. Call `testrail_get_cases` MCP tool to fetch test cases\n2. For each test case:\n   - Read title, preconditions, steps, expected results\n   - Map to a Playwright test using appropriate template\n   - Include TestRail case ID as test annotation: `test.info().annotations.push({ type: 'testrail', description: 'C12345' })`\n3. Generate test files grouped by section\n4. Report: X cases imported, Y tests generated\n\n### 2. Push Test Results → TestRail\n\n```\n\u002Fpw:testrail push --run \u003Cid>\n```\n\nSteps:\n1. Run Playwright tests with JSON reporter:\n   ```bash\n   npx playwright test --reporter=json > test-results.json\n   ```\n2. Parse results: map each test to its TestRail case ID (from annotations)\n3. Call `testrail_add_result` MCP tool for each test:\n   - Pass → status_id: 1\n   - Fail → status_id: 5, include error message\n   - Skip → status_id: 2\n4. Report: X results pushed, Y passed, Z failed\n\n### 3. Create Test Run\n\n```\n\u002Fpw:testrail run --project \u003Cid> --name \"Sprint 42 Regression\"\n```\n\nSteps:\n1. Call `testrail_add_run` MCP tool\n2. Include all test case IDs found in Playwright test annotations\n3. Return run ID for result pushing\n\n### 4. Sync Status\n\n```\n\u002Fpw:testrail status --project \u003Cid>\n```\n\nSteps:\n1. Fetch test cases from TestRail\n2. Scan local Playwright tests for TestRail annotations\n3. Report coverage:\n   ```\n   TestRail cases: 150\n   Playwright tests with TestRail IDs: 120\n   Unlinked TestRail cases: 30\n   Playwright tests without TestRail IDs: 15\n   ```\n\n### 5. Update Test Cases in TestRail\n\n```\n\u002Fpw:testrail update --case \u003Cid>\n```\n\nSteps:\n1. Read the Playwright test for this case ID\n2. Extract steps and expected results from test code\n3. Call `testrail_update_case` MCP tool to update steps\n\n## MCP Tools Used\n\n| Tool | When |\n|---|---|\n| `testrail_get_projects` | List available projects |\n| `testrail_get_suites` | List suites in project |\n| `testrail_get_cases` | Read test cases |\n| `testrail_add_case` | Create new test case |\n| `testrail_update_case` | Update existing case |\n| `testrail_add_run` | Create test run |\n| `testrail_add_result` | Push individual result |\n| `testrail_get_results` | Read historical results |\n\n## Test Annotation Format\n\nAll Playwright tests linked to TestRail include:\n\n```typescript\ntest('should login successfully', async ({ page }) => {\n  test.info().annotations.push({\n    type: 'testrail',\n    description: 'C12345',\n  });\n  \u002F\u002F ... test code\n});\n```\n\nThis annotation is the bridge between Playwright and TestRail.\n\n## Output\n\n- Operation summary with counts\n- Any errors or unmatched cases\n- Link to TestRail run\u002Fresults\n","# TestRail Integration\n\nBidirectional sync between Playwright tests and TestRail test management.\n\n## Prerequisites\n\nEnvironment variables must be set:\n- `TESTRAIL_URL` — e.g., `https:\u002F\u002Fyour-instance.testrail.io`\n- `TESTRAIL_USER` — your email\n- `TESTRAIL_API_KEY` — API key from TestRail\n\nIf not set, inform the user how to configure them and stop.\n\n## Capabilities\n\n### 1. Import Test Cases → Generate Playwright Tests\n\n```\n\u002Fpw:testrail import --project \u003Cid> --suite \u003Cid>\n```\n\nSteps:\n1. Call `testrail_get_cases` MCP tool to fetch test cases\n2. For each test case:\n   - Read title, preconditions, steps, expected results\n   - Map to a Playwright test using appropriate template\n   - Include TestRail case ID as test annotation: `test.info().annotations.push({ type: 'testrail', description: 'C12345' })`\n3. Generate test files grouped by section\n4. Report: X cases imported, Y tests generated\n\n### 2. Push Test Results → TestRail\n\n```\n\u002Fpw:testrail push --run \u003Cid>\n```\n\nSteps:\n1. Run Playwright tests with JSON reporter:\n   ```bash\n   npx playwright test --reporter=json > test-results.json\n   ```\n2. Parse results: map each test to its TestRail case ID (from annotations)\n3. Call `testrail_add_result` MCP tool for each test:\n   - Pass → status_id: 1\n   - Fail → status_id: 5, include error message\n   - Skip → status_id: 2\n4. Report: X results pushed, Y passed, Z failed\n\n### 3. Create Test Run\n\n```\n\u002Fpw:testrail run --project \u003Cid> --name \"Sprint 42 Regression\"\n```\n\nSteps:\n1. Call `testrail_add_run` MCP tool\n2. Include all test case IDs found in Playwright test annotations\n3. Return run ID for result pushing\n\n### 4. Sync Status\n\n```\n\u002Fpw:testrail status --project \u003Cid>\n```\n\nSteps:\n1. Fetch test cases from TestRail\n2. Scan local Playwright tests for TestRail annotations\n3. Report coverage:\n   ```\n   TestRail cases: 150\n   Playwright tests with TestRail IDs: 120\n   Unlinked TestRail cases: 30\n   Playwright tests without TestRail IDs: 15\n   ```\n\n### 5. Update Test Cases in TestRail\n\n```\n\u002Fpw:testrail update --case \u003Cid>\n```\n\nSteps:\n1. Read the Playwright test for this case ID\n2. Extract steps and expected results from test code\n3. Call `testrail_update_case` MCP tool to update steps\n\n## MCP Tools Used\n\n| Tool | When |\n|---|---|\n| `testrail_get_projects` | List available projects |\n| `testrail_get_suites` | List suites in project |\n| `testrail_get_cases` | Read test cases |\n| `testrail_add_case` | Create new test case |\n| `testrail_update_case` | Update existing case |\n| `testrail_add_run` | Create test run |\n| `testrail_add_result` | Push individual result |\n| `testrail_get_results` | Read historical results |\n\n## Test Annotation Format\n\nAll Playwright tests linked to TestRail include:\n\n```typescript\ntest('should login successfully', async ({ page }) => {\n  test.info().annotations.push({\n    type: 'testrail',\n    description: 'C12345',\n  });\n  \u002F\u002F ... test code\n});\n```\n\nThis annotation is the bridge between Playwright and TestRail.\n\n## Output\n\n- Operation summary with counts\n- Any errors or unmatched cases\n- Link to TestRail run\u002Fresults\n",{"name":5,"description":7},"main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Ftestrail",1,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one","https:\u002F\u002Fagisota.github.io\u002Fold-one\u002F","https:\u002F\u002Fgithub.com\u002Fagisota","pzd.world","2026-07-04 22:32:06",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add agisota\u002Fold-one --skill testrail",{"tool":38,"command":39},"bunx","bunx skills add agisota\u002Fold-one --skill testrail",{"tool":41,"command":42},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill testrail","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Ftestrail\u002FSKILL.md",true,[],[47,54,61,70,77,84],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":18},"01M75KRGZWQWE9JDBS6RX42NWV","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M75KRCZHKE0ZYAQFFYHS0YNP","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":65,"licenseFileUrl":66,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":18},"01M75KR94KYQ30DTE1P9WNDAE0","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M75KR3H13YJ9QHMD49818FA1","yara-rule-authoring","Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyara-rule-authoring\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M75KQMPY8A4Y8XTDD2DT0M9T","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M75KQHNZ0ANZNJGZY6M8MDAK","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]