[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M783QWB0A7YT652FXTYZGAC7":3,"skill-same:01M783QWB0A7YT652FXTYZGAC7":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},"01M783QWB0A7YT652FXTYZGAC7","remember",null,"Explicitly save important knowledge to auto-memory with timestamp and context. Use when a discovery is too important to rely on auto-capture.","motivatedc-creator\u002FSaafy","motivatedc-creator","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F250662783?v=4","01M782H2D8C7XJGXMJC3YHQAWK","Happy Haris","01M782H2ERMBYEM1NSPPPC06S0",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fengineering-team\u002Fself-improving-agent\u002Fskills\u002Fremember\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"remember\"\ndescription: \"Explicitly save important knowledge to auto-memory with timestamp and context. Use when a discovery is too important to rely on auto-capture.\"\n---\n\n# \u002Fsi:remember — Save Knowledge Explicitly\n\nWrites an explicit entry to auto-memory when something is important enough that you don't want to rely on Claude noticing it automatically.\n\n## Usage\n\n```\n\u002Fsi:remember \u003Cwhat to remember>\n\u002Fsi:remember \"This project's CI requires Node 20 LTS — v22 breaks the build\"\n\u002Fsi:remember \"The \u002Fapi\u002Fauth endpoint uses a custom JWT library, not passport\"\n\u002Fsi:remember \"Reza prefers explicit error handling over try-catch-all patterns\"\n```\n\n## When to Use\n\n| Situation | Example |\n|-----------|---------|\n| Hard-won debugging insight | \"CORS errors on \u002Fapi\u002Fupload are caused by the CDN, not the backend\" |\n| Project convention not in CLAUDE.md | \"We use barrel exports in src\u002Fcomponents\u002F\" |\n| Tool-specific gotcha | \"Jest needs `--forceExit` flag or it hangs on DB tests\" |\n| Architecture decision | \"We chose Drizzle over Prisma for type-safe SQL\" |\n| Preference you want Claude to learn | \"Don't add comments explaining obvious code\" |\n\n## Workflow\n\n### Step 1: Parse the knowledge\n\nExtract from the user's input:\n- **What**: The concrete fact or pattern\n- **Why it matters**: Context (if provided)\n- **Scope**: Project-specific or global?\n\n### Step 2: Check for duplicates\n\n```bash\nMEMORY_DIR=\"$HOME\u002F.claude\u002Fprojects\u002F$(pwd | sed 's|\u002F|%2F|g; s|%2F|\u002F|; s|^\u002F||')\u002Fmemory\"\ngrep -ni \"\u003Ckeywords>\" \"$MEMORY_DIR\u002FMEMORY.md\" 2>\u002Fdev\u002Fnull\n```\n\nIf a similar entry exists:\n- Show it to the user\n- Ask: \"Update the existing entry or add a new one?\"\n\n### Step 3: Write to MEMORY.md\n\nAppend to the end of `MEMORY.md`:\n\n```markdown\n- {{concise fact or pattern}}\n```\n\nKeep entries concise — one line when possible. Auto-memory entries don't need timestamps, IDs, or metadata. They're notes, not database records.\n\nIf MEMORY.md is over 180 lines, warn the user:\n\n```\n⚠️ MEMORY.md is at {{n}}\u002F200 lines. Consider running \u002Fsi:review to free space.\n```\n\n### Step 4: Suggest promotion\n\nIf the knowledge sounds like a rule (imperative, always\u002Fnever, convention):\n\n```\n💡 This sounds like it could be a CLAUDE.md rule rather than a memory entry.\n   Rules are enforced with higher priority. Want to \u002Fsi:promote it instead?\n```\n\n### Step 5: Confirm\n\n```\n✅ Saved to auto-memory\n\n  \"{{entry}}\"\n\n  MEMORY.md: {{n}}\u002F200 lines\n  Claude will see this at the start of every session in this project.\n```\n\n## What NOT to use \u002Fsi:remember for\n\n- **Temporary context**: Use session memory or just tell Claude in conversation\n- **Enforced rules**: Use `\u002Fsi:promote` to write directly to CLAUDE.md\n- **Cross-project knowledge**: Use `~\u002F.claude\u002FCLAUDE.md` for global rules\n- **Sensitive data**: Never store credentials, tokens, or secrets in memory files\n\n## Tips\n\n- Be concise — one line beats a paragraph\n- Include the concrete command or value, not just the concept\n  - ✅ \"Build with `pnpm build`, tests with `pnpm test:e2e`\"\n  - ❌ \"The project uses pnpm for building and testing\"\n- If you're remembering the same thing twice, promote it to CLAUDE.md\n","# \u002Fsi:remember — Save Knowledge Explicitly\n\nWrites an explicit entry to auto-memory when something is important enough that you don't want to rely on Claude noticing it automatically.\n\n## Usage\n\n```\n\u002Fsi:remember \u003Cwhat to remember>\n\u002Fsi:remember \"This project's CI requires Node 20 LTS — v22 breaks the build\"\n\u002Fsi:remember \"The \u002Fapi\u002Fauth endpoint uses a custom JWT library, not passport\"\n\u002Fsi:remember \"Reza prefers explicit error handling over try-catch-all patterns\"\n```\n\n## When to Use\n\n| Situation | Example |\n|-----------|---------|\n| Hard-won debugging insight | \"CORS errors on \u002Fapi\u002Fupload are caused by the CDN, not the backend\" |\n| Project convention not in CLAUDE.md | \"We use barrel exports in src\u002Fcomponents\u002F\" |\n| Tool-specific gotcha | \"Jest needs `--forceExit` flag or it hangs on DB tests\" |\n| Architecture decision | \"We chose Drizzle over Prisma for type-safe SQL\" |\n| Preference you want Claude to learn | \"Don't add comments explaining obvious code\" |\n\n## Workflow\n\n### Step 1: Parse the knowledge\n\nExtract from the user's input:\n- **What**: The concrete fact or pattern\n- **Why it matters**: Context (if provided)\n- **Scope**: Project-specific or global?\n\n### Step 2: Check for duplicates\n\n```bash\nMEMORY_DIR=\"$HOME\u002F.claude\u002Fprojects\u002F$(pwd | sed 's|\u002F|%2F|g; s|%2F|\u002F|; s|^\u002F||')\u002Fmemory\"\ngrep -ni \"\u003Ckeywords>\" \"$MEMORY_DIR\u002FMEMORY.md\" 2>\u002Fdev\u002Fnull\n```\n\nIf a similar entry exists:\n- Show it to the user\n- Ask: \"Update the existing entry or add a new one?\"\n\n### Step 3: Write to MEMORY.md\n\nAppend to the end of `MEMORY.md`:\n\n```markdown\n- {{concise fact or pattern}}\n```\n\nKeep entries concise — one line when possible. Auto-memory entries don't need timestamps, IDs, or metadata. They're notes, not database records.\n\nIf MEMORY.md is over 180 lines, warn the user:\n\n```\n⚠️ MEMORY.md is at {{n}}\u002F200 lines. Consider running \u002Fsi:review to free space.\n```\n\n### Step 4: Suggest promotion\n\nIf the knowledge sounds like a rule (imperative, always\u002Fnever, convention):\n\n```\n💡 This sounds like it could be a CLAUDE.md rule rather than a memory entry.\n   Rules are enforced with higher priority. Want to \u002Fsi:promote it instead?\n```\n\n### Step 5: Confirm\n\n```\n✅ Saved to auto-memory\n\n  \"{{entry}}\"\n\n  MEMORY.md: {{n}}\u002F200 lines\n  Claude will see this at the start of every session in this project.\n```\n\n## What NOT to use \u002Fsi:remember for\n\n- **Temporary context**: Use session memory or just tell Claude in conversation\n- **Enforced rules**: Use `\u002Fsi:promote` to write directly to CLAUDE.md\n- **Cross-project knowledge**: Use `~\u002F.claude\u002FCLAUDE.md` for global rules\n- **Sensitive data**: Never store credentials, tokens, or secrets in memory files\n\n## Tips\n\n- Be concise — one line beats a paragraph\n- Include the concrete command or value, not just the concept\n  - ✅ \"Build with `pnpm build`, tests with `pnpm test:e2e`\"\n  - ❌ \"The project uses pnpm for building and testing\"\n- If you're remembering the same thing twice, promote it to CLAUDE.md\n",{"name":5,"description":7},"main","55ae24ca5523c0499dd70b2874ef674a0e66a85b","engineering-team\u002Fself-improving-agent\u002Fskills\u002Fremember","https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy","https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator","2026-07-04 02:45:55",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add motivatedc-creator\u002FSaafy --skill remember",{"tool":36,"command":37},"bunx","bunx skills add motivatedc-creator\u002FSaafy --skill remember",{"tool":39,"command":40},"pnpm","pnpm dlx skills add motivatedc-creator\u002FSaafy --skill remember","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fengineering-team\u002Fself-improving-agent\u002Fskills\u002Fremember\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},"01M78558T3RQ22S1B5H0FJAY1Y","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\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\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},"01M7854YEAAV883M2PKS04TQEK","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. 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\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fresearch\u002Fresearch\u002Fskills\u002Fresearch\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},"01M7854NCGDBQ6Q0QG2YY4VHSX","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\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\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},"01M78549YZMPYGC1F6S7ZJ4VF8","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\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\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},"01M78541PWEQMBPN91PEZZK8H7","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\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\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},"01M7853P7CWJNW5G0Z99YB6H5D","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\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[]]