[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M755MATD7FSDNX3RR403GTWH":3,"skill-same:01M755MATD7FSDNX3RR403GTWH":43},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"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":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":28,"install":29,"resources":42},"01M755MATD7FSDNX3RR403GTWH","report",null,"Generate test report. Use when user says \"test report\", \"results summary\", \"test status\", \"show results\", \"test dashboard\", or \"how did tests go\".","msm47\u002FGitskil","msm47","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F288053465?v=4","01M754J0R2V3Q31DD8BV9CCDEN","01M754J0S8Q6Y7P0S3AYCY0YQ5",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fengineering-team\u002Fplaywright-pro\u002Fskills\u002Freport\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: \"report\"\ndescription: >-\n  Generate test report. Use when user says \"test report\", \"results summary\",\n  \"test status\", \"show results\", \"test dashboard\", or \"how did tests go\".\n---\n\n# Smart Test Reporting\n\nGenerate test reports that plug into the user's existing workflow. Zero new tools.\n\n## Steps\n\n### 1. Run Tests (If Not Already Run)\n\nCheck if recent test results exist:\n\n```bash\nls -la test-results\u002F playwright-report\u002F 2>\u002Fdev\u002Fnull\n```\n\nIf no recent results, run tests:\n\n```bash\nnpx playwright test --reporter=json,html,list 2>&1 | tee test-output.log\n```\n\n### 2. Parse Results\n\nRead the JSON report:\n\n```bash\nnpx playwright test --reporter=json 2> \u002Fdev\u002Fnull\n```\n\nExtract:\n- Total tests, passed, failed, skipped, flaky\n- Duration per test and total\n- Failed test names with error messages\n- Flaky tests (passed on retry)\n\n### 3. Detect Report Destination\n\nCheck what's configured and route automatically:\n\n| Check | If found | Action |\n|---|---|---|\n| `TESTRAIL_URL` env var | TestRail configured | Push results via `\u002Fpw:testrail push` |\n| `SLACK_WEBHOOK_URL` env var | Slack configured | Post summary to Slack |\n| `.github\u002Fworkflows\u002F` | GitHub Actions | Results go to PR comment via artifacts |\n| `playwright-report\u002F` | HTML reporter | Open or serve the report |\n| None of the above | Default | Generate markdown report |\n\n### 4. Generate Report\n\n#### Markdown Report (Always Generated)\n\n```markdown\n# Test Results — {{date}}\n\n## Summary\n- ✅ Passed: {{passed}}\n- ❌ Failed: {{failed}}\n- ⏭️ Skipped: {{skipped}}\n- 🔄 Flaky: {{flaky}}\n- ⏱️ Duration: {{duration}}\n\n## Failed Tests\n| Test | Error | File |\n|---|---|---|\n| {{name}} | {{error}} | {{file}}:{{line}} |\n\n## Flaky Tests\n| Test | Retries | File |\n|---|---|---|\n| {{name}} | {{retries}} | {{file}} |\n\n## By Project\n| Browser | Passed | Failed | Duration |\n|---|---|---|---|\n| Chromium | X | Y | Zs |\n| Firefox | X | Y | Zs |\n| WebKit | X | Y | Zs |\n```\n\nSave to `test-reports\u002F{{date}}-report.md`.\n\n#### Slack Summary (If Webhook Configured)\n\n```bash\ncurl -X POST \"$SLACK_WEBHOOK_URL\" \\\n  -H 'Content-Type: application\u002Fjson' \\\n  -d '{\n    \"text\": \"🧪 Test Results: ✅ {{passed}} | ❌ {{failed}} | ⏱️ {{duration}}\\n{{failed_details}}\"\n  }'\n```\n\n#### TestRail Push (If Configured)\n\nInvoke `\u002Fpw:testrail push` with the JSON results.\n\n#### HTML Report\n\n```bash\nnpx playwright show-report\n```\n\nOr if in CI:\n```bash\necho \"HTML report available at: playwright-report\u002Findex.html\"\n```\n\n### 5. Trend Analysis (If Historical Data Exists)\n\nIf previous reports exist in `test-reports\u002F`:\n- Compare pass rate over time\n- Identify tests that became flaky recently\n- Highlight new failures vs. recurring failures\n\n## Output\n\n- Summary with pass\u002Ffail\u002Fskip\u002Fflaky counts\n- Failed test details with error messages\n- Report destination confirmation\n- Trend comparison (if historical data available)\n- Next action recommendation (fix failures or celebrate green)\n","# Smart Test Reporting\n\nGenerate test reports that plug into the user's existing workflow. Zero new tools.\n\n## Steps\n\n### 1. Run Tests (If Not Already Run)\n\nCheck if recent test results exist:\n\n```bash\nls -la test-results\u002F playwright-report\u002F 2>\u002Fdev\u002Fnull\n```\n\nIf no recent results, run tests:\n\n```bash\nnpx playwright test --reporter=json,html,list 2>&1 | tee test-output.log\n```\n\n### 2. Parse Results\n\nRead the JSON report:\n\n```bash\nnpx playwright test --reporter=json 2> \u002Fdev\u002Fnull\n```\n\nExtract:\n- Total tests, passed, failed, skipped, flaky\n- Duration per test and total\n- Failed test names with error messages\n- Flaky tests (passed on retry)\n\n### 3. Detect Report Destination\n\nCheck what's configured and route automatically:\n\n| Check | If found | Action |\n|---|---|---|\n| `TESTRAIL_URL` env var | TestRail configured | Push results via `\u002Fpw:testrail push` |\n| `SLACK_WEBHOOK_URL` env var | Slack configured | Post summary to Slack |\n| `.github\u002Fworkflows\u002F` | GitHub Actions | Results go to PR comment via artifacts |\n| `playwright-report\u002F` | HTML reporter | Open or serve the report |\n| None of the above | Default | Generate markdown report |\n\n### 4. Generate Report\n\n#### Markdown Report (Always Generated)\n\n```markdown\n# Test Results — {{date}}\n\n## Summary\n- ✅ Passed: {{passed}}\n- ❌ Failed: {{failed}}\n- ⏭️ Skipped: {{skipped}}\n- 🔄 Flaky: {{flaky}}\n- ⏱️ Duration: {{duration}}\n\n## Failed Tests\n| Test | Error | File |\n|---|---|---|\n| {{name}} | {{error}} | {{file}}:{{line}} |\n\n## Flaky Tests\n| Test | Retries | File |\n|---|---|---|\n| {{name}} | {{retries}} | {{file}} |\n\n## By Project\n| Browser | Passed | Failed | Duration |\n|---|---|---|---|\n| Chromium | X | Y | Zs |\n| Firefox | X | Y | Zs |\n| WebKit | X | Y | Zs |\n```\n\nSave to `test-reports\u002F{{date}}-report.md`.\n\n#### Slack Summary (If Webhook Configured)\n\n```bash\ncurl -X POST \"$SLACK_WEBHOOK_URL\" \\\n  -H 'Content-Type: application\u002Fjson' \\\n  -d '{\n    \"text\": \"🧪 Test Results: ✅ {{passed}} | ❌ {{failed}} | ⏱️ {{duration}}\\n{{failed_details}}\"\n  }'\n```\n\n#### TestRail Push (If Configured)\n\nInvoke `\u002Fpw:testrail push` with the JSON results.\n\n#### HTML Report\n\n```bash\nnpx playwright show-report\n```\n\nOr if in CI:\n```bash\necho \"HTML report available at: playwright-report\u002Findex.html\"\n```\n\n### 5. Trend Analysis (If Historical Data Exists)\n\nIf previous reports exist in `test-reports\u002F`:\n- Compare pass rate over time\n- Identify tests that became flaky recently\n- Highlight new failures vs. recurring failures\n\n## Output\n\n- Summary with pass\u002Ffail\u002Fskip\u002Fflaky counts\n- Failed test details with error messages\n- Report destination confirmation\n- Trend comparison (if historical data available)\n- Next action recommendation (fix failures or celebrate green)\n",{"name":5,"description":7},"main","56d41613d1ca1e2b0614a19c3816ec97a6159ec2","engineering-team\u002Fplaywright-pro\u002Fskills\u002Freport","https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil","https:\u002F\u002Fgithub.com\u002Fmsm47","2026-06-22 18:36:50",{"source":8,"skillName":5,"commands":30,"prompt":40,"zipAvailable":41},[31,34,37],{"tool":32,"command":33},"npx","npx skills add msm47\u002FGitskil --skill report",{"tool":35,"command":36},"bunx","bunx skills add msm47\u002FGitskil --skill report",{"tool":38,"command":39},"pnpm","pnpm dlx skills add msm47\u002FGitskil --skill report","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fengineering-team\u002Fplaywright-pro\u002Fskills\u002Freport\u002FSKILL.md",true,[],[44,51,58,65,72,79],{"skillNo":45,"name":46,"nameZh":6,"description":47,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":48,"categories":49,"keywords":50,"publishedAt":18},"01M76S8VB9Q65XVZXC99QVF20M","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Triggers whenever a user uploads a syllabus, course outline, or curriculum document and wants supplementary readings. Also triggers on: 'syllabus reading list', 'find papers for my course', 'create a reading list from this syllabus', 'recent research for my class', 'supplementary readings', 'find journal articles for these topics', 'what recent papers cover this material', 'any new research on these course topics', 'update my syllabus with recent papers'. Even casual mentions when a syllabus is attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":18},"01M76S8K8X17M3CV7RENS6KA32","research","Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends\u002Fsentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Triggers — \"research [topic]\", \"look into [topic]\", \"what do we know about [topic]\", \"investigate [topic]\", \"find me information on [topic]\", \"do some research on [topic]\", \"I need to understand [topic]\", or any research request that doesn't obviously match a more-specific specialist skill. Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.","https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fresearch\u002Fresearch\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":18},"01M76S8AZCNS7Q5M4G1SBQ8HDV","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Triggers: 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]', or any variation requesting multi-source recency intelligence on a topic. Also use for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":18},"01M76S7YVS0NHD51AFTZM5965R","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Triggers: 'prior art search for [invention]', 'patent search on [topic]', 'freedom to operate analysis', 'FTO for [product]', 'patent landscape for [field]', 'is [invention] novel', 'patents on [topic]', 'competitive patent analysis', 'prior art for litigation', 'patent diligence on [company]'. Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"01M76S7MQDZR49Y3DRXF394R2F","notebooklm","Browser automation skill for controlling Google's NotebookLM. Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio Overview, infographics, slide decks, study guides, briefing docs, mind maps, timelines, FAQs), and creating new notebooks. Triggers on any phrase involving NotebookLM — 'open NotebookLM', 'check my [name] notebook', 'pull info from NotebookLM', 'ask my notebook about X', 'add [source] to NotebookLM', 'create an infographic in NotebookLM', 'use NotebookLM Studio', 'generate a slide deck from my notebook', or any variation where the goal involves NotebookLM. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":18},"01M76S78K1ZJ092YYRKX0KBTYJ","litreview","Academic literature orientation skill that searches papers via Consensus, builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a professionally formatted Word document (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — not a finished review, but an orientation guide that lets a researcher dive in confidently. Triggers: 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'. Do NOT trigger for single one-off paper searches where the user just wants a quick list — that's a plain Consensus search.","https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[]]