agentsclimarketplace

Learn & study

4,785 rows, by stacks then stars

598 of these skill files have been read, by 545 distinct authors, and what they tell an agent counted. What Learn & study authors agree on, and what they forbid

  • Legal doc summarizer

    Uhudsavasindankacanokcu2/legal-skills-for-claude/legal-doc-summarizer Skill

    no license0★ repo

    Summarize long legal documents (contracts, terms of service, privacy policies, court filings, leases) into plain-English key points, obligations, deadlines, and red flags. Use when the user pastes or uploads a long legal/dense document and wants the gist, key dates, obligations, or "what does this actually say".

  • Learn from session

    Erlemar/cayley-puzzles/.claude/skills/learn-from-session Skill

    no license0★ repo

    Extract patterns and learnings from the current session. Use when asked to learn from this session, capture session learnings, or review what was accomplished. Outputs structured findings for use with /llm-rules-updater.

    The same file is in 1 other repository

  • Transcriptsummary

    saurabhshuklagrowisto/saurabh-ai-systems/claude-skills/transcriptsummary Skill

    0★ repo

    Analyze a single B2B sales-call transcript and produce a structured deal-stage diagnostic for [Your Company] using the 5 Agreements framework (Mark Kosoglow / 30 Minutes to President's Club), layered with SPIN discovery notes and a BANT scorecard. Use this whenever someone pastes or uploads a sales-call transcript and asks to "summarize this call", "analyze this deal", "where does this deal stand", "score this call", "is this proposal-ready", "run the 5 agreements on this", or shares a discovery/sales call and wants to know the true stage. This is a DEAL-STAGE VERDICT, not a CRM log — if the user wants a BANT-style note for logging into Zoho CRM, use the crm-note skill instead; if they want an honest assessment of how far the deal has actually progressed, use this skill.

  • Meeting notes to actions

    SkillMedev/remote-team-toolkit/skills/meeting-notes-to-actions Skill

    0★ repo

    Converts raw meeting notes or transcripts into a four-part record - a 3-5 sentence summary, the decisions actually made, an action table with owner, verb-phrased action, due date, and status, and the open questions - without inventing owners, dates, or tasks. Use when someone pastes notes and asks "pull the action items out of this", "summarize this meeting", "who owns what from this transcript", or "what did we actually decide". Do NOT use for preparing the agenda before a meeting happens - use meeting-agenda instead - or for turning extracted actions into engineering tickets - use jira-ticket-writer instead.

    The same file is in 1 other repository

  • First principles

    opelpleple/meta-skills/first-principles Skill

    0★ repo

    Breaks a problem down to fundamental, irreducible truths and rebuilds a solution from them, refusing to reason by analogy or by copying how others already do it. Use this skill when the user is stuck in conventional thinking, asks "why do we even do it this way", wants to challenge baked-in assumptions, faces a hard design or strategy problem with no obvious answer, says "think from first principles", "go back to basics", "forget how everyone else does it", or suspects the standard approach is cargo-culted rather than reasoned. Best when the default solution feels expensive, slow, or inherited rather than chosen.

  • Teach back

    opelpleple/meta-skills/teach-back Skill

    0★ repo

    Forces real understanding of a concept by explaining it in the plainest possible language — as if to a 10-year-old — so that every place the explanation stumbles exposes a genuine gap in understanding (the Feynman technique). Use this skill when the user is learning something new and wants to check whether they actually get it: phrases like "explain like I'm 5", "ELI5", "do I actually understand this", "help me learn X", "I'm studying X", "quiz my understanding", "make sure this sticks", or when they ask you to explain a concept simply or to let them teach it back to you and probe the holes.

  • Weekly trade review skill

    solidx86/intraday-trade/weekly-trade-review-skill Skill

    no license0★ repo

    Runs a weekly review of the user's journaled intraday trades — a longitudinal accountability pass over the trade journal, not a fresh-trade critique. Use this skill whenever the user asks for a weekly review, week-end recap, or pattern summary of their journaled trades: "review my week", "weekly review", "how did I trade this week", "summarize my last N trades", "what patterns am I showing this week", "give me my week-end review", or just "weekly review" with no other context. Operates on the already-journaled trades in data/trade-journal/daily/<date>/ (written by the intraday-trade-mentor skill) — it does NOT take fresh chart screenshots; if the user wants a single trade critiqued, that's the intraday-trade-mentor skill. The review aggregates process grades and theme tags, surfaces recurring psychology, grades whether the user held last week's discipline order, then issues the next week's single discipline focus — drill-sergeant on accountability, head-coach on strategy. Persists each review to data/trade-journal/weekly/.

  • Pitch practice coach

    SkillMedev/founder-fundraising-os/skills/pitch-practice-coach Skill

    0★ repo

    Use when a founder needs to rehearse a pitch or prepare for investor questions. Triggers on "practice my pitch", "mock investor meeting", "what will VCs ask me", "help me prep for a partner meeting", "investor Q&A drill", "I freeze on hard questions", "rehearse my deck". Runs realistic rehearsal and objection drills.

    The same file is in 1 other repository

  • Term sheet explainer

    SkillMedev/founder-fundraising-os/skills/term-sheet-explainer Skill

    0★ repo

    Decodes every clause of a VC term sheet into plain English, marks each term founder-favorable, market-standard, or investor-favorable, and flags deviations in priority order. Use when a founder asks "what does liquidation preference mean", "is this term sheet normal", "explain participating preferred", "what is the option pool shuffle", or receives a term sheet and needs to understand it before responding. Do NOT use for planning counters, trades, and negotiation strategy - use term-sheet-negotiation instead; do NOT use for choosing between a SAFE and a priced round - use safe-vs-priced-round instead.

    The same file is in 2 other repositories

  • Escalation summary

    SkillMedev/customer-support-copilot/skills/escalation-summary Skill

    0★ repo

    Writes a tight escalation summary to engineering or management with a one-line headline, quantified customer impact, repro steps, prior attempts, and a single clear ask. Use when someone says "I need to escalate this ticket", "write this up for engineering", "this bug needs eng eyes", or a support issue must leave the queue for specialist action. Do NOT use for replying to the customer - use support-ticket-reply instead; do NOT use for assigning incident severity and coordinating an active outage - use sev-triage instead; do NOT use for the after-the-fact incident writeup - use postmortem-writer instead.

    The same file is in 1 other repository

  • Obsidian doc prompter

    rubber-ducks-syndicate/obsidian-documentation-skill/skills/obsidian-doc-prompter Skill

    0★ repo

    Documentation reflex for coding sessions. Consult this skill whenever you have just implemented, modified, refactored, or fixed something in a project — a feature, an endpoint, a component, a schema change, an architectural change, a dependency swap — even if the user never mentioned documentation. It checks whether the change is worth documenting, asks the user, and on yes hands a pre-approved scope to the obsidian-documentation orchestrator. It never documents without consent.

  • Obsidian documentation

    rubber-ducks-syndicate/obsidian-documentation-skill/skills/obsidian-documentation Skill

    0★ repo

    Orchestrator and ONLY entrypoint for all Obsidian documentation work. Use this skill whenever the user wants to document anything in their Obsidian vault — features, architecture, decisions (ADRs), diagrams, tags, links/MOCs, or vault cleanup — or says things like "document this", "write this up in Obsidian", "add this to the vault", "create an ADR", "update the docs". Even if the request seems to match a specialist skill directly, route through this skill. It analyzes intent, gathers context (git diff, repo, vault, conversation), delegates to specialist skills, and assembles one coherent documentation package.

  • Obsidian excalidraw

    rubber-ducks-syndicate/obsidian-documentation-skill/skills/obsidian-excalidraw Skill

    0★ repo

    Specialist skill for generating Excalidraw diagrams (.excalidraw.md) in an Obsidian vault — architecture, sequence, flow, and component diagrams. Normally invoked by the obsidian-documentation orchestrator. Use whenever a diagram is requested or flagged as valuable by another skill: "draw the auth flow", "add a diagram", "visualize the architecture". Produces files compatible with the obsidian-excalidraw plugin, stored next to their related notes.

  • Obsidian feature

    rubber-ducks-syndicate/obsidian-documentation-skill/skills/obsidian-feature Skill

    0★ repo

    Specialist skill for documenting features (backend + frontend) in an Obsidian vault. Normally invoked by the obsidian-documentation orchestrator, but also use it directly when the user asks to document a feature, a new capability, an endpoint, a UI flow, or "what I just built" — including from a git diff or PR. Produces feature notes under Features/ with backend/frontend sub-notes, ready for the tagging and linking pass.

  • Obsidian linking

    rubber-ducks-syndicate/obsidian-documentation-skill/skills/obsidian-linking Skill

    0★ repo

    Specialist skill that owns the knowledge graph of an Obsidian vault — bidirectional wiki links, Maps of Content (MOCs), backlink maintenance, and orphan prevention. Normally invoked by the obsidian-documentation orchestrator as the final pass of every documentation run, and directly for "connect these notes", "build a MOC", "find orphan notes", "the graph view is a mess" requests.

  • Obsidian maintenance

    rubber-ducks-syndicate/obsidian-documentation-skill/skills/obsidian-maintenance Skill

    0★ repo

    Specialist skill for keeping an Obsidian vault healthy over time — deduplicating overlapping notes, merging, refactoring outdated documentation, fixing structural mess, and updating docs after code changes. Normally invoked by the obsidian-documentation orchestrator. Use for "clean up the vault", "these notes overlap", "the docs are outdated", "refactor the documentation", or when any skill notices duplication or rot.

  • Obsidian query

    rubber-ducks-syndicate/obsidian-documentation-skill/skills/obsidian-query Skill

    0★ repo

    Specialist skill for answering questions FROM the Obsidian vault — "how does X work", "why did we choose Y", "what do we know about Z", "find the docs about…". It owns the hidden per-project index (a catalog of every note with one-line summaries, in <vault>/.claude-docs/) and run log, reads the index first to locate relevant notes, then synthesizes a cited answer. Valuable answers can be filed back into the vault. Use whenever the user asks a question whose answer should live in the documentation, or asks to find/locate notes.

  • Obsidian tagging

    rubber-ducks-syndicate/obsidian-documentation-skill/skills/obsidian-tagging Skill

    0★ repo

    Specialist skill that owns the tag taxonomy of an Obsidian vault — assigning tags to new notes, keeping tags consistent, extending the hierarchy, and auditing/fixing tag drift. Normally invoked by the obsidian-documentation orchestrator as the final pass of every documentation run, and directly for "fix my tags", "what tags should this have", "tags are a mess" requests.

  • Conductor memory

    scoobydrew83/skills/plugins/coordinated-skills/skills/conductor-memory Skill

    0★ repo

    Extract and build a complete memory pack from a Claude conversation or session, synthesizing it into vault-ready artifacts so the next session resumes with full context. Produces a conversation summary, artifact index, communication-style and project-context notes, a machine-readable seed JSON and persona YAML, verification and maintenance checklists, and a generalized integration.py that copies the pack into an Obsidian vault and updates a Claude Code resume pointer (with an optional MCP/vector-store hook). Use this whenever the user says 'build conductor memory', 'extract memory from this conversation', 'capture this session', 'snapshot our progress', 'save this to memory', or 'update conductor memory' - and also when wrapping up a substantial working session that should persist for continuity across Claude Code, Obsidian, or MCP, even if they don't say the word 'memory'. Built for the Conductor Method continuity system; works for any project needing durable cross-session memory.

  • Instinct learn eval

    search-atlas-group/amm-founding-circle/skills/instinct-learn-eval Skill

    0★ repo

    Score existing instincts, execute status transitions, prune stale candidates, write scorecard

  • Instinct learn

    search-atlas-group/amm-founding-circle/skills/instinct-learn Skill

    0★ repo

    Extract instincts from the current session — corrections, confirmations, and tool-usage patterns

  • Ml math tutor v2

    CondoriPaulo/Learning-Skills---Claude/ml-math-tutor-v2 Skill

    no license0★ repo

    A list of skills focused on creating HTMLs (Works for mobile or Laptop) to can teach you any subject and provide problems for you.

  • Study from lecture

    CondoriPaulo/Learning-Skills---Claude/study-from-lecture Skill

    no license0★ repo

    A list of skills focused on creating HTMLs (Works for mobile or Laptop) to can teach you any subject and provide problems for you.

  • Notion helper formulas

    chiragg-ds/claude-skills/skills/notion-helper-formulas Skill

    0★ repo

    Patch checkbox helper formulas onto Notion databases — collapse complex multi-condition view filters into single-checkbox lookups. Handles Notion's cross-formula-reference limit.

  • Notion provision

    chiragg-ds/claude-skills/skills/notion-provision Skill

    0★ repo

    Provision a Notion workspace (section pages + databases) from a YAML schema spec. Idempotent. Use when building a new Notion-based OS from a structured spec.

  • Notion schema dump

    chiragg-ds/claude-skills/skills/notion-schema-dump Skill

    0★ repo

    Generate a canonical SCHEMA-REFERENCE.md from a live Notion workspace. Use before authoring any filter, formula, view, or rollup — schema-first rule.

  • Notion seed

    chiragg-ds/claude-skills/skills/notion-seed Skill

    0★ repo

    Bulk import rows into Notion databases from JSON seed files. Supports relation rewiring via template-group lookup (e.g. Tasks Dependencies). Use when you have many rows to add at once.

  • Ve scenario miner

    onyx679/automotive-ve-ai-skills-kit/skills/ve-scenario-miner Skill

    0★ repo

    Extract value-engineering business scenarios, high-frequency tasks, reusable methods, and Skill candidates from interview notes, meeting notes, SOPs, or shadowing records. Use when analyzing value engineering, VAVE, cost analysis, BOM review, supplier collaboration, or process documentation materials.

  • Term sheet explainer

    SkillMedev/startup-fundraising/skills/term-sheet-explainer Skill

    0★ repo

    Decodes every clause of a VC term sheet into plain English, marks each term founder-favorable, market-standard, or investor-favorable, and flags deviations in priority order. Use when a founder asks "what does liquidation preference mean", "is this term sheet normal", "explain participating preferred", "what is the option pool shuffle", or receives a term sheet and needs to understand it before responding. Do NOT use for planning counters, trades, and negotiation strategy - use term-sheet-negotiation instead; do NOT use for choosing between a SAFE and a priced round - use safe-vs-priced-round instead.

    The same file is in 2 other repositories

  • Job interview prep

    SkillMedev/job-search-kit/skills/job-interview-prep Skill

    0★ repo

    Prepares a candidate for a specific job interview - company research checklist, a STAR story bank mined from their resume and mapped to common competencies, a questions-to-ask bank, salary-question deflection lines, and a mock-interview loop. Use when a user says "I have an interview next week, help me prepare", "help me practice answers for this interview", "what should I ask the interviewer", "build me STAR stories from my resume", or "they're going to ask about salary, what do I say". Do NOT use for negotiating after an offer arrives - use salary-negotiation instead - and do NOT use for fixing the resume itself - use resume-reviewer instead.

    The same file is in 1 other repository

  • Notion database

    SkillMedev/project-management/skills/notion-database Skill

    0★ repo

    Designs Notion databases that scale - one entity per database, deliberate property types, two-way relations with rollups, audience-specific views, and row templates - with explicit decision rules for relation vs rollup vs formula. Use when someone asks "design a Notion database for my projects", "should this be a relation or a rollup", "my Notion workspace is a junk drawer", or "set up a tasks and projects system in Notion". Do NOT use for building a full personal knowledge-management method with capture and review habits - use second-brain instead. For SQL or application database schemas, use database-schema.

    The same file is in 1 other repository

  • Meeting notes

    Sidsaladi9/persona-os/plugins/product-manager-os/skills/meeting-notes Skill

    0★ repo

    Turns raw, messy meeting notes or a transcript into a crisp, shareable summary. Use when someone says "summarize these meeting notes", "turn this transcript into action items", "what did we decide", "clean up my notes", or "send a recap". Works for any meeting type — standup, planning, review, 1:1, or stakeholder sync — from pasted notes or a connected transcript tool.

  • Release notes

    Sidsaladi9/persona-os/plugins/product-manager-os/skills/release-notes Skill

    0★ repo

    Turns a list of shipped changes into audience-tiered release notes — a benefit-led user-facing changelog, a what/why/impact internal log, and a short social announcement cut. Use when you say "write release notes," "draft the changelog," "we just shipped X, announce it," "turn these tickets into release notes," or "summarize this release for customers and the team."

  • Research brief

    alectivism/organization-ai-skills/org-meetings/skills/research-brief Skill

    0★ repo

    Format research findings into structured briefs for different audiences — board updates, member/client summaries, internal team updates, and public-facing summaries. Use for "research brief", "summarize this research", "board update on", or "[program name] summary".

  • Slack summary

    alectivism/organization-ai-skills/org-meetings/skills/slack-summary Skill

    0★ repo

    Summarize Slack channel activity — decisions, action items, key discussions. Use for "summarize Slack", "Slack recap", "catch me up on [channel]", or "what did I miss in Slack".

  • Salesforce trailhead navigator

    ayanme/salesforce-navigator-suite/skills/salesforce-trailhead-navigator Skill

    0★ repo

    This Navigator researches Salesforce learning paths, certifications, and Trailhead content from official learning resources. Use when the user asks how to learn, study, or get certified on Salesforce: Trailhead modules, trails, superbadges, Trailmixes, certification preparation, Agentforce learning, Data Cloud learning, Marketing Cloud learning, Marketing Cloud Personalization learning, CRM Analytics learning, MuleSoft learning, architect learning, and developer learning.

  • Release notes writer

    mohitkhandelwal242/ai-pm-operator/.claude/skills/release-notes-writer Skill

    no license0★ repo

    Generate slide content for the Product section of a leadership weekly / release-notes deck. Aggregates user-visible product ships from the last 4 weeks across all of the business's repos (the current git repo + every repo in business.json → stack.code_repos[]) plus Jira Done items in ${PROJECT_KEY}, groups them by theme, and produces per-experiment slides with measured impact tables. Use when asked for 'leadership product slides', 'product week deck', 'release notes deck', 'what shipped to production', '/leadership-product-weekly', or '/product-weekly'.

  • Mansplain

    mehdiforoozandeh/skills/skills/mansplain Skill

    0★ repo

    Re-situate something you (the agent) just said when it drifted into jargon or internal framing the user never grounded — NOT by dumbing it down (ELI5), but by filling in the missing context: a brief backdrop, how it fits together, and where it lands in *this* conversation, always with 1–2 simple concrete examples. Governed by one rule — the certainty test: say and explain only what you are not sure the user already knows. Use when the user asks to have something put in perspective, re-anchored, or explained in the conversation's own terms. Triggers: /mansplain, /mansplain <term>, "you lost me", "put that in perspective", "situate that", "wait — what actually is X and why does it matter here".

  • Pptx

    Drvivek34/Skill-Bazaar/business-finance/pptx Skill

    no license0★ repo

    Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx filename, regardless of what they plan to do with the content afterward. If a .pptx file needs to be opened, created, or touched, use this skill.

    The same file is in 22 other repositories

  • Code mentor

    ohugonnot/claude-skills/plugins/code-mentor/skills/code-mentor Skill

    0★ repo

    Use when you want to LEVEL UP while coding, not just get code shipped — the assistant slows down at each important decision, explains it from zero (the why, not just the what), keeps YOU doing the thinking, and saves a course-like markdown lesson you can review later. Trigger on "teach me while we build this", "explain your choices as you go", "I want to understand, not just copy", "level up", "mentor mode". NOT for when you just want the code fast (use a normal session).

  • Keel ops

    sayeediftekhar/Keel/skills/keel-ops Skill

    0★ repo

    Operations & connectors lane router. Routes memory, workspace connectors, and meta/skills-management to the right tool — claude-mem, granola, slack, notion, zapier MCPs, plus find-skills and the claude-skills library. Defers to keel-v2. Use for persistent memory, pulling meeting notes, reading/writing Slack or Notion, wide app automation, or discovering/installing new skills.

  • Keel research

    sayeediftekhar/Keel/skills/keel-research Skill

    0★ repo

    Research lane router. Routes knowledge tasks — querying your own documents, real-time web search, and building a searchable second brain — to the right vendored skill (notebooklm-skill, ai-second-brain) or MCP (perplexity). Defers to keel-v2. Use for grounded research, citation-backed answers from your notes, live web lookups, or mining your own AI history.

  • Skill coach

    flll/grow-your-own-skills/skills/skill-coach Skill

    0★ repo

    Use when the user corrects you about the same thing for the second time, or when they ask to create, improve, or prune a skill. Also use when you catch yourself repeating a mistake an existing skill was meant to prevent. Not for one-off fixes that will never recur.

  • Case study story map

    jpoindexter/design-case-study-skills/skills/case-study-story-map Skill

    0★ repo

    Map project evidence into a user-centered outcome arc for a product or design case study. Use when raw notes are chronological, the story lacks tension or a clear result, the product or designer has become the hero instead of the user, a journey needs a beginning-middle-end structure, or research and analytics must be connected to goals, conflicts, pivotal decisions, and measurable outcomes.

  • Case study storytelling

    jpoindexter/design-case-study-skills/skills/case-study-storytelling Skill

    0★ repo

    Build a coherent narrative system for complex design case studies using characters, context, plot, subplots, turning points, branching journeys, theme, scenes, and a trust or emotional arc. Use for multichannel products, nonlinear flows, service ecosystems, AI-agent experiences, portfolio presentations, or drafts that contain good evidence but read like disconnected screens and activities.

  • Case study writing

    jpoindexter/design-case-study-skills/skills/case-study-writing Skill

    0★ repo

    Draft, edit, and finish concise design case-study copy from an evidence ledger or structured outline. Use when a portfolio case study is verbose, vague, generic, overly chronological, full of UX process theater, missing scannable headings and captions, inconsistent in voice, or needs publication-ready structure without inventing research, metrics, outcomes, or quotes.

  • Case study

    jpoindexter/design-case-study-skills/skills/case-study Skill

    0★ repo

    Route and produce evidence-backed product or design case studies from raw notes, research, screenshots, specifications, decision logs, architecture, metrics, and project artifacts. Use when the user invokes /case-study, asks to write, critique, structure, or polish a portfolio case study, needs to explain a complex design project, or needs an AI-agent case study covering autonomy, human oversight, telemetry, trust, latency, failures, and recovery.

  • Weekly performance digest

    kochellenk-afk/google-ads-diagnostic-toolkit/skills/weekly-performance-digest Skill

    0★ repo

    Generate a structured weekly Google Ads performance report with trend analysis, anomaly flags, and prioritized next-week action items. Designed to be sent directly to stakeholders without editing. Use this skill when a user asks for a weekly report, weekly digest, weekly summary, performance recap, "what happened this week", week-over-week analysis, or any recurring weekly reporting need. Trigger on phrases like "weekly digest", "weekly report", "send me a recap", "this week vs last week", "weekly performance update", or any request to summarize Google Ads activity over the last week.

  • Codebase to course

    lankyjo/lankyjo-core-skills/skills/code/codebase-to-course Skill

    no license0★ repo

    Turn any codebase into a beautiful, interactive single-page HTML course that teaches how the code works to non-technical people. Use this skill whenever someone wants to create an interactive course, tutorial, or educational walkthrough from a codebase or project. Also trigger when users mention 'turn this into a course,' 'explain this codebase interactively,' 'teach this code,' 'interactive tutorial from code,' 'codebase walkthrough,' 'learn from this codebase,' or 'make a course from this project.' This skill produces a stunning, self-contained HTML file with scroll-based navigation, animated visualizations, embedded quizzes, and code-with-plain-English side-by-side translations.

  • Cypress explain

    jgamaraalv/delivery-loop/.claude/skills/cypress-explain Skill

    0★ repo

    Explains Cypress tests (E2E and component) and how Cypress works — use to understand, review, or critique tests without editing code, even if the user only says "tests". For creating or fixing tests, prefer cypress-author.

  • Session summary

    youkistudios/session-save-system/skills/session-summary Skill

    0★ repo

    Close an existing source-attributed Session Save record with a human summary and technical resume state. Use when the user asks to summarize, close out, or preserve a finished session. Not a mid-session checkpoint.

  • Leadership brief

    taufiqigalih/launch-decision-kit/skills/leadership-brief Skill

    0★ repo

    Use when someone needs to compress an already-made release, launch, or incident call into a short brief for leadership or a wider audience — a status update, a checkpoint message, a summary to send up before a meeting. Trigger on phrases like "write the update for leadership," "summarize this for the exec sync," "what do I tell the room," or "draft the checkpoint message." This compresses an existing decision; it does not draft the decision itself (use launch-decision-record or incident-decision-log first).

  • Meeting to actions

    moses607/skillforge/skills/meeting-to-actions Skill

    0★ repo

    Convert meeting notes, a transcript, or a rough recap into a clean record of decisions, owned action items, and a follow-up message. Use whenever the user pastes meeting notes or a transcript, says "summarize this meeting", "what did we decide", "pull the action items", "who owns what", or asks for a recap email after a call. Trigger even from messy or partial notes.

  • Engineering mentor

    willianbs/skills/engineering-mentor Skill

    0★ repo

    Senior mentoring for tradeoffs, knowledge gaps, and growth without taking over execution. Use when the user wants guidance, options, or learning. Modes Mentor (default) vs Executor handoff. Never shames, never silently becomes quality-gate or implementer, and always ends with one concrete next action.

  • Listenhub

    Alexxiang2008/awesome-skills-map/skills/第13章ListenHub Skill/ListenHub 解说视频/.agents/skills/listenhub Skill

    0★ repo

    Explain anything — turn ideas into podcasts, explainer videos, or voice narration. Use when the user wants to "make a podcast", "create an explainer video", "read this aloud", "generate an image", or share knowledge in audio/visual form. Supports: topic descriptions, YouTube links, article URLs, plain text, and image prompts.

  • Listenhub

    Alexxiang2008/awesome-skills-map/skills/第13章ListenHub Skill/ListenHub 解说视频/.claude/skills/listenhub Skill

    0★ repo

    Explain anything — turn ideas into podcasts, explainer videos, or voice narration. Use when the user wants to "make a podcast", "create an explainer video", "read this aloud", "generate an image", or share knowledge in audio/visual form. Supports: topic descriptions, YouTube links, article URLs, plain text, and image prompts.

  • Listenhub

    Alexxiang2008/awesome-skills-map/skills/第13章ListenHub Skill/ListenHub 解说视频/.codex/skills/listenhub Skill

    0★ repo

    Explain anything — turn ideas into podcasts, explainer videos, or voice narration. Use when the user wants to "make a podcast", "create an explainer video", "read this aloud", "generate an image", or share knowledge in audio/visual form. Supports: topic descriptions, YouTube links, article URLs, plain text, and image prompts.

  • Listenhub

    Alexxiang2008/awesome-skills-map/skills/第13章ListenHub Skill/ListenHub 解说视频/.opencode/skills/listenhub Skill

    0★ repo

    Explain anything — turn ideas into podcasts, explainer videos, or voice narration. Use when the user wants to "make a podcast", "create an explainer video", "read this aloud", "generate an image", or share knowledge in audio/visual form. Supports: topic descriptions, YouTube links, article URLs, plain text, and image prompts.

  • Startup coach

    ajstars1/startup-coach/startup-coach Skill

    0★ repo

    Master startup coaching orchestrator with a zero-hallucination protocol and a belief-ledger architecture. Use for startup help at ANY stage — finding an idea, validating one, customer discovery, JTBD, Value Proposition Canvas, Business Model Canvas, Where to Play, problem statements, pricing tests, pivot decisions, or scaling. Diagnoses the founder's situation, routes to framework skills, dispatches one subagent per framework in parallel, and verifies every output before the founder sees it.

  • Prompt coach

    goingli0324/muzi-going-skills/plugins/prompt-coach/skills/prompt-coach Skill

    0★ repo

    Turns a vague ask into a Goal / Constraints / Obstacle breakdown, then a ready-to-use structured prompt. Use when the user brings a fuzzy request (「幫我想辦法…」「有什麼方法可以…」「我不知道怎麼處理…」), asks to 「問對問題」, or names a real problem without saying what success looks like, what can't change, or what the blocker is.