[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76RPKDYR18H53XFV0S3KD7X":3,"skill-same:01M76RPKDYR18H53XFV0S3KD7X":107},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":13,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M76RPKDYR18H53XFV0S3KD7X","workflow-builder",null,"Design and write deterministic multi-agent workflow scripts (.js files in .claude\u002Fworkflows\u002F) for Claude Code's Workflow tool. Use when a user wants to build, create, author, scaffold, or run a custom Claude Code workflow, orchestrate sub-agents (fan-out, pipeline, loop, judge-panel), or automate a repeatable multi-step task across fresh-context agents.","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\u002Fworkflow-builder\u002Fskills\u002Fworkflow-builder\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: workflow-builder\ndescription: Design and write deterministic multi-agent workflow scripts (.js files in .claude\u002Fworkflows\u002F) for Claude Code's Workflow tool. Use when a user wants to build, create, author, scaffold, or run a custom Claude Code workflow, orchestrate sub-agents (fan-out, pipeline, loop, judge-panel), or automate a repeatable multi-step task across fresh-context agents.\nlicense: MIT\nmetadata:\n  inspired_by: \"https:\u002F\u002Fgithub.com\u002Fray-amjad\u002Fclaude-code-workflow-creator (Ray Amjad)\"\n  targets: \"Claude Code Workflow tool (CLAUDE_CODE_WORKFLOWS=1, \u002Fworkflows)\"\n  version: 1.0.0\n---\n\n# Workflow Builder\n\nAuthor runnable workflow scripts for Claude Code's Workflow tool: deterministic multi-agent orchestration files (`.js`) that fan work out to fresh-context sub-agents under plain JavaScript control flow. Only leaf `agent()` calls spend tokens, so the main session stays clean and the whole run is resumable.\n\n## ALWAYS start every session with intake (non-negotiable)\n\nBefore proposing or writing any workflow, run the intake. Do not skip to code.\n\n1. **Ask what kind of workflow they want.** Use this opening question set:\n   - What repeatable, multi-step task do you want to automate?\n   - What is the one unit of work a single sub-agent does once?\n   - How many units — a known list, or discovered by looping?\n   - Do later steps need *all* prior results at once, or can each item flow on its own?\n   - Does any step need structured data back (a verdict, a list, scores)?\n   - Roughly how many tokens \u002F how deep should it go?\n\n2. **If the user is vague, do NOT stall.** Run the recommendation engine to turn whatever you have into 1-2 concrete proposals, then present them *with the reasoning*:\n   ```bash\n   python scripts\u002Fworkflow_intake.py --task \"their description\" \\\n     --units unknown --stages unknown --needs-all unknown --structured unknown\n   ```\n   The engine returns a recommended topology (fan-out \u002F pipeline \u002F loop \u002F barrier \u002F judge-panel), model picks, a budget guard, and a one-line rationale per choice. Present those as \"Here's what I'd build and why\" — never ask the user to re-answer questions they already half-answered.\n\n3. **Confirm the shape with the user** (topology + phases + parallel-vs-pipeline) before writing the file. This is the only approval gate.\n\nSee [references\u002Fdecision_and_intake_guide.md](references\u002Fdecision_and_intake_guide.md) for the full question framework, the vague-input playbook, and worked recommendation examples.\n\n## Decide if a workflow is even the right tool\n\n| Scenario | Use |\n|----------|-----|\n| Single sub-agent, one task | plain Agent tool |\n| Reusable procedure, Claude picks steps dynamically | a Skill |\n| Many sub-agents in a fixed topology, deterministic + resumable | **Workflow** ✓ |\n\nWorkflows earn their cost when work is parallel or multi-stage, must be reproducible, long enough to fail halfway (so resume matters), or benefits from isolating each step in its own context window. For one-off tasks, just use Claude directly.\n\n## Build → validate → run loop\n\n1. **Scaffold** a starter from the confirmed topology:\n   ```bash\n   python scripts\u002Fscaffold_workflow.py --topology pipeline --name pr-triage \\\n     --description \"Triage open PRs\" > .claude\u002Fworkflows\u002Fpr-triage.js\n   ```\n2. **Edit** the file: `meta` block first (pure literal, first statement), then the async body using the injected globals — `agent()`, `pipeline()`, `parallel()`, `phase()`, `log()`, `budget`, `args`, `workflow()`. Full surface in [references\u002Fapi_reference.md](references\u002Fapi_reference.md); copy-paste shapes in [references\u002Forchestration_patterns.md](references\u002Forchestration_patterns.md).\n3. **Validate** before running — catches the parser-fatal mistakes:\n   ```bash\n   python scripts\u002Fvalidate_workflow.py .claude\u002Fworkflows\u002Fpr-triage.js\n   ```\n4. **Run** it: enable the feature with `export CLAUDE_CODE_WORKFLOWS=1`, save the file under `.claude\u002Fworkflows\u002F`, then use `\u002Fworkflows` to launch and watch it live. Press **P** to pause\u002Fresume, **X** to skip a sub-agent. Failed agents retry automatically.\n\n## Hard rules (validator enforces these)\n\n- `meta` is a **pure literal** and the **first statement** — no variables, spreads, template strings, or function calls inside it.\n- **No non-determinism:** `Date.now()`, `Math.random()`, argless `new Date()` break resume — pass timestamps via `args`.\n- **No filesystem \u002F Node APIs** (`require`, `fs`, `process`, network) in the orchestrator — that work belongs *inside* `agent()` prompts.\n- `parallel()` takes **thunks** (`() => agent(...)`), not bare promises. Default to `pipeline()` unless a stage needs the whole prior result set.\n- **Guard every open-ended loop** with a counter or `budget.remaining()` check — unguarded loops hit the 1000-agent cap.\n- Filter skipped\u002Ffailed agents: `results.filter(Boolean)`.\n\n## Tooling\n\n- `scripts\u002Fworkflow_intake.py` — intake recommendation engine (topology + model + budget + rationale from vague input).\n- `scripts\u002Fvalidate_workflow.py` — stdlib linter for the rules above; PASS \u002F WARN \u002F FAIL with line numbers.\n- `scripts\u002Fscaffold_workflow.py` — generate a starter `.js` for any topology.\n- `assets\u002Ftemplates\u002F` — fan-out, pipeline, loop-until-budget starters. `assets\u002Fexamples\u002F` — a complete runnable workflow.\n\nAll scripts run with `--sample` (no args) and `--help`.\n","# Workflow Builder\n\nAuthor runnable workflow scripts for Claude Code's Workflow tool: deterministic multi-agent orchestration files (`.js`) that fan work out to fresh-context sub-agents under plain JavaScript control flow. Only leaf `agent()` calls spend tokens, so the main session stays clean and the whole run is resumable.\n\n## ALWAYS start every session with intake (non-negotiable)\n\nBefore proposing or writing any workflow, run the intake. Do not skip to code.\n\n1. **Ask what kind of workflow they want.** Use this opening question set:\n   - What repeatable, multi-step task do you want to automate?\n   - What is the one unit of work a single sub-agent does once?\n   - How many units — a known list, or discovered by looping?\n   - Do later steps need *all* prior results at once, or can each item flow on its own?\n   - Does any step need structured data back (a verdict, a list, scores)?\n   - Roughly how many tokens \u002F how deep should it go?\n\n2. **If the user is vague, do NOT stall.** Run the recommendation engine to turn whatever you have into 1-2 concrete proposals, then present them *with the reasoning*:\n   ```bash\n   python scripts\u002Fworkflow_intake.py --task \"their description\" \\\n     --units unknown --stages unknown --needs-all unknown --structured unknown\n   ```\n   The engine returns a recommended topology (fan-out \u002F pipeline \u002F loop \u002F barrier \u002F judge-panel), model picks, a budget guard, and a one-line rationale per choice. Present those as \"Here's what I'd build and why\" — never ask the user to re-answer questions they already half-answered.\n\n3. **Confirm the shape with the user** (topology + phases + parallel-vs-pipeline) before writing the file. This is the only approval gate.\n\nSee [references\u002Fdecision_and_intake_guide.md](references\u002Fdecision_and_intake_guide.md) for the full question framework, the vague-input playbook, and worked recommendation examples.\n\n## Decide if a workflow is even the right tool\n\n| Scenario | Use |\n|----------|-----|\n| Single sub-agent, one task | plain Agent tool |\n| Reusable procedure, Claude picks steps dynamically | a Skill |\n| Many sub-agents in a fixed topology, deterministic + resumable | **Workflow** ✓ |\n\nWorkflows earn their cost when work is parallel or multi-stage, must be reproducible, long enough to fail halfway (so resume matters), or benefits from isolating each step in its own context window. For one-off tasks, just use Claude directly.\n\n## Build → validate → run loop\n\n1. **Scaffold** a starter from the confirmed topology:\n   ```bash\n   python scripts\u002Fscaffold_workflow.py --topology pipeline --name pr-triage \\\n     --description \"Triage open PRs\" > .claude\u002Fworkflows\u002Fpr-triage.js\n   ```\n2. **Edit** the file: `meta` block first (pure literal, first statement), then the async body using the injected globals — `agent()`, `pipeline()`, `parallel()`, `phase()`, `log()`, `budget`, `args`, `workflow()`. Full surface in [references\u002Fapi_reference.md](references\u002Fapi_reference.md); copy-paste shapes in [references\u002Forchestration_patterns.md](references\u002Forchestration_patterns.md).\n3. **Validate** before running — catches the parser-fatal mistakes:\n   ```bash\n   python scripts\u002Fvalidate_workflow.py .claude\u002Fworkflows\u002Fpr-triage.js\n   ```\n4. **Run** it: enable the feature with `export CLAUDE_CODE_WORKFLOWS=1`, save the file under `.claude\u002Fworkflows\u002F`, then use `\u002Fworkflows` to launch and watch it live. Press **P** to pause\u002Fresume, **X** to skip a sub-agent. Failed agents retry automatically.\n\n## Hard rules (validator enforces these)\n\n- `meta` is a **pure literal** and the **first statement** — no variables, spreads, template strings, or function calls inside it.\n- **No non-determinism:** `Date.now()`, `Math.random()`, argless `new Date()` break resume — pass timestamps via `args`.\n- **No filesystem \u002F Node APIs** (`require`, `fs`, `process`, network) in the orchestrator — that work belongs *inside* `agent()` prompts.\n- `parallel()` takes **thunks** (`() => agent(...)`), not bare promises. Default to `pipeline()` unless a stage needs the whole prior result set.\n- **Guard every open-ended loop** with a counter or `budget.remaining()` check — unguarded loops hit the 1000-agent cap.\n- Filter skipped\u002Ffailed agents: `results.filter(Boolean)`.\n\n## Tooling\n\n- `scripts\u002Fworkflow_intake.py` — intake recommendation engine (topology + model + budget + rationale from vague input).\n- `scripts\u002Fvalidate_workflow.py` — stdlib linter for the rules above; PASS \u002F WARN \u002F FAIL with line numbers.\n- `scripts\u002Fscaffold_workflow.py` — generate a starter `.js` for any topology.\n- `assets\u002Ftemplates\u002F` — fan-out, pipeline, loop-until-budget starters. `assets\u002Fexamples\u002F` — a complete runnable workflow.\n\nAll scripts run with `--sample` (no args) and `--help`.\n",{"name":5,"license":14,"metadata":23,"description":7},{"targets":24,"version":25,"inspired_by":26},"Claude Code Workflow tool (CLAUDE_CODE_WORKFLOWS=1, \u002Fworkflows)","1.0.0","https:\u002F\u002Fgithub.com\u002Fray-amjad\u002Fclaude-code-workflow-creator (Ray Amjad)","main","56d41613d1ca1e2b0614a19c3816ec97a6159ec2","engineering\u002Fworkflow-builder\u002Fskills\u002Fworkflow-builder","https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil","https:\u002F\u002Fgithub.com\u002Fmsm47","2026-06-22 18:36:50",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add msm47\u002FGitskil --skill workflow-builder",{"tool":39,"command":40},"bunx","bunx skills add msm47\u002FGitskil --skill workflow-builder",{"tool":42,"command":43},"pnpm","pnpm dlx skills add msm47\u002FGitskil --skill workflow-builder","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fengineering\u002Fworkflow-builder\u002Fskills\u002Fworkflow-builder\u002FSKILL.md",true,[47,53,57,61,65,71,75,79,83,87,91,95,99,103],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"assets\u002Fexamples\u002Fpr-triage.js","SCRIPT","脚本",3610,"https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fengineering\u002Fworkflow-builder\u002Fskills\u002Fworkflow-builder\u002Fassets\u002Fexamples\u002Fpr-triage.js",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"assets\u002Ftemplates\u002Ffan-out.js",1127,"https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fengineering\u002Fworkflow-builder\u002Fskills\u002Fworkflow-builder\u002Fassets\u002Ftemplates\u002Ffan-out.js",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"assets\u002Ftemplates\u002Floop-until-budget.js",1203,"https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fengineering\u002Fworkflow-builder\u002Fskills\u002Fworkflow-builder\u002Fassets\u002Ftemplates\u002Floop-until-budget.js",{"path":62,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":63,"sourceHtmlUrl":64},"assets\u002Ftemplates\u002Fpipeline.js",1250,"https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fengineering\u002Fworkflow-builder\u002Fskills\u002Fworkflow-builder\u002Fassets\u002Ftemplates\u002Fpipeline.js",{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"expected_outputs\u002Fintake_pr_review.json","REFERENCE","参考文档",1206,"https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fengineering\u002Fworkflow-builder\u002Fskills\u002Fworkflow-builder\u002Fexpected_outputs\u002Fintake_pr_review.json",{"path":72,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":73,"sourceHtmlUrl":74},"expected_outputs\u002Fscaffold_pipeline.js",1233,"https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fengineering\u002Fworkflow-builder\u002Fskills\u002Fworkflow-builder\u002Fexpected_outputs\u002Fscaffold_pipeline.js",{"path":76,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":77,"sourceHtmlUrl":78},"expected_outputs\u002Fvalidate_sample.txt",555,"https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fengineering\u002Fworkflow-builder\u002Fskills\u002Fworkflow-builder\u002Fexpected_outputs\u002Fvalidate_sample.txt",{"path":80,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":81,"sourceHtmlUrl":82},"README.md",1468,"https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fengineering\u002Fworkflow-builder\u002Fskills\u002Fworkflow-builder\u002FREADME.md",{"path":84,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fapi_reference.md",6413,"https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fengineering\u002Fworkflow-builder\u002Fskills\u002Fworkflow-builder\u002Freferences\u002Fapi_reference.md",{"path":88,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Fdecision_and_intake_guide.md",5948,"https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fengineering\u002Fworkflow-builder\u002Fskills\u002Fworkflow-builder\u002Freferences\u002Fdecision_and_intake_guide.md",{"path":92,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Forchestration_patterns.md",5522,"https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fengineering\u002Fworkflow-builder\u002Fskills\u002Fworkflow-builder\u002Freferences\u002Forchestration_patterns.md",{"path":96,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":97,"sourceHtmlUrl":98},"scripts\u002Fscaffold_workflow.py",6816,"https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fengineering\u002Fworkflow-builder\u002Fskills\u002Fworkflow-builder\u002Fscripts\u002Fscaffold_workflow.py",{"path":100,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":101,"sourceHtmlUrl":102},"scripts\u002Fvalidate_workflow.py",10940,"https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fengineering\u002Fworkflow-builder\u002Fskills\u002Fworkflow-builder\u002Fscripts\u002Fvalidate_workflow.py",{"path":104,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":105,"sourceHtmlUrl":106},"scripts\u002Fworkflow_intake.py",10485,"https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fengineering\u002Fworkflow-builder\u002Fskills\u002Fworkflow-builder\u002Fscripts\u002Fworkflow_intake.py",[108,115,122,129,136,143],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"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":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"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":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"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":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":135,"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":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":142,"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":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":149,"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",[],[]]