[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CBHS70RYX772NHGA65EPJM":3,"skill-same:01M7CBHS70RYX772NHGA65EPJM":57},{"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":29,"commitSha":30,"skillDirectory":31,"forksCount":32,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":6,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M7CBHS70RYX772NHGA65EPJM","sf-testing",null,"Apex test execution, coverage analysis, and test-fix loops with 120-point scoring. TRIGGER when: user runs Apex tests, checks code coverage, fixes failing tests, or touches *Test.cls \u002F *_Test.cls files. DO NOT TRIGGER when: writing Apex production code (use sf-apex), Agentforce agent testing (use sf-ai-agentforce-testing), or Jest\u002FLWC tests (use sf-lwc).","om-scogo\u002Fskillsh-scraper","om-scogo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160466840?v=4","01M79AWB6DFVCQ7RK70CS34B96","Om Achrekar","01M79AWB6ZM9SKR8KDH1WSSM22",0,"MIT","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fjaganpro-sf-skills\u002Fsf-testing\u002FSkill.md",[],[],"2026-11-15 14:19:17",false,"---\nname: sf-testing\ndescription: >\n  Apex test execution, coverage analysis, and test-fix loops with 120-point scoring.\n  TRIGGER when: user runs Apex tests, checks code coverage, fixes failing tests,\n  or touches *Test.cls \u002F *_Test.cls files.\n  DO NOT TRIGGER when: writing Apex production code (use sf-apex), Agentforce agent\n  testing (use sf-ai-agentforce-testing), or Jest\u002FLWC tests (use sf-lwc).\nlicense: MIT\nmetadata:\n  version: \"1.1.0\"\n  author: \"Jag Valaiyapathy\"\n  scoring: \"120 points across 6 categories\"\n---\n\n# sf-testing: Salesforce Test Execution & Coverage Analysis\n\nUse this skill when the user needs **Apex test execution and failure analysis**: running tests, checking coverage, interpreting failures, improving coverage, and managing a disciplined test-fix loop for Salesforce code.\n\n## When This Skill Owns the Task\n\nUse `sf-testing` when the work involves:\n- `sf apex run test` workflows\n- Apex unit-test failures\n- code coverage analysis\n- identifying uncovered lines and missing test scenarios\n- structured test-fix loops for Apex code\n\nDelegate elsewhere when the user is:\n- writing or refactoring production Apex → [sf-apex](..\u002Fsf-apex\u002FSKILL.md)\n- testing Agentforce agents → [sf-ai-agentforce-testing](..\u002Fsf-ai-agentforce-testing\u002FSKILL.md)\n- testing LWC with Jest → [sf-lwc](..\u002Fsf-lwc\u002FSKILL.md)\n\n---\n\n## Required Context to Gather First\n\nAsk for or infer:\n- target org alias\n- desired test scope: single class, specific methods, suite, or local tests\n- coverage threshold expectation\n- whether the user wants diagnosis only or a test-fix loop\n- whether related test data factories already exist\n\n---\n\n## Recommended Workflow\n\n### 1. Discover test scope\nIdentify:\n- existing test classes\n- target production classes\n- test data factories \u002F setup helpers\n\n### 2. Run the smallest useful test set first\nStart narrow when debugging a failure; widen only after the fix is stable.\n\n### 3. Analyze results\nFocus on:\n- failing methods\n- exception types and stack traces\n- uncovered lines \u002F weak coverage areas\n- whether failures indicate bad test data, brittle assertions, or broken production logic\n\n### 4. Run a disciplined fix loop\nWhen the issue is code or test quality:\n- delegate code fixes to [sf-apex](..\u002Fsf-apex\u002FSKILL.md) when needed\n- add or improve tests\n- rerun focused tests before broader regression\n\n### 5. Improve coverage intentionally\nCover:\n- positive path\n- negative \u002F exception path\n- bulk path (251+ records where appropriate)\n- callout or async path when relevant\n\n---\n\n## High-Signal Rules\n\n- default to `SeeAllData=false`\n- every test should assert meaningful outcomes\n- test bulk behavior, not just single-record happy paths\n- use factories \u002F `@TestSetup` when they improve clarity and speed\n- pair `Test.startTest()` with `Test.stopTest()` when async behavior matters\n- do not hide flaky org dependencies inside tests\n\n---\n\n## Output Format\n\nWhen finishing, report in this order:\n1. **What tests were run**\n2. **Pass\u002Ffail summary**\n3. **Coverage result**\n4. **Root-cause findings**\n5. **Fix or next-run recommendation**\n\nSuggested shape:\n\n```text\nTest run: \u003Cscope>\nOrg: \u003Calias>\nResult: \u003Cpassed \u002F partial \u002F failed>\nCoverage: \u003Cpercent \u002F key classes>\nIssues: \u003Chighest-signal failures>\nNext step: \u003Cfix class, add test, rerun scope, or widen regression>\n```\n\n---\n\n## Cross-Skill Integration\n\n| Need | Delegate to | Reason |\n|---|---|---|\n| fix production code or author tests | [sf-apex](..\u002Fsf-apex\u002FSKILL.md) | code generation and repair |\n| create bulk \u002F edge-case data | [sf-data](..\u002Fsf-data\u002FSKILL.md) | realistic test datasets |\n| deploy updated tests | [sf-deploy](..\u002Fsf-deploy\u002FSKILL.md) | rollout |\n| inspect detailed runtime logs | [sf-debug](..\u002Fsf-debug\u002FSKILL.md) | deeper failure analysis |\n\n---\n\n## Reference Map\n\n### Start here\n- [references\u002Fcli-commands.md](references\u002Fcli-commands.md)\n- [references\u002Ftest-patterns.md](references\u002Ftest-patterns.md)\n- [references\u002Ftesting-best-practices.md](references\u002Ftesting-best-practices.md)\n- [references\u002Ftest-fix-loop.md](references\u002Ftest-fix-loop.md)\n\n### Specialized guidance\n- [references\u002Fmocking-patterns.md](references\u002Fmocking-patterns.md)\n- [references\u002Fperformance-optimization.md](references\u002Fperformance-optimization.md)\n- [assets\u002F](assets\u002F)\n\n---\n\n## Score Guide\n\n| Score | Meaning |\n|---|---|\n| 108+ | strong production-grade test confidence |\n| 96–107 | good test suite with minor gaps |\n| 84–95 | acceptable but strengthen coverage \u002F assertions |\n| \u003C 84 | below standard; revise before relying on it |\n","# sf-testing: Salesforce Test Execution & Coverage Analysis\n\nUse this skill when the user needs **Apex test execution and failure analysis**: running tests, checking coverage, interpreting failures, improving coverage, and managing a disciplined test-fix loop for Salesforce code.\n\n## When This Skill Owns the Task\n\nUse `sf-testing` when the work involves:\n- `sf apex run test` workflows\n- Apex unit-test failures\n- code coverage analysis\n- identifying uncovered lines and missing test scenarios\n- structured test-fix loops for Apex code\n\nDelegate elsewhere when the user is:\n- writing or refactoring production Apex → [sf-apex](..\u002Fsf-apex\u002FSKILL.md)\n- testing Agentforce agents → [sf-ai-agentforce-testing](..\u002Fsf-ai-agentforce-testing\u002FSKILL.md)\n- testing LWC with Jest → [sf-lwc](..\u002Fsf-lwc\u002FSKILL.md)\n\n---\n\n## Required Context to Gather First\n\nAsk for or infer:\n- target org alias\n- desired test scope: single class, specific methods, suite, or local tests\n- coverage threshold expectation\n- whether the user wants diagnosis only or a test-fix loop\n- whether related test data factories already exist\n\n---\n\n## Recommended Workflow\n\n### 1. Discover test scope\nIdentify:\n- existing test classes\n- target production classes\n- test data factories \u002F setup helpers\n\n### 2. Run the smallest useful test set first\nStart narrow when debugging a failure; widen only after the fix is stable.\n\n### 3. Analyze results\nFocus on:\n- failing methods\n- exception types and stack traces\n- uncovered lines \u002F weak coverage areas\n- whether failures indicate bad test data, brittle assertions, or broken production logic\n\n### 4. Run a disciplined fix loop\nWhen the issue is code or test quality:\n- delegate code fixes to [sf-apex](..\u002Fsf-apex\u002FSKILL.md) when needed\n- add or improve tests\n- rerun focused tests before broader regression\n\n### 5. Improve coverage intentionally\nCover:\n- positive path\n- negative \u002F exception path\n- bulk path (251+ records where appropriate)\n- callout or async path when relevant\n\n---\n\n## High-Signal Rules\n\n- default to `SeeAllData=false`\n- every test should assert meaningful outcomes\n- test bulk behavior, not just single-record happy paths\n- use factories \u002F `@TestSetup` when they improve clarity and speed\n- pair `Test.startTest()` with `Test.stopTest()` when async behavior matters\n- do not hide flaky org dependencies inside tests\n\n---\n\n## Output Format\n\nWhen finishing, report in this order:\n1. **What tests were run**\n2. **Pass\u002Ffail summary**\n3. **Coverage result**\n4. **Root-cause findings**\n5. **Fix or next-run recommendation**\n\nSuggested shape:\n\n```text\nTest run: \u003Cscope>\nOrg: \u003Calias>\nResult: \u003Cpassed \u002F partial \u002F failed>\nCoverage: \u003Cpercent \u002F key classes>\nIssues: \u003Chighest-signal failures>\nNext step: \u003Cfix class, add test, rerun scope, or widen regression>\n```\n\n---\n\n## Cross-Skill Integration\n\n| Need | Delegate to | Reason |\n|---|---|---|\n| fix production code or author tests | [sf-apex](..\u002Fsf-apex\u002FSKILL.md) | code generation and repair |\n| create bulk \u002F edge-case data | [sf-data](..\u002Fsf-data\u002FSKILL.md) | realistic test datasets |\n| deploy updated tests | [sf-deploy](..\u002Fsf-deploy\u002FSKILL.md) | rollout |\n| inspect detailed runtime logs | [sf-debug](..\u002Fsf-debug\u002FSKILL.md) | deeper failure analysis |\n\n---\n\n## Reference Map\n\n### Start here\n- [references\u002Fcli-commands.md](references\u002Fcli-commands.md)\n- [references\u002Ftest-patterns.md](references\u002Ftest-patterns.md)\n- [references\u002Ftesting-best-practices.md](references\u002Ftesting-best-practices.md)\n- [references\u002Ftest-fix-loop.md](references\u002Ftest-fix-loop.md)\n\n### Specialized guidance\n- [references\u002Fmocking-patterns.md](references\u002Fmocking-patterns.md)\n- [references\u002Fperformance-optimization.md](references\u002Fperformance-optimization.md)\n- [assets\u002F](assets\u002F)\n\n---\n\n## Score Guide\n\n| Score | Meaning |\n|---|---|\n| 108+ | strong production-grade test confidence |\n| 96–107 | good test suite with minor gaps |\n| 84–95 | acceptable but strengthen coverage \u002F assertions |\n| \u003C 84 | below standard; revise before relying on it |\n",{"name":5,"license":15,"metadata":24,"description":28},{"author":25,"scoring":26,"version":27},"Jag Valaiyapathy","120 points across 6 categories","1.1.0","Apex test execution, coverage analysis, and test-fix loops with 120-point scoring. TRIGGER when: user runs Apex tests, checks code coverage, fixes failing tests, or touches *Test.cls \u002F *_Test.cls files. DO NOT TRIGGER when: writing Apex production code (use sf-apex), Agentforce agent testing (use sf-ai-agentforce-testing), or Jest\u002FLWC tests (use sf-lwc).\n","main","8859218955d9504cd18b59e7892100718039d3b4","data\u002Fskills\u002Fjaganpro-sf-skills\u002Fsf-testing",1,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper","https:\u002F\u002Fgithub.com\u002Fom-scogo","SDE-1 @ Scogo ","2026-07-18 12:22:46",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add om-scogo\u002Fskillsh-scraper --skill sf-testing",{"tool":43,"command":44},"bunx","bunx skills add om-scogo\u002Fskillsh-scraper --skill sf-testing",{"tool":46,"command":47},"pnpm","pnpm dlx skills add om-scogo\u002Fskillsh-scraper --skill sf-testing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fjaganpro-sf-skills\u002Fsf-testing\u002FSkill.md",true,[51],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"metadata.json","REFERENCE","参考文档",415,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fjaganpro-sf-skills\u002Fsf-testing\u002Fmetadata.json",[58,65,70,77,82,89],{"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":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7D6MC9FAAEV4CMNYX8W7JTG","arxiv-search","Search arXiv physics, math, and computer science preprints using natural language queries. Powered by Valyu semantic search.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002Fskills\u002Farxiv-search\u002FSKILL.md",[],[],{"skillNo":66,"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":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7D6M85CKKN87TA98VCQV4H7","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002FSkill.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7D4ZTCS4DR3CE4JY06X84T2","working-with-legacy-code","Safely change and test untested codebases using Feathers' \"Working Effectively with Legacy Code\". Use when the user mentions \"legacy code\", \"no tests\", \"untested codebase\", \"how do I test this\", \"seams\", \"characterization tests\", \"golden master\", \"sprout method\", \"afraid to change this code\", \"monster method\", \"dependency breaking\", or \"inherited a messy codebase\". Also trigger when changing code without tests safely, getting a class under test when constructors, statics, or singletons block it, adding features to tangled modules, or planning incremental test coverage for an old codebase. Covers the legacy-code change algorithm, seams, characterization tests, sprout\u002Fwrap, and dependency-breaking techniques. For refactoring code that already has tests, see refactoring-patterns. For day-to-day code quality, see clean-code.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002Fworking-with-legacy-code\u002FSKILL.md",[],[],{"skillNo":78,"name":72,"nameZh":6,"description":73,"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},"01M7D4ZHZKJD2RSNGAF63V14P4","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\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},"01M7D4ZB4CJBFW5JE67CPH2QRV","web-typography","Select, pair, and implement typefaces for web projects. Use when the user mentions \"font pairing\", \"which typeface\", \"line height\", \"responsive typography\", \"web font loading\", \"type hierarchy\", \"variable fonts\", \"FOUT\u002FFOIT\", \"typographic scale\", or \"the text is hard to read\". Also trigger when choosing between system fonts and web fonts, optimizing font-loading performance, or designing readable long-form content. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002Fweb-typography\u002FSKILL.md",[],[],{"skillNo":90,"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":91,"categories":92,"keywords":93,"publishedAt":19},"01M7D4Z4MVYVY3NMJ18BNV6WNA","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002FSkill.md",[],[]]