[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CGESXF7W080VMJ8J4SVF1V":3,"skill-same:01M7CGESXF7W080VMJ8J4SVF1V":44},{"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":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7CGESXF7W080VMJ8J4SVF1V","self-eval",null,"Honestly evaluate AI work quality using a two-axis scoring system. Use after completing a task, code review, or work session to get an unbiased assessment. Detects score inflation, forces devil's advocate reasoning, and persists scores across sessions.","azhri1990\u002Fjarvis-mega-repo","azhri1990","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F281207543?v=4","01M7BMC0WHXB2ZA9SH1PFJDYNS","Nashriq Mokhtar","01M7C4WMQVQ450E0NA99BG7BHA",0,"MIT","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002FJ.A.R.V.I.S\u002Fcomponents\u002Fcore\u002Fclaude-skills\u002Fengineering\u002Fskills\u002Fself-eval\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"self-eval\"\ndescription: \"Honestly evaluate AI work quality using a two-axis scoring system. Use after completing a task, code review, or work session to get an unbiased assessment. Detects score inflation, forces devil's advocate reasoning, and persists scores across sessions.\"\nlicense: \"MIT\"\n---\n\n# Self-Eval: Honest Work Evaluation\n\nultrathink\n\n**Tier:** STANDARD\n**Category:** Engineering \u002F Quality\n**Dependencies:** None (prompt-only, no external tools required)\n\n## Description\n\nSelf-eval is a Claude Code skill that produces honest, calibrated work evaluations. It replaces the default AI tendency to rate everything 4\u002F5 with a structured two-axis scoring system, mandatory devil's advocate reasoning, and cross-session anti-inflation detection.\n\nThe core insight: AI self-assessment converges to \"everything is a 4\" because a single-axis score conflates task difficulty with execution quality. Self-eval separates these axes, then combines them via a fixed matrix that the model cannot override.\n\n## Features\n\n- **Two-axis scoring** — Independently rates task ambition (Low\u002FMedium\u002FHigh) and execution quality (Poor\u002FAdequate\u002FStrong), then combines via a lookup matrix\n- **Mandatory devil's advocate** — Before finalizing, must argue for both higher AND lower scores, then resolve the tension\n- **Score persistence** — Appends scores to `.self-eval-scores.jsonl` in the working directory, building history across sessions\n- **Anti-inflation detection** — Reads past scores and flags clustering (4+ of last 5 identical)\n- **Matrix-locked scoring** — The composite score comes from the matrix, not from direct selection. Low ambition caps at 2\u002F5 regardless of execution quality\n\n## Usage\n\nAfter completing work in a Claude Code session:\n\n```\n\u002Fself-eval\n```\n\nWith context about what to evaluate:\n\n```\n\u002Fself-eval the authentication refactor we just completed\n```\n\nThe skill reviews the conversation history, identifies what was accomplished, scores it on both axes, runs the devil's advocate check, and appends the result to the score history file.\n\n## Examples\n\n### Example 1: Feature Implementation\n\n```\n\u002Fself-eval added pagination to the user list API\n```\n\nOutput:\n```\n## Self-Evaluation\n\n**Task:** Added cursor-based pagination to the user list API endpoint\n**Ambition:** Medium — New feature with established patterns, but required careful backwards compatibility\n**Execution:** Strong — All tests pass, handles edge cases, existing clients unaffected\n\n**Devil's Advocate:**\n- Lower: Pagination is well-documented. The pattern was copied from another endpoint with minor changes. Could argue Low ambition.\n- Higher: The backwards-compat requirement made this harder than a greenfield implementation. Had to support both offset and cursor modes.\n- Resolution: Medium ambition holds — the backwards-compat constraint added real complexity beyond copy-paste.\n\n**Score: 4** — Solid execution on meaningful work with real constraints.\n```\n\n### Example 2: Bug Fix\n\n```\n\u002Fself-eval\n```\n\nOutput:\n```\n## Self-Evaluation\n\n**Task:** Fixed race condition in the checkout flow causing duplicate orders\n**Ambition:** Medium — Required debugging across 3 services to find the root cause\n**Execution:** Adequate — Fix works but the test only covers the exact scenario reported, not the general class of race conditions\n\n**Devil's Advocate:**\n- Lower: The fix was a single line (adding a mutex). Once found, it was trivial.\n- Higher: Finding the root cause across 3 services took real investigation. The mutex placement required understanding the full flow.\n- Resolution: Medium ambition is correct for the investigation, but execution drops to Adequate — a more thorough fix would address the pattern, not just the instance.\n\n**Score: 3** — Good debugging work but the fix is narrow.\n```\n\n---\n\n## What to Evaluate\n\n$ARGUMENTS\n\nIf no arguments provided, review the full conversation history to identify what was accomplished this session. Summarize the work in one sentence before scoring.\n\n## How to Score — Two-Axis Model\n\nScore on two independent axes, then combine using the matrix. Do NOT pick a number first and rationalize it — rate each axis separately, then read the matrix.\n\n### Axis 1: Task Ambition (what was attempted)\n\nRate the difficulty and risk of what was worked on. NOT how well it was done.\n\n- **Low (1)** — Safe, familiar, routine. No real risk of failure. Examples: minor config changes, simple refactors, copy-paste with small modifications, tasks you were confident you'd complete before starting.\n- **Medium (2)** — Meaningful work with novelty or challenge. Partial failure was possible. Examples: new feature implementation, integrating an unfamiliar API, architectural changes, debugging a tricky issue.\n- **High (3)** — Ambitious, unfamiliar, or high-stakes. Real risk of complete failure. Examples: building something from scratch in an unfamiliar domain, complex system redesign, performance-critical optimization, shipping to production under pressure.\n\n**Self-check:** If you were confident of success before starting, ambition is Low or Medium, not High.\n\n### Axis 2: Execution Quality (how well it was done)\n\nRate the quality of the actual output, independent of how ambitious the task was.\n\n- **Poor (1)** — Major failures, incomplete, wrong output, or abandoned mid-task. The deliverable doesn't meet its own stated criteria.\n- **Adequate (2)** — Completed but with gaps, shortcuts, or missing rigor. Did the thing but left obvious improvements on the table.\n- **Strong (3)** — Well-executed, thorough, quality output. No obvious improvements left undone given the scope.\n\n### Composite Score Matrix\n\n|                        | Poor Exec (1) | Adequate Exec (2) | Strong Exec (3) |\n|------------------------|:---:|:---:|:---:|\n| **Low Ambition (1)**   |  1  |  2  |  2  |\n| **Medium Ambition (2)**|  2  |  3  |  4  |\n| **High Ambition (3)**  |  2  |  4  |  5  |\n\n**Read the matrix, don't override it.** The composite is your score. The devil's advocate below can cause you to re-rate an axis — but you cannot directly override the matrix result.\n\nKey properties:\n- Low ambition caps at 2. Safe work done perfectly is still safe work.\n- A 5 requires BOTH high ambition AND strong execution. It should be rare.\n- High ambition + poor execution = 2. Bold failure hurts.\n- The most common honest score for solid work is 3 (medium ambition, adequate execution).\n\n## Devil's Advocate (MANDATORY)\n\nBefore writing your final score, you MUST write all three of these:\n\n1. **Case for LOWER:** Why might this work deserve a lower score? What was easy, what was avoided, what was less ambitious than it appears? Would a skeptical reviewer agree with your axis ratings?\n2. **Case for HIGHER:** Why might this work deserve a higher score? What was genuinely challenging, surprising, or exceeded the original plan?\n3. **Resolution:** If either case reveals you mis-rated an axis, re-rate it and recompute the matrix result. Then state your final score with a 1-2 sentence justification that addresses at least one point from each case.\n\nIf your devil's advocate is less than 3 sentences total, you're not engaging with it — try harder.\n\n## Anti-Inflation Check\n\nCheck for a score history file at `.self-eval-scores.jsonl` in the current working directory.\n\nIf the file exists, read it and check the last 5 scores. If 4+ of the last 5 are the same number, flag it:\n> **Warning: Score clustering detected.** Last 5 scores: [list]. Consider whether you're anchoring to a default.\n\nIf the file doesn't exist, ask yourself: \"Would an outside observer rate this the same way I am?\"\n\n## Score Persistence\n\nAfter presenting your evaluation, append one line to `.self-eval-scores.jsonl` in the current working directory:\n\n```json\n{\"date\":\"YYYY-MM-DD\",\"score\":N,\"ambition\":\"Low|Medium|High\",\"execution\":\"Poor|Adequate|Strong\",\"task\":\"1-sentence summary\"}\n```\n\nThis enables the anti-inflation check to work across sessions. If the file doesn't exist, create it.\n\n## Output Format\n\nPresent your evaluation as:\n\n## Self-Evaluation\n\n**Task:** [1-sentence summary of what was attempted]\n**Ambition:** [Low\u002FMedium\u002FHigh] — [1-sentence justification]\n**Execution:** [Poor\u002FAdequate\u002FStrong] — [1-sentence justification]\n\n**Devil's Advocate:**\n- Lower: [why it might deserve less]\n- Higher: [why it might deserve more]\n- Resolution: [final reasoning]\n\n**Score: [1-5]** — [1-sentence final justification]\n","# Self-Eval: Honest Work Evaluation\n\nultrathink\n\n**Tier:** STANDARD\n**Category:** Engineering \u002F Quality\n**Dependencies:** None (prompt-only, no external tools required)\n\n## Description\n\nSelf-eval is a Claude Code skill that produces honest, calibrated work evaluations. It replaces the default AI tendency to rate everything 4\u002F5 with a structured two-axis scoring system, mandatory devil's advocate reasoning, and cross-session anti-inflation detection.\n\nThe core insight: AI self-assessment converges to \"everything is a 4\" because a single-axis score conflates task difficulty with execution quality. Self-eval separates these axes, then combines them via a fixed matrix that the model cannot override.\n\n## Features\n\n- **Two-axis scoring** — Independently rates task ambition (Low\u002FMedium\u002FHigh) and execution quality (Poor\u002FAdequate\u002FStrong), then combines via a lookup matrix\n- **Mandatory devil's advocate** — Before finalizing, must argue for both higher AND lower scores, then resolve the tension\n- **Score persistence** — Appends scores to `.self-eval-scores.jsonl` in the working directory, building history across sessions\n- **Anti-inflation detection** — Reads past scores and flags clustering (4+ of last 5 identical)\n- **Matrix-locked scoring** — The composite score comes from the matrix, not from direct selection. Low ambition caps at 2\u002F5 regardless of execution quality\n\n## Usage\n\nAfter completing work in a Claude Code session:\n\n```\n\u002Fself-eval\n```\n\nWith context about what to evaluate:\n\n```\n\u002Fself-eval the authentication refactor we just completed\n```\n\nThe skill reviews the conversation history, identifies what was accomplished, scores it on both axes, runs the devil's advocate check, and appends the result to the score history file.\n\n## Examples\n\n### Example 1: Feature Implementation\n\n```\n\u002Fself-eval added pagination to the user list API\n```\n\nOutput:\n```\n## Self-Evaluation\n\n**Task:** Added cursor-based pagination to the user list API endpoint\n**Ambition:** Medium — New feature with established patterns, but required careful backwards compatibility\n**Execution:** Strong — All tests pass, handles edge cases, existing clients unaffected\n\n**Devil's Advocate:**\n- Lower: Pagination is well-documented. The pattern was copied from another endpoint with minor changes. Could argue Low ambition.\n- Higher: The backwards-compat requirement made this harder than a greenfield implementation. Had to support both offset and cursor modes.\n- Resolution: Medium ambition holds — the backwards-compat constraint added real complexity beyond copy-paste.\n\n**Score: 4** — Solid execution on meaningful work with real constraints.\n```\n\n### Example 2: Bug Fix\n\n```\n\u002Fself-eval\n```\n\nOutput:\n```\n## Self-Evaluation\n\n**Task:** Fixed race condition in the checkout flow causing duplicate orders\n**Ambition:** Medium — Required debugging across 3 services to find the root cause\n**Execution:** Adequate — Fix works but the test only covers the exact scenario reported, not the general class of race conditions\n\n**Devil's Advocate:**\n- Lower: The fix was a single line (adding a mutex). Once found, it was trivial.\n- Higher: Finding the root cause across 3 services took real investigation. The mutex placement required understanding the full flow.\n- Resolution: Medium ambition is correct for the investigation, but execution drops to Adequate — a more thorough fix would address the pattern, not just the instance.\n\n**Score: 3** — Good debugging work but the fix is narrow.\n```\n\n---\n\n## What to Evaluate\n\n$ARGUMENTS\n\nIf no arguments provided, review the full conversation history to identify what was accomplished this session. Summarize the work in one sentence before scoring.\n\n## How to Score — Two-Axis Model\n\nScore on two independent axes, then combine using the matrix. Do NOT pick a number first and rationalize it — rate each axis separately, then read the matrix.\n\n### Axis 1: Task Ambition (what was attempted)\n\nRate the difficulty and risk of what was worked on. NOT how well it was done.\n\n- **Low (1)** — Safe, familiar, routine. No real risk of failure. Examples: minor config changes, simple refactors, copy-paste with small modifications, tasks you were confident you'd complete before starting.\n- **Medium (2)** — Meaningful work with novelty or challenge. Partial failure was possible. Examples: new feature implementation, integrating an unfamiliar API, architectural changes, debugging a tricky issue.\n- **High (3)** — Ambitious, unfamiliar, or high-stakes. Real risk of complete failure. Examples: building something from scratch in an unfamiliar domain, complex system redesign, performance-critical optimization, shipping to production under pressure.\n\n**Self-check:** If you were confident of success before starting, ambition is Low or Medium, not High.\n\n### Axis 2: Execution Quality (how well it was done)\n\nRate the quality of the actual output, independent of how ambitious the task was.\n\n- **Poor (1)** — Major failures, incomplete, wrong output, or abandoned mid-task. The deliverable doesn't meet its own stated criteria.\n- **Adequate (2)** — Completed but with gaps, shortcuts, or missing rigor. Did the thing but left obvious improvements on the table.\n- **Strong (3)** — Well-executed, thorough, quality output. No obvious improvements left undone given the scope.\n\n### Composite Score Matrix\n\n|                        | Poor Exec (1) | Adequate Exec (2) | Strong Exec (3) |\n|------------------------|:---:|:---:|:---:|\n| **Low Ambition (1)**   |  1  |  2  |  2  |\n| **Medium Ambition (2)**|  2  |  3  |  4  |\n| **High Ambition (3)**  |  2  |  4  |  5  |\n\n**Read the matrix, don't override it.** The composite is your score. The devil's advocate below can cause you to re-rate an axis — but you cannot directly override the matrix result.\n\nKey properties:\n- Low ambition caps at 2. Safe work done perfectly is still safe work.\n- A 5 requires BOTH high ambition AND strong execution. It should be rare.\n- High ambition + poor execution = 2. Bold failure hurts.\n- The most common honest score for solid work is 3 (medium ambition, adequate execution).\n\n## Devil's Advocate (MANDATORY)\n\nBefore writing your final score, you MUST write all three of these:\n\n1. **Case for LOWER:** Why might this work deserve a lower score? What was easy, what was avoided, what was less ambitious than it appears? Would a skeptical reviewer agree with your axis ratings?\n2. **Case for HIGHER:** Why might this work deserve a higher score? What was genuinely challenging, surprising, or exceeded the original plan?\n3. **Resolution:** If either case reveals you mis-rated an axis, re-rate it and recompute the matrix result. Then state your final score with a 1-2 sentence justification that addresses at least one point from each case.\n\nIf your devil's advocate is less than 3 sentences total, you're not engaging with it — try harder.\n\n## Anti-Inflation Check\n\nCheck for a score history file at `.self-eval-scores.jsonl` in the current working directory.\n\nIf the file exists, read it and check the last 5 scores. If 4+ of the last 5 are the same number, flag it:\n> **Warning: Score clustering detected.** Last 5 scores: [list]. Consider whether you're anchoring to a default.\n\nIf the file doesn't exist, ask yourself: \"Would an outside observer rate this the same way I am?\"\n\n## Score Persistence\n\nAfter presenting your evaluation, append one line to `.self-eval-scores.jsonl` in the current working directory:\n\n```json\n{\"date\":\"YYYY-MM-DD\",\"score\":N,\"ambition\":\"Low|Medium|High\",\"execution\":\"Poor|Adequate|Strong\",\"task\":\"1-sentence summary\"}\n```\n\nThis enables the anti-inflation check to work across sessions. If the file doesn't exist, create it.\n\n## Output Format\n\nPresent your evaluation as:\n\n## Self-Evaluation\n\n**Task:** [1-sentence summary of what was attempted]\n**Ambition:** [Low\u002FMedium\u002FHigh] — [1-sentence justification]\n**Execution:** [Poor\u002FAdequate\u002FStrong] — [1-sentence justification]\n\n**Devil's Advocate:**\n- Lower: [why it might deserve less]\n- Higher: [why it might deserve more]\n- Resolution: [final reasoning]\n\n**Score: [1-5]** — [1-sentence final justification]\n",{"name":5,"license":15,"description":7},"main","46d43f3edecde97283ac410e9051444d90120cfb","repos\u002FJ.A.R.V.I.S\u002Fcomponents\u002Fcore\u002Fclaude-skills\u002Fengineering\u002Fskills\u002Fself-eval","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo","https:\u002F\u002Fgithub.com\u002Fazhri1990","2026-10-10 07:58:58",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add azhri1990\u002Fjarvis-mega-repo --skill self-eval",{"tool":36,"command":37},"bunx","bunx skills add azhri1990\u002Fjarvis-mega-repo --skill self-eval",{"tool":39,"command":40},"pnpm","pnpm dlx skills add azhri1990\u002Fjarvis-mega-repo --skill self-eval","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002FJ.A.R.V.I.S\u002Fcomponents\u002Fcore\u002Fclaude-skills\u002Fengineering\u002Fskills\u002Fself-eval\u002FSKILL.md",true,[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":19},"01M7CYPF9V9EMA4ZXS1TTCMBFH","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\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7CYNRJDTQCRF5KGPMBMSB1S","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\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7CYNAVSE84QD7HAWZWTY2FS","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\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7CYN0CE8P5ZN7WV2X06HKPC","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\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7CYMHZ3QRJ9BKRB859KW8TQ","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\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7CYM3D8YKV7R6DT4RNJSF0A","grants","NIH grant research skill for clinical researchers. Grill-me intake (research idea + career stage + preliminary data + environment + submission posture + known institute targets) locks down the funding strategy before any search runs. Runs a 5-facet Consensus positioning analysis (with draft Significance\u002FInnovation language), maps the research to the right NIH institutes and study sections via RePORTER, finds NOSIs and funded overlap, and produces an editable Word document (.docx) with budget\u002Fscope-aware mechanism recommendations, submission timelines, and a mandatory program officer recommendation. Use when the user asks about research funding or makes any grant-related request (e.g., 'grants for [topic]', 'find grants for my research idea', 'what grants match my research', 'help me find NIH funding', 'grant opportunities for my research'). NIH-only scope — non-NIH funders (PCORI, DOD CDMRP, VA, foundations) are out of scope and flagged at intake.","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002Fresearch\u002Fgrants\u002Fskills\u002Fgrants\u002FSKILL.md",[],[]]