[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BQBVCNGW0PRAP06GZX7JWK":3,"skill-same:01M7BQBVCNGW0PRAP06GZX7JWK":47},{"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},"01M7BQBVCNGW0PRAP06GZX7JWK","freeze",null,"\u002Fcs:freeze \u003Cdecision> \u003Cdays> — Lock a strategic decision for a cooldown period to prevent impulse reversal. Mirrors gstack's safety primitives for the business layer. Use when an irreversible decision was made under pressure — e.g. a layoff plan or multi-year contract — and deserves a cooling-off lock before execution.","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\u002Fc-level-agents\u002Fskills\u002Ffreeze\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"freeze\"\ndescription: \"\u002Fcs:freeze \u003Cdecision> \u003Cdays> — Lock a strategic decision for a cooldown period to prevent impulse reversal. Mirrors gstack's safety primitives for the business layer. Use when an irreversible decision was made under pressure — e.g. a layoff plan or multi-year contract — and deserves a cooling-off lock before execution.\"\n---\n\n# \u002Fcs:freeze — Cooldown Lock on a Decision\n\n**Command:** `\u002Fcs:freeze \u003Cdecision-path> \u003Cdays>`\n\nLocks a decision for a defined cooldown period. During the freeze, the chief-of-staff router refuses to re-litigate the decision unless a kill criterion explicitly triggers.\n\nInspired by gstack's `\u002Ffreeze` and `\u002Fguard` safety primitives — adapted from code-scoping to strategic-scoping.\n\n## When to Use\n\nFounders are pattern-matchers; pattern-matching after a tough decision often produces a reversal that's actually just decision fatigue. The freeze enforces a discipline:\n\n- After any **irreversible** or **high-cost-to-reverse** decision (fundraise, layoff, market entry)\n- After a **split-vote boardroom** (preserve the call against second-guessing)\n- After a **founder gut-feel** override of unanimous advisor consensus (let it run)\n- During a **personnel transition** (lock the strategy so the new exec can execute, not redebate)\n\n## Default Freeze Periods\n\n| Decision type | Default freeze |\n|---|---|\n| Fundraise round size \u002F lead choice | 30 days |\n| Pricing change | 60 days |\n| Market entry \u002F exit | 90 days |\n| Layoff \u002F RIF | 30 days |\n| Strategic pivot | 90 days |\n| Personnel (exec hire \u002F fire) | 60 days |\n| M&A LOI | 30 days |\n| Custom | specify in command |\n\n## Workflow\n\n1. Read the decision record\n2. Validate it has APPROVED status\n3. Apply freeze: write `freeze_until: YYYY-MM-DD` to the decision record\n4. Add to active-freezes index at `~\u002F.claude\u002Ffreezes\u002Factive.md`\n5. cs-chief-of-staff router now refuses to re-route this topic to the boardroom until:\n   - The freeze period expires, OR\n   - A kill criterion explicitly triggers\n\n## Output\n\nThe decision record is updated in place:\n\n```markdown\n# Decision: \u003Ctitle>\n...\n**Status:** FROZEN\n**Frozen until:** YYYY-MM-DD\n**Reason for freeze:** \u003Ctext>\n**Override condition:** Kill criterion \u003Cname> triggers OR founder issues `\u002Fcs:unfreeze` with stated reason\n```\n\nThe active-freezes index is updated:\n\n```markdown\n# Active Freezes\n**Updated:** YYYY-MM-DD\n\n| Decision | Frozen until | Override condition |\n|---|---|---|\n| \u003Cdecision title> | YYYY-MM-DD | \u003Ckill criterion or \u002Fcs:unfreeze> |\n```\n\n## Override\n\nTo unfreeze before the period ends, the founder runs:\n\n```\n\u002Fcs:unfreeze \u003Cdecision> \u003Creason>\n```\n\nThe unfreeze is logged in the decision history (preserved permanently). Forced overrides create a paper trail that surfaces at post-mortem.\n\n## Auto-Override\n\nIf a kill criterion in the decision triggers, the freeze auto-releases and the chief-of-staff routes immediately to `\u002Fcs:post-mortem`. The freeze does not protect against reality; it protects against impulse.\n\n## Why This Beats \"Just Don't Re-Decide\"\n\nFounders have authority. Without an explicit lock + log, every wobble produces a \"let's discuss this again\" — which is exhausting for advisors and erodes the value of the boardroom. The freeze is **a process**, not a rule; it logs every override so the post-mortem can audit founder discipline.\n\n## Routing\n\n- `\u002Fcs:unfreeze` — explicit early release\n- `\u002Fcs:post-mortem` — auto-triggered if kill criterion fires\n- `\u002Fcs:boardroom` — blocked until unfreeze or expiry\n\n## Related\n\n- Skill: [`decision-logger`](..\u002F..\u002F..\u002Fc-level-advisor\u002Fskills\u002Fdecision-logger\u002FSKILL.md)\n- Agent: [`cs-chief-of-staff`](..\u002F..\u002Fagents\u002Fcs-chief-of-staff.md) — enforces freezes in routing\n\n---\n\n**Version:** 1.0.0\n","# \u002Fcs:freeze — Cooldown Lock on a Decision\n\n**Command:** `\u002Fcs:freeze \u003Cdecision-path> \u003Cdays>`\n\nLocks a decision for a defined cooldown period. During the freeze, the chief-of-staff router refuses to re-litigate the decision unless a kill criterion explicitly triggers.\n\nInspired by gstack's `\u002Ffreeze` and `\u002Fguard` safety primitives — adapted from code-scoping to strategic-scoping.\n\n## When to Use\n\nFounders are pattern-matchers; pattern-matching after a tough decision often produces a reversal that's actually just decision fatigue. The freeze enforces a discipline:\n\n- After any **irreversible** or **high-cost-to-reverse** decision (fundraise, layoff, market entry)\n- After a **split-vote boardroom** (preserve the call against second-guessing)\n- After a **founder gut-feel** override of unanimous advisor consensus (let it run)\n- During a **personnel transition** (lock the strategy so the new exec can execute, not redebate)\n\n## Default Freeze Periods\n\n| Decision type | Default freeze |\n|---|---|\n| Fundraise round size \u002F lead choice | 30 days |\n| Pricing change | 60 days |\n| Market entry \u002F exit | 90 days |\n| Layoff \u002F RIF | 30 days |\n| Strategic pivot | 90 days |\n| Personnel (exec hire \u002F fire) | 60 days |\n| M&A LOI | 30 days |\n| Custom | specify in command |\n\n## Workflow\n\n1. Read the decision record\n2. Validate it has APPROVED status\n3. Apply freeze: write `freeze_until: YYYY-MM-DD` to the decision record\n4. Add to active-freezes index at `~\u002F.claude\u002Ffreezes\u002Factive.md`\n5. cs-chief-of-staff router now refuses to re-route this topic to the boardroom until:\n   - The freeze period expires, OR\n   - A kill criterion explicitly triggers\n\n## Output\n\nThe decision record is updated in place:\n\n```markdown\n# Decision: \u003Ctitle>\n...\n**Status:** FROZEN\n**Frozen until:** YYYY-MM-DD\n**Reason for freeze:** \u003Ctext>\n**Override condition:** Kill criterion \u003Cname> triggers OR founder issues `\u002Fcs:unfreeze` with stated reason\n```\n\nThe active-freezes index is updated:\n\n```markdown\n# Active Freezes\n**Updated:** YYYY-MM-DD\n\n| Decision | Frozen until | Override condition |\n|---|---|---|\n| \u003Cdecision title> | YYYY-MM-DD | \u003Ckill criterion or \u002Fcs:unfreeze> |\n```\n\n## Override\n\nTo unfreeze before the period ends, the founder runs:\n\n```\n\u002Fcs:unfreeze \u003Cdecision> \u003Creason>\n```\n\nThe unfreeze is logged in the decision history (preserved permanently). Forced overrides create a paper trail that surfaces at post-mortem.\n\n## Auto-Override\n\nIf a kill criterion in the decision triggers, the freeze auto-releases and the chief-of-staff routes immediately to `\u002Fcs:post-mortem`. The freeze does not protect against reality; it protects against impulse.\n\n## Why This Beats \"Just Don't Re-Decide\"\n\nFounders have authority. Without an explicit lock + log, every wobble produces a \"let's discuss this again\" — which is exhausting for advisors and erodes the value of the boardroom. The freeze is **a process**, not a rule; it logs every override so the post-mortem can audit founder discipline.\n\n## Routing\n\n- `\u002Fcs:unfreeze` — explicit early release\n- `\u002Fcs:post-mortem` — auto-triggered if kill criterion fires\n- `\u002Fcs:boardroom` — blocked until unfreeze or expiry\n\n## Related\n\n- Skill: [`decision-logger`](..\u002F..\u002F..\u002Fc-level-advisor\u002Fskills\u002Fdecision-logger\u002FSKILL.md)\n- Agent: [`cs-chief-of-staff`](..\u002F..\u002Fagents\u002Fcs-chief-of-staff.md) — enforces freezes in routing\n\n---\n\n**Version:** 1.0.0\n",{"name":5,"description":7},"main","7e219d4f922f94392cb65883ba910846c3c2e71b","c-level-agents\u002Fskills\u002Ffreeze",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 freeze",{"tool":39,"command":40},"bunx","bunx skills add devlify-marketplace\u002Fdevlify-skills --skill freeze",{"tool":42,"command":43},"pnpm","pnpm dlx skills add devlify-marketplace\u002Fdevlify-skills --skill freeze","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdevlify-marketplace\u002Fdevlify-skills\u002Fblob\u002Fmain\u002Fc-level-agents\u002Fskills\u002Ffreeze\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"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":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"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":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"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":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"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":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"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":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"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",[],[]]