[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BQYH4DM31CF4ESM7EHSQPE":3,"skill-same:01M7BQYH4DM31CF4ESM7EHSQPE":71},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7BQYH4DM31CF4ESM7EHSQPE","git-worktree-manager",null,"Run parallel feature work safely with Git worktrees. Standardizes branch isolation, port allocation, environment sync, and cleanup so each worktree behaves like an independent local app. Optimized for multi-agent workflows where each agent or terminal session owns one worktree. Use when running multiple feature branches simultaneously, isolating experimental work, or coordinating multi-agent development across the same repo.","devlify-marketplace\u002Fdevlify-skills","devlify-marketplace","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F196752365?v=4","01M7BPJC94F4G2AG0T3N220BQ3","Sadiq Abdullahi","01M7BPJC9QENFCHFM5NEFAJR1Y",1,"MIT","https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fengineering\u002Fskills\u002Fgit-worktree-manager\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"git-worktree-manager\"\ndescription: \"Run parallel feature work safely with Git worktrees. Standardizes branch isolation, port allocation, environment sync, and cleanup so each worktree behaves like an independent local app. Optimized for multi-agent workflows where each agent or terminal session owns one worktree. Use when running multiple feature branches simultaneously, isolating experimental work, or coordinating multi-agent development across the same repo.\"\n---\n\n# Git Worktree Manager\n\n**Tier:** POWERFUL  \n**Category:** Engineering  \n**Domain:** Parallel Development & Branch Isolation\n\n## Overview\n\nUse this skill to run parallel feature work safely with Git worktrees. It standardizes branch isolation, port allocation, environment sync, and cleanup so each worktree behaves like an independent local app without stepping on another branch.\n\nThis skill is optimized for multi-agent workflows where each agent or terminal session owns one worktree.\n\n## Core Capabilities\n\n- Create worktrees from new or existing branches with deterministic naming\n- Auto-allocate non-conflicting ports per worktree and persist assignments\n- Copy local environment files (`.env*`) from main repo to new worktree\n- Optionally install dependencies based on lockfile detection\n- Detect stale worktrees and uncommitted changes before cleanup\n- Identify merged branches and safely remove outdated worktrees\n\n## When to Use\n\n- You need 2+ concurrent branches open locally\n- You want isolated dev servers for feature, hotfix, and PR validation\n- You are working with multiple agents that must not share a branch\n- Your current branch is blocked but you need to ship a quick fix now\n- You want repeatable cleanup instead of ad-hoc `rm -rf` operations\n\n## Key Workflows\n\n### 1. Create a Fully-Prepared Worktree\n\n1. Pick a branch name and worktree name.\n2. Run the manager script (creates branch if missing).\n3. Review generated port map.\n4. Start app using allocated ports.\n\n```bash\npython scripts\u002Fworktree_manager.py \\\n  --repo . \\\n  --branch feature\u002Fnew-auth \\\n  --name wt-auth \\\n  --base-branch main \\\n  --install-deps \\\n  --format text\n```\n\nIf you use JSON automation input:\n\n```bash\ncat config.json | python scripts\u002Fworktree_manager.py --format json\n# or\npython scripts\u002Fworktree_manager.py --input config.json --format json\n```\n\n### 2. Run Parallel Sessions\n\nRecommended convention:\n\n- Main repo: integration branch (`main`\u002F`develop`) on default port\n- Worktree A: feature branch + offset ports\n- Worktree B: hotfix branch + next offset\n\nEach worktree contains `.worktree-ports.json` with assigned ports.\n\n### 3. Cleanup with Safety Checks\n\n1. Scan all worktrees and stale age.\n2. Inspect dirty trees and branch merge status.\n3. Remove only merged + clean worktrees, or force explicitly.\n\n```bash\npython scripts\u002Fworktree_cleanup.py --repo . --stale-days 14 --format text\npython scripts\u002Fworktree_cleanup.py --repo . --remove-merged --format text\n```\n\n### 4. Docker Compose Pattern\n\nUse per-worktree override files mapped from allocated ports. The script outputs a deterministic port map; apply it to `docker-compose.worktree.yml`.\n\nSee [docker-compose-patterns.md](references\u002Fdocker-compose-patterns.md) for concrete templates.\n\n### 5. Port Allocation Strategy\n\nDefault strategy is `base + (index * stride)` with collision checks:\n\n- App: `3000`\n- Postgres: `5432`\n- Redis: `6379`\n- Stride: `10`\n\nSee [port-allocation-strategy.md](references\u002Fport-allocation-strategy.md) for the full strategy and edge cases.\n\n## Script Interfaces\n\n- `python scripts\u002Fworktree_manager.py --help`\n  - Create\u002Flist worktrees\n  - Allocate\u002Fpersist ports\n  - Copy `.env*` files\n  - Optional dependency installation\n- `python scripts\u002Fworktree_cleanup.py --help`\n  - Stale detection by age\n  - Dirty-state detection\n  - Merged-branch detection\n  - Optional safe removal\n\nBoth tools support stdin JSON and `--input` file mode for automation pipelines.\n\n## Common Pitfalls\n\n1. Creating worktrees inside the main repo directory\n2. Reusing `localhost:3000` across all branches\n3. Sharing one database URL across isolated feature branches\n4. Removing a worktree with uncommitted changes\n5. Forgetting to prune old metadata after branch deletion\n6. Assuming merged status without checking against the target branch\n\n## Best Practices\n\n1. One branch per worktree, one agent per worktree.\n2. Keep worktrees short-lived; remove after merge.\n3. Use a deterministic naming pattern (`wt-\u003Ctopic>`).\n4. Persist port mappings in file, not memory or terminal notes.\n5. Run cleanup scan weekly in active repos.\n6. Use `--format json` for machine flows and `--format text` for human review.\n7. Never force-remove dirty worktrees unless changes are intentionally discarded.\n\n## Validation Checklist\n\nBefore claiming setup complete:\n\n1. `git worktree list` shows expected path + branch.\n2. `.worktree-ports.json` exists and contains unique ports.\n3. `.env` files copied successfully (if present in source repo).\n4. Dependency install command exits with code `0` (if enabled).\n5. Cleanup scan reports no unintended stale dirty trees.\n\n## References\n\n- [port-allocation-strategy.md](references\u002Fport-allocation-strategy.md)\n- [docker-compose-patterns.md](references\u002Fdocker-compose-patterns.md)\n- [README.md](README.md) for quick start and installation details\n\n## Decision Matrix\n\nUse this quick selector before creating a new worktree:\n\n- Need isolated dependencies and server ports -> create a new worktree\n- Need only a quick local diff review -> stay on current tree\n- Need hotfix while feature branch is dirty -> create dedicated hotfix worktree\n- Need ephemeral reproduction branch for bug triage -> create temporary worktree and cleanup same day\n\n## Operational Checklist\n\n### Before Creation\n\n1. Confirm main repo has clean baseline or intentional WIP commits.\n2. Confirm target branch naming convention.\n3. Confirm required base branch exists (`main`\u002F`develop`).\n4. Confirm no reserved local ports are already occupied by non-repo services.\n\n### After Creation\n\n1. Verify `git status` branch matches expected branch.\n2. Verify `.worktree-ports.json` exists.\n3. Verify app boots on allocated app port.\n4. Verify DB and cache endpoints target isolated ports.\n\n### Before Removal\n\n1. Verify branch has upstream and is merged when intended.\n2. Verify no uncommitted files remain.\n3. Verify no running containers\u002Fprocesses depend on this worktree path.\n\n## CI and Team Integration\n\n- Use worktree path naming that maps to task ID (`wt-1234-auth`).\n- Include the worktree path in terminal title to avoid wrong-window commits.\n- In automated setups, persist creation metadata in CI artifacts\u002Flogs.\n- Trigger cleanup report in scheduled jobs and post summary to team channel.\n\n## Failure Recovery\n\n- If `git worktree add` fails due to existing path: inspect path, do not overwrite.\n- If dependency install fails: keep worktree created, mark status and continue manual recovery.\n- If env copy fails: continue with warning and explicit missing file list.\n- If port allocation collides with external service: rerun with adjusted base ports.\n","# Git Worktree Manager\n\n**Tier:** POWERFUL  \n**Category:** Engineering  \n**Domain:** Parallel Development & Branch Isolation\n\n## Overview\n\nUse this skill to run parallel feature work safely with Git worktrees. It standardizes branch isolation, port allocation, environment sync, and cleanup so each worktree behaves like an independent local app without stepping on another branch.\n\nThis skill is optimized for multi-agent workflows where each agent or terminal session owns one worktree.\n\n## Core Capabilities\n\n- Create worktrees from new or existing branches with deterministic naming\n- Auto-allocate non-conflicting ports per worktree and persist assignments\n- Copy local environment files (`.env*`) from main repo to new worktree\n- Optionally install dependencies based on lockfile detection\n- Detect stale worktrees and uncommitted changes before cleanup\n- Identify merged branches and safely remove outdated worktrees\n\n## When to Use\n\n- You need 2+ concurrent branches open locally\n- You want isolated dev servers for feature, hotfix, and PR validation\n- You are working with multiple agents that must not share a branch\n- Your current branch is blocked but you need to ship a quick fix now\n- You want repeatable cleanup instead of ad-hoc `rm -rf` operations\n\n## Key Workflows\n\n### 1. Create a Fully-Prepared Worktree\n\n1. Pick a branch name and worktree name.\n2. Run the manager script (creates branch if missing).\n3. Review generated port map.\n4. Start app using allocated ports.\n\n```bash\npython scripts\u002Fworktree_manager.py \\\n  --repo . \\\n  --branch feature\u002Fnew-auth \\\n  --name wt-auth \\\n  --base-branch main \\\n  --install-deps \\\n  --format text\n```\n\nIf you use JSON automation input:\n\n```bash\ncat config.json | python scripts\u002Fworktree_manager.py --format json\n# or\npython scripts\u002Fworktree_manager.py --input config.json --format json\n```\n\n### 2. Run Parallel Sessions\n\nRecommended convention:\n\n- Main repo: integration branch (`main`\u002F`develop`) on default port\n- Worktree A: feature branch + offset ports\n- Worktree B: hotfix branch + next offset\n\nEach worktree contains `.worktree-ports.json` with assigned ports.\n\n### 3. Cleanup with Safety Checks\n\n1. Scan all worktrees and stale age.\n2. Inspect dirty trees and branch merge status.\n3. Remove only merged + clean worktrees, or force explicitly.\n\n```bash\npython scripts\u002Fworktree_cleanup.py --repo . --stale-days 14 --format text\npython scripts\u002Fworktree_cleanup.py --repo . --remove-merged --format text\n```\n\n### 4. Docker Compose Pattern\n\nUse per-worktree override files mapped from allocated ports. The script outputs a deterministic port map; apply it to `docker-compose.worktree.yml`.\n\nSee [docker-compose-patterns.md](references\u002Fdocker-compose-patterns.md) for concrete templates.\n\n### 5. Port Allocation Strategy\n\nDefault strategy is `base + (index * stride)` with collision checks:\n\n- App: `3000`\n- Postgres: `5432`\n- Redis: `6379`\n- Stride: `10`\n\nSee [port-allocation-strategy.md](references\u002Fport-allocation-strategy.md) for the full strategy and edge cases.\n\n## Script Interfaces\n\n- `python scripts\u002Fworktree_manager.py --help`\n  - Create\u002Flist worktrees\n  - Allocate\u002Fpersist ports\n  - Copy `.env*` files\n  - Optional dependency installation\n- `python scripts\u002Fworktree_cleanup.py --help`\n  - Stale detection by age\n  - Dirty-state detection\n  - Merged-branch detection\n  - Optional safe removal\n\nBoth tools support stdin JSON and `--input` file mode for automation pipelines.\n\n## Common Pitfalls\n\n1. Creating worktrees inside the main repo directory\n2. Reusing `localhost:3000` across all branches\n3. Sharing one database URL across isolated feature branches\n4. Removing a worktree with uncommitted changes\n5. Forgetting to prune old metadata after branch deletion\n6. Assuming merged status without checking against the target branch\n\n## Best Practices\n\n1. One branch per worktree, one agent per worktree.\n2. Keep worktrees short-lived; remove after merge.\n3. Use a deterministic naming pattern (`wt-\u003Ctopic>`).\n4. Persist port mappings in file, not memory or terminal notes.\n5. Run cleanup scan weekly in active repos.\n6. Use `--format json` for machine flows and `--format text` for human review.\n7. Never force-remove dirty worktrees unless changes are intentionally discarded.\n\n## Validation Checklist\n\nBefore claiming setup complete:\n\n1. `git worktree list` shows expected path + branch.\n2. `.worktree-ports.json` exists and contains unique ports.\n3. `.env` files copied successfully (if present in source repo).\n4. Dependency install command exits with code `0` (if enabled).\n5. Cleanup scan reports no unintended stale dirty trees.\n\n## References\n\n- [port-allocation-strategy.md](references\u002Fport-allocation-strategy.md)\n- [docker-compose-patterns.md](references\u002Fdocker-compose-patterns.md)\n- [README.md](README.md) for quick start and installation details\n\n## Decision Matrix\n\nUse this quick selector before creating a new worktree:\n\n- Need isolated dependencies and server ports -> create a new worktree\n- Need only a quick local diff review -> stay on current tree\n- Need hotfix while feature branch is dirty -> create dedicated hotfix worktree\n- Need ephemeral reproduction branch for bug triage -> create temporary worktree and cleanup same day\n\n## Operational Checklist\n\n### Before Creation\n\n1. Confirm main repo has clean baseline or intentional WIP commits.\n2. Confirm target branch naming convention.\n3. Confirm required base branch exists (`main`\u002F`develop`).\n4. Confirm no reserved local ports are already occupied by non-repo services.\n\n### After Creation\n\n1. Verify `git status` branch matches expected branch.\n2. Verify `.worktree-ports.json` exists.\n3. Verify app boots on allocated app port.\n4. Verify DB and cache endpoints target isolated ports.\n\n### Before Removal\n\n1. Verify branch has upstream and is merged when intended.\n2. Verify no uncommitted files remain.\n3. Verify no running containers\u002Fprocesses depend on this worktree path.\n\n## CI and Team Integration\n\n- Use worktree path naming that maps to task ID (`wt-1234-auth`).\n- Include the worktree path in terminal title to avoid wrong-window commits.\n- In automated setups, persist creation metadata in CI artifacts\u002Flogs.\n- Trigger cleanup report in scheduled jobs and post summary to team channel.\n\n## Failure Recovery\n\n- If `git worktree add` fails due to existing path: inspect path, do not overwrite.\n- If dependency install fails: keep worktree created, mark status and continue manual recovery.\n- If env copy fails: continue with warning and explicit missing file list.\n- If port allocation collides with external service: rerun with adjusted base ports.\n",{"name":5,"description":7},"main","7e219d4f922f94392cb65883ba910846c3c2e71b","engineering\u002Fskills\u002Fgit-worktree-manager",0,"https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills","https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace","devlify.com.ng","Software Developer & full-stack dev building secure web and mobile applications, AI\u002FML solutions, and scalable digital products. Founder of Devlify ","2026-08-30 00:40:50",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add devlify-marketplace\u002Fdevlify-skills --skill git-worktree-manager",{"tool":39,"command":40},"bunx","bunx skills add devlify-marketplace\u002Fdevlify-skills --skill git-worktree-manager",{"tool":42,"command":43},"pnpm","pnpm dlx skills add devlify-marketplace\u002Fdevlify-skills --skill git-worktree-manager","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fengineering\u002Fskills\u002Fgit-worktree-manager\u002FSKILL.md",true,[47,53,57,61,67],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"README.md","REFERENCE","参考文档",1291,"https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fengineering\u002Fskills\u002Fgit-worktree-manager\u002FREADME.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fdocker-compose-patterns.md",1149,"https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fengineering\u002Fskills\u002Fgit-worktree-manager\u002Freferences\u002Fdocker-compose-patterns.md",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fport-allocation-strategy.md",1030,"https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fengineering\u002Fskills\u002Fgit-worktree-manager\u002Freferences\u002Fport-allocation-strategy.md",{"path":62,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":65,"sourceHtmlUrl":66},"scripts\u002Fworktree_cleanup.py","SCRIPT","脚本",6620,"https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fengineering\u002Fskills\u002Fgit-worktree-manager\u002Fscripts\u002Fworktree_cleanup.py",{"path":68,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":69,"sourceHtmlUrl":70},"scripts\u002Fworktree_manager.py",8566,"https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fengineering\u002Fskills\u002Fgit-worktree-manager\u002Fscripts\u002Fworktree_manager.py",[72,79,86,93,100,107],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7BRV5Q3BJT22HG25WJFTKZN","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. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7BRTW6RRTHXT6SBE41AY5GD","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, deepread for evidence-first reading of supplied documents) 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. Use when the user makes any research request that doesn't obviously match a more-specific specialist skill (e.g., \"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]\"). Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.","https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fresearch\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7BRTMK3PGPNH76R2HY57AKC","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. Use when the user requests multi-source recency intelligence on a topic (e.g., '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]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7BRTAR0YJWNZ2AP3QTH39BW","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. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). 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\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M7BRT3J0V5A9V3VJ96G97AGW","notebooklm","Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio\u002FVideo Overviews, Mind Maps, Reports incl. Briefing Doc\u002FStudy Guide\u002FFAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":19},"01M7BRSS7P0CJP7X9ERDFYN6GC","litreview","Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a formatted Word (.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' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., '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 use for single one-off paper searches wanting a quick list — that's a plain PubMed\u002FOpenAlex (or Consensus) query.","https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[]]