[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M742XKBT29T8KAPESVVCW7W6":3,"skill-same:01M742XKBT29T8KAPESVVCW7W6":69},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":34,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M742XKBT29T8KAPESVVCW7W6","skill-check",null,"Comprehensive testing and validation of Claude skills. Use this skill whenever the user wants to test, validate, audit, or quality-check a skill — whether they say \"test my skill\", \"check this skill works\", \"validate my skill\", \"run skill-check\", or anything similar. Also trigger when the user asks things like \"does this skill handle edge cases?\", \"what's wrong with my skill?\", \"find problems in my skill\", \"is this skill secure?\", \"does my skill follow best practices?\", or \"how robust is this skill?\". Even if they just say \"check this\" and point at a skill directory, use skill-check. This skill covers triggering tests, output quality tests, input\u002Foutput contract validation, script execution checks, security review, best practices auditing, and multi-file skill analysis. Do NOT use for creating or editing skills (that's skill-creator) — skill-check is purely about testing and reporting on existing skills.","bg-szy\u002FTOP-SKILLS","bg-szy","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F106576190?v=4","01M73A4E8KPV67SFXRY8XZGNBX","ShuZhiyong","01M73A4E96MQ294MHM74TZBVQD",6,"MIT","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fskill-check\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fskill-check\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: skill-check\ndescription: >\n  Comprehensive testing and validation of Claude skills. Use this skill whenever the user wants to\n  test, validate, audit, or quality-check a skill — whether they say \"test my skill\", \"check this\n  skill works\", \"validate my skill\", \"run skill-check\", or anything similar. Also trigger when the\n  user asks things like \"does this skill handle edge cases?\", \"what's wrong with my skill?\",\n  \"find problems in my skill\", \"is this skill secure?\", \"does my skill follow best practices?\",\n  or \"how robust is this skill?\". Even if they just say \"check this\" and point at a skill\n  directory, use skill-check. This skill covers triggering tests, output quality tests, input\u002Foutput\n  contract validation, script execution checks, security review, best practices auditing, and\n  multi-file skill analysis.\n  Do NOT use for creating or editing skills (that's skill-creator) — skill-check is purely about\n  testing and reporting on existing skills.\nlicense: MIT\nallowed-tools: Bash Read Write\n---\n\n# SkillCheck — Comprehensive Skill Testing\n\nSkillCheck audits an entire skill directory, understands every moving part, and generates targeted\ntests to verify the skill works as advertised. It doesn't just check \"does it roughly work\" — it\ntests every aspect: triggering, input handling, output quality, script correctness, security,\nbest practices, and resource integrity.\n\n---\n\n## How it works\n\nThree phases: **Discover → Test → Report.** Discovery is always required. Testing depth\ndepends on what the user wants. Reporting adapts to what was found.\n\n| Depth         | What it covers                                                            |\n|---------------|---------------------------------------------------------------------------|\n| **Quick**     | Static analysis — structure, syntax, integrity, security, best practices  |\n| **Standard**  | Static + script execution + happy-path I\u002FO + eval regression              |\n| **Deep**      | Everything — edge cases, mock files, e2e workflows, stress                |\n\nIf the user doesn't specify, default to **Standard** — it catches real functional problems\nwithout the time investment of Deep. If they seem in a hurry, go **Quick**. If they mention\nthoroughness, edge cases, or \"test everything\", go **Deep**.\n\nFor a worked example of a Standard Check from start to finish, see `references\u002Fexample-run.md`.\n\n---\n\n## Gotchas\n\n- The `evals.json` format must match the skill-creator schema exactly (see\n  `references\u002Feval-schema.md`). Don't invent a new format — compatibility with\n  skill-creator's benchmarking tools is the whole point.\n- Mock file generation for binary formats (DOCX, XLSX, PPTX, PDF, images) requires\n  third-party Python packages that may not be installed. Always check availability\n  before generating and fall back to text-based equivalents if installation fails.\n  See `references\u002Fmock-files.md` for the dependency list.\n- Cross-reference mismatches between SKILL.md and scripts are often the root cause\n  of multiple downstream test failures (script execution fails, eval regression fails,\n  I\u002FO tests fail — all for the same reason). Identify and report the root cause\n  rather than listing each symptom as a separate unrelated failure.\n- Best practice scores are advisory and reported separately — do not add them to the\n  main pass\u002Ffail verdict percentage. A skill can be functionally perfect but\n  structurally messy, and the report should reflect that distinction.\n- Security review runs before script execution for a reason — if Critical security\n  issues are found in scripts, warn the user before executing them at Standard or\n  Deep depth. Don't silently run code you've just flagged as dangerous.\n- Incomplete skills (TODOs, stubs, placeholder text) need a progress report, not a\n  wall of failures. It's easy to mechanically run the standard flow and produce 15\n  failures that all say \"this doesn't exist yet\" — that's not useful. Read\n  `references\u002Fincomplete-skills.md` and reframe.\n- On Claude.ai without subagents, end-to-end tests run sequentially in shared context.\n  This means earlier test results can influence later tests — an agent that just\n  discovered a cross-reference bug might \"know\" to use the correct arguments on the\n  next test. Keep this in mind when interpreting e2e results.\n- The frontmatter `name` field must match the parent directory name per the Agent\n  Skills spec. This is easy to miss because many platforms will still load the skill\n  with a mismatch — but others won't, making it a silent portability bug.\n- Report sections should be collapsed when empty — a Quick Check on a minimal skill\n  should produce 5 sections, not a 12-section skeleton full of \"N\u002FA\".\n  See `references\u002Freport-format.md` for collapsing rules.\n\n---\n\n## Phase 1: Discover\n\nFind the skill, scan it, understand what it contains, and decide how to test it.\n\n### Find the skill\n\nIf the user gives a specific path, use it. If not, read `references\u002Ffinding-the-skill.md`\nto locate the skill from conversation context or common locations.\n\n### Scan the directory\n\nRead the entire skill directory, not just SKILL.md. Categorize every file:\n\n| Category       | What to look for                                                       |\n|----------------|------------------------------------------------------------------------|\n| **Core**       | `SKILL.md` — the main instructions file                                |\n| **Scripts**    | `scripts\u002F` — executable code (Python, Bash, JS, etc.)                  |\n| **References** | `references\u002F` — documentation loaded into context as needed            |\n| **Assets**     | `assets\u002F` — templates, icons, fonts, images used in output             |\n| **Examples**   | Any example input\u002Foutput files, sample data                            |\n| **Config**     | Package files, requirements, dependency lists                          |\n| **Evals**      | `evals\u002F` — existing test cases (if any)                                |\n\nRecord a manifest — you'll reference this throughout testing.\n\n### Parse the SKILL.md\n\nExtract from the frontmatter and body:\n\n- **Name and description** — what it does and when it should trigger\n- **Declared inputs** — file types, formats, schemas (pay close attention to explicitly\n  named extensions, column names, data structures)\n- **Declared outputs** — file types, formats, target paths, expected structures\n- **Step-by-step workflows** — numbered or ordered procedures\n- **Tool\u002Fdependency requirements** — libraries, CLIs, external tools\n- **Conditional logic** — branching paths\n- **Constraints and rules** — ALWAYS, NEVER, MUST directives\n- **References to bundled files** — when to read other files in the skill\n- **Script invocations** — exact commands including arguments and flags\n\n### Analyze supporting files\n\nFor each non-SKILL.md file:\n\n- **Scripts**: Read the code. Identify arguments, outputs, hardcoded paths, error handling,\n  and dependencies. Pay special attention to argument parsing — you'll compare this against\n  how SKILL.md invokes the script.\n- **References**: Skim for structure and purpose. Note if SKILL.md actually references them.\n- **Assets**: Note file types and whether they're referenced. Assets will be validated for\n  integrity during testing — see `references\u002Fquick-check.md`.\n- **Examples**: Identify as input examples, output examples, or both — gold for test generation.\n- **Evals**: Read `evals.json` if present. See `references\u002Feval-schema.md` for the format.\n\n### Present findings\n\nShow the user: the file manifest, what the skill claims to do, declared inputs\u002Foutputs,\nimmediate red flags, and whether evals were found.\n\n**If the skill appears incomplete** (TODOs, placeholder text, missing referenced files,\nstub scripts), read `references\u002Fincomplete-skills.md` and adjust your approach — reframe\nas a progress report rather than a failure report.\n\nThen ask which depth level they'd like (if they haven't already said).\n\n---\n\n## Phase 2: Test\n\nRead the reference file for the chosen depth level. It defines exactly which tests to run,\nin what order, and how to evaluate results:\n\n- **Quick:** `references\u002Fquick-check.md` — static integrity, asset validation, SKILL.md\n  quality, cross-reference consistency, multi-skill dependencies, security review, and\n  22 best practice checks (`references\u002Fbest-practices.md`)\n- **Standard:** `references\u002Fstandard-check.md` — everything in Quick, plus eval regression\n  (`references\u002Feval-schema.md`), script execution with mock inputs (`references\u002Fmock-files.md`),\n  happy-path I\u002FO contract validation, and workflow tests\n- **Deep:** `references\u002Fdeep-check.md` — everything in Standard, plus edge case inputs,\n  end-to-end workflow simulation, triggering analysis, error recovery, and script robustness\n\n### Test plan (Standard and Deep only)\n\nFor Standard and Deep checks, present the test plan to the user before executing — they may\nknow about domain-specific edge cases worth adding, or tests that aren't relevant. For Quick\nchecks on simple skills, skip straight to running the tests.\n\n### Execution order\n\n1. **Static tests first** — fast, free, and may reveal issues that make later tests\n   pointless or unsafe (security problems, broken cross-references)\n2. **Eval regression next** — the author's own tests are the most authoritative baseline\n3. **Script tests** — run with mock inputs, verify outputs\n4. **I\u002FO contract tests** — generate mock files, run the skill, check results\n5. **End-to-end tests last** — slowest and most context-heavy; earlier tests may have\n   already uncovered the issues they'd find\n\nFor each test, record: test ID, what was tested, pass\u002Ffail, evidence, and notes. Evidence\nis critical — it lets the user verify your judgment and makes the report actionable.\n\n**On Claude.ai (no subagents):** Run tests sequentially. Save outputs to a workspace\ndirectory so the user can inspect them after the report.\n\n**With subagents:** Static tests first, then dynamic tests in parallel. Use independent\nsubagents for end-to-end tests — shared context lets earlier tests influence later ones,\nmasking issues that would appear in a fresh invocation.\n\n---\n\n## Phase 3: Report\n\nRead `references\u002Freport-format.md` for the full template and collapsing rules. Key elements:\n\n- **Summary card** with pass\u002Ffail counts and verdict (HEALTHY \u002F MOSTLY HEALTHY \u002F\n  NEEDS ATTENTION \u002F CRITICAL)\n- **Failed test details** — what was tested, what happened, why it matters, suggested fix\n- **Security findings** — dedicated section if anything flagged, prominent banner for\n  Critical findings\n- **Best practices score** — separate from the main verdict\n- **Improvement suggestions** — prioritized: Critical → Important → Nice to have\n\nOnly include report sections that have content. See the collapsing rules in\n`references\u002Freport-format.md` for which sections to skip at each depth level.\n","# SkillCheck — Comprehensive Skill Testing\n\nSkillCheck audits an entire skill directory, understands every moving part, and generates targeted\ntests to verify the skill works as advertised. It doesn't just check \"does it roughly work\" — it\ntests every aspect: triggering, input handling, output quality, script correctness, security,\nbest practices, and resource integrity.\n\n---\n\n## How it works\n\nThree phases: **Discover → Test → Report.** Discovery is always required. Testing depth\ndepends on what the user wants. Reporting adapts to what was found.\n\n| Depth         | What it covers                                                            |\n|---------------|---------------------------------------------------------------------------|\n| **Quick**     | Static analysis — structure, syntax, integrity, security, best practices  |\n| **Standard**  | Static + script execution + happy-path I\u002FO + eval regression              |\n| **Deep**      | Everything — edge cases, mock files, e2e workflows, stress                |\n\nIf the user doesn't specify, default to **Standard** — it catches real functional problems\nwithout the time investment of Deep. If they seem in a hurry, go **Quick**. If they mention\nthoroughness, edge cases, or \"test everything\", go **Deep**.\n\nFor a worked example of a Standard Check from start to finish, see `references\u002Fexample-run.md`.\n\n---\n\n## Gotchas\n\n- The `evals.json` format must match the skill-creator schema exactly (see\n  `references\u002Feval-schema.md`). Don't invent a new format — compatibility with\n  skill-creator's benchmarking tools is the whole point.\n- Mock file generation for binary formats (DOCX, XLSX, PPTX, PDF, images) requires\n  third-party Python packages that may not be installed. Always check availability\n  before generating and fall back to text-based equivalents if installation fails.\n  See `references\u002Fmock-files.md` for the dependency list.\n- Cross-reference mismatches between SKILL.md and scripts are often the root cause\n  of multiple downstream test failures (script execution fails, eval regression fails,\n  I\u002FO tests fail — all for the same reason). Identify and report the root cause\n  rather than listing each symptom as a separate unrelated failure.\n- Best practice scores are advisory and reported separately — do not add them to the\n  main pass\u002Ffail verdict percentage. A skill can be functionally perfect but\n  structurally messy, and the report should reflect that distinction.\n- Security review runs before script execution for a reason — if Critical security\n  issues are found in scripts, warn the user before executing them at Standard or\n  Deep depth. Don't silently run code you've just flagged as dangerous.\n- Incomplete skills (TODOs, stubs, placeholder text) need a progress report, not a\n  wall of failures. It's easy to mechanically run the standard flow and produce 15\n  failures that all say \"this doesn't exist yet\" — that's not useful. Read\n  `references\u002Fincomplete-skills.md` and reframe.\n- On Claude.ai without subagents, end-to-end tests run sequentially in shared context.\n  This means earlier test results can influence later tests — an agent that just\n  discovered a cross-reference bug might \"know\" to use the correct arguments on the\n  next test. Keep this in mind when interpreting e2e results.\n- The frontmatter `name` field must match the parent directory name per the Agent\n  Skills spec. This is easy to miss because many platforms will still load the skill\n  with a mismatch — but others won't, making it a silent portability bug.\n- Report sections should be collapsed when empty — a Quick Check on a minimal skill\n  should produce 5 sections, not a 12-section skeleton full of \"N\u002FA\".\n  See `references\u002Freport-format.md` for collapsing rules.\n\n---\n\n## Phase 1: Discover\n\nFind the skill, scan it, understand what it contains, and decide how to test it.\n\n### Find the skill\n\nIf the user gives a specific path, use it. If not, read `references\u002Ffinding-the-skill.md`\nto locate the skill from conversation context or common locations.\n\n### Scan the directory\n\nRead the entire skill directory, not just SKILL.md. Categorize every file:\n\n| Category       | What to look for                                                       |\n|----------------|------------------------------------------------------------------------|\n| **Core**       | `SKILL.md` — the main instructions file                                |\n| **Scripts**    | `scripts\u002F` — executable code (Python, Bash, JS, etc.)                  |\n| **References** | `references\u002F` — documentation loaded into context as needed            |\n| **Assets**     | `assets\u002F` — templates, icons, fonts, images used in output             |\n| **Examples**   | Any example input\u002Foutput files, sample data                            |\n| **Config**     | Package files, requirements, dependency lists                          |\n| **Evals**      | `evals\u002F` — existing test cases (if any)                                |\n\nRecord a manifest — you'll reference this throughout testing.\n\n### Parse the SKILL.md\n\nExtract from the frontmatter and body:\n\n- **Name and description** — what it does and when it should trigger\n- **Declared inputs** — file types, formats, schemas (pay close attention to explicitly\n  named extensions, column names, data structures)\n- **Declared outputs** — file types, formats, target paths, expected structures\n- **Step-by-step workflows** — numbered or ordered procedures\n- **Tool\u002Fdependency requirements** — libraries, CLIs, external tools\n- **Conditional logic** — branching paths\n- **Constraints and rules** — ALWAYS, NEVER, MUST directives\n- **References to bundled files** — when to read other files in the skill\n- **Script invocations** — exact commands including arguments and flags\n\n### Analyze supporting files\n\nFor each non-SKILL.md file:\n\n- **Scripts**: Read the code. Identify arguments, outputs, hardcoded paths, error handling,\n  and dependencies. Pay special attention to argument parsing — you'll compare this against\n  how SKILL.md invokes the script.\n- **References**: Skim for structure and purpose. Note if SKILL.md actually references them.\n- **Assets**: Note file types and whether they're referenced. Assets will be validated for\n  integrity during testing — see `references\u002Fquick-check.md`.\n- **Examples**: Identify as input examples, output examples, or both — gold for test generation.\n- **Evals**: Read `evals.json` if present. See `references\u002Feval-schema.md` for the format.\n\n### Present findings\n\nShow the user: the file manifest, what the skill claims to do, declared inputs\u002Foutputs,\nimmediate red flags, and whether evals were found.\n\n**If the skill appears incomplete** (TODOs, placeholder text, missing referenced files,\nstub scripts), read `references\u002Fincomplete-skills.md` and adjust your approach — reframe\nas a progress report rather than a failure report.\n\nThen ask which depth level they'd like (if they haven't already said).\n\n---\n\n## Phase 2: Test\n\nRead the reference file for the chosen depth level. It defines exactly which tests to run,\nin what order, and how to evaluate results:\n\n- **Quick:** `references\u002Fquick-check.md` — static integrity, asset validation, SKILL.md\n  quality, cross-reference consistency, multi-skill dependencies, security review, and\n  22 best practice checks (`references\u002Fbest-practices.md`)\n- **Standard:** `references\u002Fstandard-check.md` — everything in Quick, plus eval regression\n  (`references\u002Feval-schema.md`), script execution with mock inputs (`references\u002Fmock-files.md`),\n  happy-path I\u002FO contract validation, and workflow tests\n- **Deep:** `references\u002Fdeep-check.md` — everything in Standard, plus edge case inputs,\n  end-to-end workflow simulation, triggering analysis, error recovery, and script robustness\n\n### Test plan (Standard and Deep only)\n\nFor Standard and Deep checks, present the test plan to the user before executing — they may\nknow about domain-specific edge cases worth adding, or tests that aren't relevant. For Quick\nchecks on simple skills, skip straight to running the tests.\n\n### Execution order\n\n1. **Static tests first** — fast, free, and may reveal issues that make later tests\n   pointless or unsafe (security problems, broken cross-references)\n2. **Eval regression next** — the author's own tests are the most authoritative baseline\n3. **Script tests** — run with mock inputs, verify outputs\n4. **I\u002FO contract tests** — generate mock files, run the skill, check results\n5. **End-to-end tests last** — slowest and most context-heavy; earlier tests may have\n   already uncovered the issues they'd find\n\nFor each test, record: test ID, what was tested, pass\u002Ffail, evidence, and notes. Evidence\nis critical — it lets the user verify your judgment and makes the report actionable.\n\n**On Claude.ai (no subagents):** Run tests sequentially. Save outputs to a workspace\ndirectory so the user can inspect them after the report.\n\n**With subagents:** Static tests first, then dynamic tests in parallel. Use independent\nsubagents for end-to-end tests — shared context lets earlier tests influence later ones,\nmasking issues that would appear in a fresh invocation.\n\n---\n\n## Phase 3: Report\n\nRead `references\u002Freport-format.md` for the full template and collapsing rules. Key elements:\n\n- **Summary card** with pass\u002Ffail counts and verdict (HEALTHY \u002F MOSTLY HEALTHY \u002F\n  NEEDS ATTENTION \u002F CRITICAL)\n- **Failed test details** — what was tested, what happened, why it matters, suggested fix\n- **Security findings** — dedicated section if anything flagged, prominent banner for\n  Critical findings\n- **Best practices score** — separate from the main verdict\n- **Improvement suggestions** — prioritized: Critical → Important → Nice to have\n\nOnly include report sections that have content. See the collapsing rules in\n`references\u002Freport-format.md` for which sections to skip at each depth level.\n",{"name":5,"license":15,"description":25,"allowed-tools":26},"Comprehensive testing and validation of Claude skills. Use this skill whenever the user wants to test, validate, audit, or quality-check a skill — whether they say \"test my skill\", \"check this skill works\", \"validate my skill\", \"run skill-check\", or anything similar. Also trigger when the user asks things like \"does this skill handle edge cases?\", \"what's wrong with my skill?\", \"find problems in my skill\", \"is this skill secure?\", \"does my skill follow best practices?\", or \"how robust is this skill?\". Even if they just say \"check this\" and point at a skill directory, use skill-check. This skill covers triggering tests, output quality tests, input\u002Foutput contract validation, script execution checks, security review, best practices auditing, and multi-file skill analysis. Do NOT use for creating or editing skills (that's skill-creator) — skill-check is purely about testing and reporting on existing skills.\n","Bash Read Write","master","63f17866001c5ca854bf2fa0b678ce277133de5b","skills\u002Fmarketplace\u002Fskill-check",0,"https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS","https:\u002F\u002Fbg-szy.github.io\u002FTOP-SKILLS\u002F","https:\u002F\u002Fgithub.com\u002Fbg-szy","https:\u002F\u002Fwww.ecust.edu.cn\u002F","a student of East China University of Science and Technology","2026-11-15 03:38:02",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add bg-szy\u002FTOP-SKILLS --skill skill-check",{"tool":43,"command":44},"bunx","bunx skills add bg-szy\u002FTOP-SKILLS --skill skill-check",{"tool":46,"command":47},"pnpm","pnpm dlx skills add bg-szy\u002FTOP-SKILLS --skill skill-check","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fskill-check\u002FSKILL.md",true,[51,57,61,65],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"CONTRIBUTING.md","REFERENCE","参考文档",3611,"https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fskill-check\u002FCONTRIBUTING.md",{"path":58,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":16},"LICENSE","许可证",1080,{"path":62,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":63,"sourceHtmlUrl":64},"README.md",6826,"https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fskill-check\u002FREADME.md",{"path":66,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":67,"sourceHtmlUrl":68},"skill-report.json",109831,"https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fskill-check\u002Fskill-report.json",[70,78,85,92,99,106],{"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":77},"01M7DXW9N826PKXK174PVW3038","serpmaven","Scrape Google search results (SERP) to JSON with SERP Maven (serpmaven) - a real Chrome browser on a residential proxy with sticky sessions. Run it as a CLI, a Python library, a local HTTP search API (`serve`), an MCP server or a Docker image; set the proxy login, workers, pages and cost tracking. Use when the user wants Google results, rank tracking, a self-hosted SERP API, or live Google search for an AI agent.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fserpmaven\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":77},"01M7DXVHSTWDV65475QEQ915M7","revnu-landing-page-audit","Find out why a landing page isn't turning visitors into signups, demos or sales. Audits one page against what the ad, post or search that sends people there promised, then checks the first screen, proof, call to action, friction and mobile. Returns at most 7 prioritized fixes, plus what is fine and what could not be checked; rewrites specific lines and fixes the page in the repo when asked. Never promises a conversion lift. Works without a Revnu account. Use when the user says or asks: \"audit my landing page\", \"why isn't this page converting\", \"review my homepage\", \"my ads get clicks but no signups\", \"people bounce from the pricing page\", \"CRO review\", \"improve conversion rate\", \"is my hero section clear\", \"roast my landing page\", \"rewrite my headline\", \"what's wrong with this page\", \"landing page feedback\", \"make the signup page convert better\". Not for SEO or AI-search audits, page speed engineering on its own, or building a new page from scratch.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Frevnu-landing-page-audit\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":77},"01M7DXV8X2D7B3VTD4HHYYHTGR","revnu-growth-context","Write down once who buys, what they're stuck on, what it costs, what proof you have and what you've already tried, so every growth task starts from facts instead of a questionnaire. Creates or updates .agents\u002Frevnu-growth.md from the repo, the live site and the user, and imports an existing product-marketing.md. Use when the user says \"set up our marketing context\", \"who is our ideal customer\", \"write our ICP\", \"describe the product for marketing\", \"positioning doc\", \"what's our brand voice\", \"remember this about our customers\", \"log what we tried\", \"what have we learned from marketing\", \"we changed pricing, update the context\", \"update our growth notes\", \"summarize the business for the agent\", \"import my product-marketing.md\", \"start a growth doc\", or before a first marketing, SEO, outreach or launch task when no context file exists. Works without a Revnu account.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Frevnu-growth-context\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":77},"01M7DXV0DGJ1G0A60PAHC6J3C5","revnu-get-listed","Get onto the third-party pages AI answers and search cite when buyers ask for the best tool in your category: \"best X\" roundups, directories, review sites, GitHub awesome lists, community threads and comparison pages. Finds which ones are cited, ranks them by fit and effort, and drafts each submission, PR or pitch by the target's own rules. Use when the user says \"get us listed\", \"which directories should we submit to\", \"how do we get into best-of lists\", \"why does ChatGPT recommend competitors and not us\", \"get mentioned in AI answers\", \"submit to awesome lists\", \"get on G2\", \"where are our competitors listed\", \"pitch listicle authors\", \"find backlink opportunities\", \"launch directories\", \"get into roundups\", \"Product Hunt alternatives\", \"where should we be listed\", \"get cited by Perplexity\". Never submits, pays or posts without a yes. Works without a Revnu account.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Frevnu-get-listed\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":77},"01M7DXTSPMGT9D6DSS0HP9BSTA","revnu-ai-readiness-audit","Audit whether your website gives ChatGPT, Perplexity, Claude, Gemini and Google's AI Overviews something worth quoting, and fix the pages that don't. Use when the user says or asks \"is my site ready for AI search\", \"audit my site for AI answers\", \"AEO audit\", \"GEO audit\", \"why doesn't ChatGPT quote our pricing\", \"make our pages citable by AI\", \"do I need llms.txt\", \"does schema help with ChatGPT\", \"check our structured data\", \"is our content visible without JavaScript\", \"AI SEO audit\", \"optimize our homepage for AI answers\", \"LLM SEO check\", \"why does AI get our product wrong\", \"fix our site for AI Overviews\". Checks fetchability and indexability, answers in the raw HTML, entity facts, schema (including JS-injected markup), headings, dates and llms.txt, then gives at most 10 prioritised fixes and edits the repo when asked. Works without a Revnu account.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Frevnu-ai-readiness-audit\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":77},"01M7DXSZHCVTRS620GC3S97JZV","proxy-troubleshooting","Diagnose residential proxy failures, with NodeMaven's gateway as the reference - 407 with correct credentials, 406, 410, 500, a connection that hangs, ERR_TUNNEL_CONNECTION_FAILED in a browser, Playwright or Puppeteer ignoring proxy credentials, a sticky session that changes IP, geo-targeting that is silently ignored, passwords with special characters, and unexpected traffic from headless Chrome. Use when a proxy connection fails, returns the wrong location, or costs more traffic than expected.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fproxy-troubleshooting\u002FSKILL.md",[],[]]