agentsclimarketplace

Plan & spec

10,807 rows, by stacks then stars

2,010 of these skill files have been read, by 1,360 distinct authors, and what they tell an agent counted. What Plan & spec authors agree on, and what they forbid

  • Alterlab thesis supervisor

    AlterLab-IEU/AlterLab-Academic-Skills/skills/core/alterlab-thesis-supervisor Skill

    87★ repo

    Supervises theses and dissertations end to end — structure guidance from proposal through defense, chapter-by-chapter writing support (introduction, literature review, methodology, results, discussion), supervision strategies, committee management, defense and viva voce preparation, timeline planning, feedback integration, examiner-expectation guidance, and formatting (APA 7, Chicago, university styles). Use when the request mentions thesis, dissertation, supervision, defense preparation, viva, proposal defense, thesis structure, thesis chapter, literature review chapter, methodology chapter, results chapter, discussion chapter, thesis timeline, committee, thesis formatting, or dissertation proposal. Part of the AlterLab Academic Skills suite.

  • Alterlab tubitak proposal

    AlterLab-IEU/AlterLab-Academic-Skills/skills/turkish-academia/alterlab-tubitak-proposal Skill

    87★ repo

    Scaffolds TÜBİTAK ARDEB national research proposals (1001 Bilimsel ve Teknolojik Araştırma Projeleri and 1002-A Hızlı Destek Modülü) against the official .doc form trees: 1. ÖZGÜN DEĞER (konunun önemi/özgün değer, araştırma sorusu/hipotezi, amaç ve hedefler), 2. YÖNTEM, 3. PROJE YÖNETİMİ (iş-zaman çizelgesi/iş paketleri + B-Planı, araştırma olanakları), 4. YAYGIN ETKİ, EK-1 Kaynaklar, EK-2 Bütçe ve Gerekçesi. Enforces the 600-word TR/EN özet (abstract) caps, program caps (1001 <=36 months/3,000,000 TRY for 2026-1; 1002-A <=12 months/150,000 TRY, rolling), and the four panel review dimensions; submission via PBS (ardeb-pbs.tubitak.gov.tr) with ARBİS prerequisite. Delegates generic grant craft to alterlab-research-grants. Use when the user wants to write a TÜBİTAK 1001 or 1002-A proposal, draft özgün değer or yaygın etki sections, scaffold a Turkish national grant, or map broader-impacts framing to TÜBİTAK terms. Part of the AlterLab Academic Skills suite.

  • Milestone

    ilang-ai/autocode/skills/milestone Skill

    86★ repo

    Track project milestones. Auto-detect when a significant checkpoint is reached.

  • Plan breakdown

    ilang-ai/autocode/skills/plan-breakdown Skill

    86★ repo

    Break complex tasks into 5-15 ordered steps with time estimates. Dependency order first.

  • Plan estimate

    ilang-ai/autocode/skills/plan-estimate Skill

    86★ repo

    Give realistic time and cost estimates for each step. Explain in human terms.

  • Plan priority

    ilang-ai/autocode/skills/plan-priority Skill

    86★ repo

    Decide what to build first. Core function before polish. Revenue before aesthetics.

  • Plan risk

    ilang-ai/autocode/skills/plan-risk Skill

    86★ repo

    Identify risks before building. Flag third-party dependencies, API limits, and cost traps.

  • Project roadmap

    ilang-ai/autocode/skills/project-roadmap Skill

    85★ repo

    Create a visual roadmap for large projects. Phases, milestones, timeline.

  • Requirement lock

    ilang-ai/autocode/skills/requirement-lock Skill

    85★ repo

    Lock confirmed requirements. Don't change them without user approval.

  • Funnel decomposition

    growthack88/growth-marketing-os/skills/funnel-decomposition Skill

    84★ repo

    Senior performance analyst skill that answers "why did sales drop (or jump)?" using rigorous funnel decomposition. Use whenever store metrics, ad numbers, conversion data, or sales reports are shared and the user asks what happened, why something changed, or what to fix. Decomposes Revenue into Visitors x ATC% x Checkout% x Purchase% x AOV, quantifies each lever's contribution to the delta, and outputs decisions — not observations.

    The same file is in 1 other repository

  • Promo brief

    kangarooking/promo-creator-skills/promo-brief Skill

    84★ repo

    产品宣传片创意简报。输入产品说明或 GitHub 链接,自动抓取产品信息,提炼核心卖点,推荐视觉风格和叙事结构。当用户提到"宣传片""promo""产品视频""做个视频介绍""项目宣传"时触发。

  • Ideate

    nelsonwerd/idea-to-ship-skills/skills/ideate Skill

    83★ repo

    Take a fuzzy idea (or an existing thing you want to improve) through a disciplined funnel — explore → pressure-test → converge — and produce one living CONCEPT_BRIEF.md: a locked concept + phased roadmap. Acts as a blunt, honest co-founder (permission to overrule you), forces a success metric and a kill criterion before any roadmap, and hands off cleanly to the prompt-pack skill for building. ALWAYS invoke when the user says any of "help me figure out what to build", "I have an idea for…", "is this idea any good", "pressure-test this idea", "should I build / should I rebuild X", "evaluate whether my app/idea is worth building", "where are we really at", "is this idea or app worth pursuing", "iron out / scope / spec this concept", or "turn my idea into a plan/roadmap". Also invoke proactively when someone is reasoning about WHAT to build or WHETHER an idea is worth it — before any code or prompt pack exists.

    The same file is in 1 other repository

  • Create implementation plan

    eai-org/agent-toolkit/skills/create-implementation-plan Skill

    82★ repo

    Turn a refined requirements document into a structured implementation PLAN.md a fresh session can execute. Planning only — decides the "how", not the "what". Invoke manually only.

  • Ecosystem brief

    runxhq/runx/skills/ecosystem-brief Skill

    82★ repo

    Produce a decision-ready ecosystem briefing from fresh governed evidence without claiming publication.

  • Organic growth

    runxhq/runx/skills/organic-growth Skill

    82★ repo

    Turn bounded search, analytics, site, and market evidence into an evidence-bound SEO and answer-engine growth brief with prioritized actions and a measurement plan, without claiming execution or guaranteed visibility.

  • Work plan

    runxhq/runx/skills/work-plan Skill

    82★ repo

    Compile a bounded objective or issue-intake change set into a dependency-safe Runx execution plan, with deterministic checks for evidence preservation, mutation boundaries, catalog references, and skill-package ownership. Use before multi-step or cross-surface work; this skill plans but does not execute.

  • Director mode

    claude-world/director-mode-lite/skills/director-mode Skill

    81★ repo

    Direct substantial repository work across Claude Code, Codex CLI, or Grok Build with a concise brief, parallel agents, evidence-based completion, and optional cross-CLI continuation. Use for project onboarding, multi-step implementation, agent coordination, verification planning, low-interruption setup, or deciding how another CLI should take over. Do not use it as a permission gate or mandatory workflow.

    The same file is in 2 other repositories

  • Focus problem

    claude-world/director-mode-lite/skills/focus-problem Skill

    81★ repo

    Deeply scope a problem before coding: parallel Explore agents map related files, similar implementations, and test patterns, producing a problem definition, boundaries, and minimal implementation plan. Use when planning a feature, investigating a bug, or entering an unfamiliar codebase area.

  • Plan

    claude-world/director-mode-lite/skills/plan Skill

    81★ repo

    Break a complex task into an ordered, dependency-aware task list with estimates and verification steps. Use when a request spans multiple components or days, before starting large features, or when the user runs /plan.

  • Plan review

    longranger2/claude-gpt-workflow/plan-review Skill

    81★ repo

    Use when the user says "/plan-review", "plan review", or "PRD review" and provides a plan file path that needs critical review and iterative refinement with Codex.

  • Nasa hsi

    jgsystemsconsulting/jgs-se-knowledge-packs/packs/nasa-hsi Skill

    no license81★ repo

    Knowledge base from NASA Human Systems Integration (HSI) Practitioner's Guide (NASA/SP-2015-3709). Use for HSI process implementation, lifecycle phase activities, function allocation, ConOps development, HSI Plan writing, HSI metrics (MOE/MOP/TPM/KPP), HITL testing strategy, HSI team organisation, scaling/tailoring for program size, and V&V planning. Does not cover the specific human engineering design standards (NASA-STD-3001 content) or detailed HFE methods beyond what the guide itself provides.

  • Nasa rm standard

    jgsystemsconsulting/jgs-se-knowledge-packs/packs/nasa-rm-standard Skill

    no license81★ repo

    Knowledge base from NASA-STD-8729.1A — NASA's R&M (Reliability and Maintainability) standard covering spaceflight and support systems (Revision A, 2017-06-13). Use for NASA's objectives-driven R&M framework — the R&M objectives hierarchy (one Top Objective decomposed into four sub-objectives, paired with tailorable strategies), how R&M requirements are established inside the SMA Plan required by NPR 7120.5, the SMA Technical Authority concurrence/independent-evaluation governance, milestone vs. readiness review gates, the reliability/maintainability/availability vocabulary (Ai vs. Ao, the failure causal chain, risk as a triplet), and the R&M Evidentiary Methods catalogue (FMEA/FMECA, FTA, RBDA, RCM, LORA, plus the space-environment and parts-pedigree analyses). Scoped to NASA spaceflight and support systems and to assurance planning: it is an objectives-and-strategies standard, so it deliberately does NOT prescribe step-by-step analysis procedures (those live in the referenced NASA Preferred Reliability Practices) and is thin on facility R&M, detailed math/derivations, and non-NASA or commercial life cycles.

  • Nasa schedule

    jgsystemsconsulting/jgs-se-knowledge-packs/packs/nasa-schedule Skill

    no license81★ repo

    Knowledge base from the NASA Schedule Management Handbook (2024 edition, Revision 2). Use for program/project schedule management of aerospace and large engineering efforts: the five sub-functions (Planning, Development, Assessment & Analysis, Maintenance & Control, Documentation & Communication); the Integrated Master Schedule (IMS) and the WBS/OBS/CBS breakdown structures; the Schedule Management Plan (SMP) and Basis of Estimate (BoE); Critical Path Method, logic, durations, float and margin; tiered schedule assessment (Requirements/Health/Basis checks, the Shock Test) and the Dimensions of Schedule Reliability; Schedule Risk Analysis (SRA), Integrated Cost-Schedule Risk Analysis (ICSRA), Monte Carlo, correlation, merge bias, and the Joint Confidence Level (JCL); baselining, replan vs. rebaseline, EVM schedule metrics (SPI, BEI, CEI, HMI, Earned Schedule, CPLI), and status/progress/forecast reporting. This is NASA's scheduling doctrine grounded in NPR 7120.5 and the GAO Schedule Assessment Guide. Thin on the underlying mechanics of CPM, statistics, and EVM (it points to companion handbooks); aerospace/space-flight-centric; anchored to the 2024 second edition.

  • Nasa systems modeling

    jgsystemsconsulting/jgs-se-knowledge-packs/packs/nasa-systems-modeling Skill

    no license81★ repo

    Knowledge base from the NASA Systems Modeling Handbook for Systems Engineering (NASA-HDBK-1009A Rev A, 2025). Use for model-based systems engineering (MBSE) wired into NASA's NPR 7123.1 SE processes: the three aspects of MBSE (language / methodology / framework), the NASA SE Engine and its two OOSEM-derived steps (Model Planning, Setting Up the Model), the Modeling Plan as a SEMP subset, the tool-agnostic NASA SE metamodel of elements and relationships across the four SysML pillars (structure / behavior / requirements / parametrics), worked SysML diagrams and tables for stakeholders, requirements, structure and V&V, generating SE work products (ConOps, MOE, MOP, TPM, V&V), the MBSE Grid framework, alternative modeling approaches (PBR, Scenario, System Specification, Verification), and the ConOps model-content template. Scope is bounded to four common technical processes (Stakeholder Expectation Definition, Technical Requirements Definition, Product Verification, Product Validation). Does NOT teach SysML itself, mandate a tool, define NPR 7123.1 processes, cover technical-management processes 10-17, or reproduce the OMG SysML specification.

  • Prd breakdown

    KerberosClaw/kc_ai_skills/prd-breakdown Skill

    80★ repo

    Use when user wants to break a PRD into Azure DevOps work items via vertical-slice plan. Workflow: read PRD → quiz user to lock durable decisions → draft slices with HITL/AFK + blocked_by → call az CLI directly via Bash to create items + Predecessor relations. Idempotent re-runs via fingerprint markers embedded in description. Pure prompt-driven — Claude is the runtime, no Python helper, no install ceremony. Trigger phrases: prd-breakdown / 拆 PRD / 切 vertical slice / 推 slice 到 ADO.

  • Prd create

    KerberosClaw/kc_ai_skills/prd-create Skill

    80★ repo

    Use when user wants to draft a PRD (Product Requirements Document) from raw input (meeting transcripts, hand-waved descriptions, scattered decisions). Workflow: load org's PRD Guideline + writing discipline → lock execution mode (human-run vs unattended-agent-run) → ingest raw input → quiz user numbered-list iterate to fill §1-§15 → draft v0.1 → handle stakeholder merge (review feedback, surface conflicts) → lock v1.0 + sanitize per ADO publication contract → publish to ADO Wiki. For an agent-run PRD, §13 carries the unattended-execution discipline (machine-checkable AC + traffic-light + 3-exits + stop-and-ask), aligned with goal-engineer's loop-run-protocol. NOT for packaging an ALREADY-FROZEN build spec (approved ADR / locked design / machine-checkable AC) into an unattended dispatch — that is goal-engineer's lean build dispatch. Pure prompt-driven — Claude is the runtime, no Python helper. Trigger phrases: 寫 PRD / PRD 撰寫 / prd-create / 初版 PRD / 起 PRD.

  • Spec

    KerberosClaw/kc_ai_skills/spec Skill

    80★ repo

    Use when the user wants a spec-driven development workflow for implementing a feature in the current codebase, from fuzzy idea or existing active spec through requirements, technical plan, tasks, implementation, verification, and closure report. Auto-detects project/spec state, writes persistent files under specs/, asks one grounded question at a time when requirements are ambiguous, and stops at stage gates. NOT for stakeholder PRDs (prd-create), ADO ticket breakdown (prd-breakdown), single architecture-decision records (adr), or already-frozen tasks that should simply be implemented.

  • Workflow router

    KerberosClaw/kc_ai_skills/workflow-router Skill

    80★ repo

    Use when the user is unsure which kc_ai_skills workflow skill to use, or describes work involving PRD, SD/software design, FR, AC/acceptance criteria, ADR, tickets, implementation, debugging, release checks, or unattended agent execution. Triage the request with at most one clarifying question when needed, explain the route in plain language, then hand off to the right specialist skill. This is an entry router only: it does not write PRDs, specs, ADRs, tickets, or dispatches itself.

  • Brainstorm beagle

    existential-birds/beagle/plugins/beagle-analysis/skills/brainstorm-beagle Skill

    79★ repo

    Use when the user has a fuzzy idea and wants to shape it into a concrete project spec before planning or building. Triggers on: "brainstorm this", "I have an idea for...", "help me think through this project", "what should I build", "spec this out". Also catches vague feature descriptions needing structured questioning to clarify scope. Does NOT write code, plan implementation, review strategy docs, or run strategy interviews \u2014 produces a WHAT/WHY spec through dialogue, not a HOW plan.

  • Prfaq beagle

    existential-birds/beagle/plugins/beagle-analysis/skills/prfaq-beagle Skill

    79★ repo

    Use when the user wants to pressure-test a product, internal-tool, or OSS concept against Amazon's Working Backwards PRFAQ gauntlet before committing to a spec. Triggers on: "work backwards", "write a PRFAQ", "press release first", "is this idea worth building", "pressure-test this concept", "filter this before brainstorm", "is this a real product". Also catches solution-first pitches ("I want to build X that does Y") and technology-first pitches ("use AI to...") that need customer-first filtering. Produces a binary pass/fail verdict, not a polished doc. Hardcore coaching — direct, skeptical, concrete. On pass, hands off to brainstorm-beagle with a concept brief. Does NOT write code, plan implementation, scaffold projects, or draft specs.

    The same file is in 3 other repositories

  • Quick plan

    existential-birds/beagle/plugins/beagle-analysis/skills/quick-plan Skill

    79★ repo

    Use when you need a bite-sized, TDD-driven implementation plan but do NOT have a brainstorm-beagle spec to plan against. quick-plan reconstructs intent from the current conversation, fans out domain-expert exploration subagents across the codebase, and synthesizes the same plan format write-plan produces — without requiring `.beagle/concepts/<slug>/spec.md`. Triggers on: "quick plan", "plan this out", "plan what we just discussed", "turn this into an implementation plan", "plan this without a spec", "I don't have a spec, just plan it", "write-plan but no spec". Make sure to use this skill whenever the user wants an implementation or TDD plan and there is no spec to plan against — even if they just say "plan it" after discussing a feature. Writes to `.beagle/plans/<slug>/plan.md`. If a finalized spec already exists at `.beagle/concepts/<slug>/spec.md`, prefer write-plan. Does NOT brainstorm specs, write code, or execute the plan — produces the plan document (and an optional handoff prompt) only.

    The same file is in 2 other repositories

  • Resolve beagle

    existential-birds/beagle/plugins/beagle-analysis/skills/resolve-beagle Skill

    79★ repo

    Use as the follow-up to brainstorm-beagle when a spec has an Open Questions section (or quietly carries latent gaps) that need closing before planning or implementation can begin. Triggers on: "resolve the open questions", "close the gaps in this spec", "research the open items", "finalize my spec", "make this spec implementation-ready", "answer the TBDs". Also triggers whenever the user points at a brainstorm-beagle spec and asks for research, proposals, or answers to unresolved items. Orchestrates parallel research subagents when available (falls back to inline sequential research otherwise), proposes answers one at a time for user approval, then rewrites the spec in place so it arrives at planning with no known gaps. Does NOT write code, design implementation, or create plans — it only produces a complete spec.

  • Strategy interview

    existential-birds/beagle/plugins/beagle-analysis/skills/strategy-interview Skill

    79★ repo

    Use when the user wants to build or think through a strategy via guided conversation \u2014 for a company, product, team, career, or initiative. Triggers on "help me figure out our direction", "what should we focus on", strategic planning, competitive positioning, go-to-market strategy. Also catches indirect requests like prioritization struggles or "we have too many priorities". Does NOT review existing strategy documents (use strategy-review) or brainstorm project features (use brainstorm-beagle).

  • Strategy review

    existential-birds/beagle/plugins/beagle-analysis/skills/strategy-review Skill

    79★ repo

    Use when reviewing, critiquing, or stress-testing an existing strategy document. Evaluates seven dimensions \u2014 diagnosis quality, guiding policy strength, action coherence, assumption exposure, falsifiability \u2014 with optional 7S, Five Forces, Balanced Scorecard, and Hoshin Kanri lenses. Triggers on: review my strategy, poke holes in this plan, what's weak here, strategy audit, red team this. Does NOT build strategy (use strategy-interview) or brainstorm project ideas (use brainstorm-beagle).

  • Write plan

    existential-birds/beagle/plugins/beagle-analysis/skills/write-plan Skill

    79★ repo

    Use when you have a finalized brainstorm-beagle spec at `.beagle/concepts/<slug>/spec.md` and need a bite-sized, TDD-driven implementation plan before any code is written. Triggers on: "write a plan", "plan this spec", "turn the spec into a plan", "now plan the implementation", "write-plan". Reads the spec, designs the file structure, decomposes work into 2-5 minute TDD steps with exact paths and commands, self-reviews against the spec, gets user approval, then writes to `.beagle/concepts/<slug>/plan.md` and offers to generate an execution handoff prompt via the subagent-prompt skill. Does NOT brainstorm specs, write code, or execute the plan — produces the plan document (and an optional handoff prompt) only.

  • Review plan

    existential-birds/beagle/plugins/beagle-core/skills/review-plan Skill

    79★ repo

    Review implementation plans for parallelization, TDD, types, libraries, and security before execution

  • Openspec propose

    JasonxzWen/harness-hub/skills/openspec-propose Skill

    no license77★ repo

    Load when a task needs an explicit OpenSpec proposal with design, spec deltas, and tasks; use product-capability for ordinary implementation contracts.

  • Hedis measure specification

    awslabs/hcls-agent-skills/skills/hedis-measure-specification Skill

    76★ repo

    Reasoning skill for HEDIS measure specification, enrollment logic, exclusion evaluation, NCQA audit requirements, and care gap prioritization. Use when the user asks about HEDIS measure definitions, denominator/numerator/exclusion logic, continuous enrollment rules, Star Rating impact, or care gap closure strategies.

  • Risk adjustment strategy

    awslabs/hcls-agent-skills/skills/risk-adjustment-strategy Skill

    76★ repo

    Reasoning skill for CMS-HCC risk adjustment strategy and methodology. Use when the user asks about CMS-HCC model versions V24 or V28, blended transition methodology, ICD-10-to-HCC mapping logic, disease interaction hierarchies, RAF score methodology, risk adjustment factor calculation, coding gap identification, audit-defensible documentation, HCC recapture strategy, prospective vs retrospective risk adjustment, or Medicare Advantage risk scoring. Triggers include "CMS-HCC", "V24", "V28", "blended transition", "HCC mapping", "disease hierarchy", "RAF score", "risk adjustment", "coding gap", "HCC recapture", "chart review", "audit defensible", "risk score methodology", "Medicare Advantage risk", "capitation revenue", "hierarchical condition category".

  • Spec converge

    JKHeadley/instar/skills/spec-converge Skill

    76★ repo

    Iteratively review an instar-development spec with multi-angle internal reviewers (security, scalability, adversarial, integration, decision-completeness, lessons-aware) and real cross-model external reviewers routed through the agent's own installed CLIs (codex → GPT-tier, gemini → Gemini-tier; one pass per available family) until convergence, then produce a comprehensive ELI10 convergence report. Output is a spec tagged review-convergence — one of the two tags /instar-dev requires before it will touch instar source. NOT user-invocable; run by the instar-developing agent before any spec-driven /instar-dev work.

  • Ios animation design

    existential-birds/beagle/plugins/beagle-ios/skills/ios-animation-design Skill

    75★ repo

    Design and plan iOS animations with structured specs covering transitions, micro-interactions, gesture-driven motion, and loading states. Use when the user asks to plan, design, or spec out animations for an iOS app — including screen transitions, navigation animations, interactive gestures, onboarding flows, or any motion design work. Also use when the user wants animation recommendations or wants to decide between animation approaches before writing code.

  • Gen test plan

    existential-birds/beagle/plugins/beagle-testing/skills/gen-test-plan Skill

    75★ repo

    Analyze repo, detect stack, trace changes to user-facing entry points, generate E2E YAML test plan

  • Run test plan

    existential-birds/beagle/plugins/beagle-testing/skills/run-test-plan Skill

    75★ repo

    Execute YAML test plan, stop on first failure, output rich debug prompt

  • Milestone review

    tranhieutt/software_development_department/.claude/skills/milestone-review Skill

    74★ repo

    Conducts a structured milestone review analyzing delivered features, metrics, blockers, and readiness for the next phase. Use when completing a milestone or when the user mentions milestone review or phase gate.

  • Planning and task breakdown

    tranhieutt/software_development_department/.claude/skills/planning-and-task-breakdown Skill

    74★ repo

    When dealing with a complex issue, epic, or multi-step feature request, break it down into executable, testable, agent-ready tasks before writing code.

  • Review spec

    tranhieutt/software_development_department/.claude/skills/review-spec Skill

    74★ repo

    Reviews a product, technical, API, UI, or implementation spec for completeness, testability, architectural fit, and readiness before planning or implementation.

  • Spec driven development

    tranhieutt/software_development_department/.claude/skills/spec-driven-development Skill

    74★ repo

    Enforces the creation of a clear, actionable specification before any implementation code is written. Prevents hallucinations and architectural drift.

  • Spec evolution

    tranhieutt/software_development_department/.claude/skills/spec-evolution Skill

    74★ repo

    Resolves mismatches between an approved spec and implementation reality by proposing controlled spec changes before code or plan changes continue.

  • Sprint plan

    tranhieutt/software_development_department/.claude/skills/sprint-plan Skill

    74★ repo

    Generates or updates sprint plans with task breakdowns, capacity estimates, dependencies, and risk flags based on milestone goals and past velocity. Use when starting a new sprint, updating sprint progress, or checking sprint status.

  • Ui spec

    tranhieutt/software_development_department/.claude/skills/ui-spec Skill

    74★ repo

    Guidelines and procedures for creating comprehensive UI Specifications from PRDs and prototypes.

  • Funnel strategy

    ominou5/funnel-architect-plugin/skills/funnel-strategy Skill

    73★ repo

    High-level funnel strategy skill. Helps define the funnel's goal, target audience, price point, traffic source, and overall conversion path before any code is written. Use this FIRST before selecting a funnel type.

  • Event curator

    lovstudio/skills/skills/event-curator Skill

    72★ repo

    Generate a complete professional event plan from guest background material. Takes guest bio / CV / intro copy as input, runs a multi-turn clarification dialog (activity type, audience, duration, tone), and outputs a cohesive plan with title + promo copy, minute-level rundown, tiered host question set, and gift / takeaway suggestions. Trigger when user mentions "活动策划", "策划案", "嘉宾对谈", "沙龙策划", "主持人问题", "活动流程", "event planning", "host prep", "salon plan", or pastes a guest bio asking for an event plan.

  • Proposal

    lovstudio/skills/skills/proposal Skill

    72★ repo

    Generate complete business proposals for client projects. Takes client requirement documents (docx/pdf/md) or verbal descriptions as input, outputs a professionally formatted proposal with technical architecture, budget, timeline, risk analysis, and team introduction. Automatically calls illustrate for images and any2pdf for final PDF delivery. Trigger when user mentions "商务方案", "合作评估", "项目评估", "报价方案", "proposal", "需求评估", "给客户出方案", or wants to generate a client-facing project proposal from requirements.

  • Spec init

    oprogramadorreal/optimus-claude/skills/spec-init Skill

    71★ repo

    Scaffolds an empty, product-neutral spec-driven-development cascade (product vision, MVP PRD, target tech-stack) for a human to fill, then hands off to brainstorm. Emits skeletons only; it never authors product content and never overwrites existing docs. Use when starting a new project or product and you want a docs-first plan before writing code.

  • Organizational strategy

    Tibsfox/gsd-skill-creator/examples/skills/business/organizational-strategy Skill

    no license71★ repo

    Organizational strategy and management theory for business decision-making. Covers objectives-based management, the knowledge-worker firm, decentralization, the five management tasks, strategy-as-practice, managerial roles, and the distinction between efficiency and effectiveness. Use when structuring an organization, setting objectives, allocating decision rights, or critiquing a strategy document.

  • Computational thinking

    Tibsfox/gsd-skill-creator/examples/skills/coding/computational-thinking Skill

    no license71★ repo

    Computational thinking as a problem-solving discipline independent of programming languages. Covers the four pillars (decomposition, pattern recognition, abstraction, algorithm design), computational problem-solving methodology (understand, decompose, generalize, formalize, verify), abstraction levels (from hardware through user interface), modeling and simulation, automata and formal languages (DFA, NFA, regular expressions, context-free grammars, Turing machines), computational complexity classes (P, NP, NP-complete, undecidable), and constructionist pedagogy (learning by building, Logo, Scratch, physical computing). Use when approaching unfamiliar problems, teaching problem-solving strategies, analyzing problem complexity, or bridging between domain knowledge and computational solutions.

  • Household economics and budgeting

    Tibsfox/gsd-skill-creator/examples/skills/home-economics/household-economics-and-budgeting Skill

    no license71★ repo

    The household as an economic unit with income, expenses, savings, and debt. Covers the envelope method, fixed vs variable expenses, the 50-30-20 baseline, emergency reserves, the true cost of ownership, opportunity cost in household decisions, and the distinction between a budget and a spending plan. Use when building a household budget, diagnosing why a household is always over, planning a major purchase, or teaching financial literacy at the household level.

  • Nutrition and meal planning

    Tibsfox/gsd-skill-creator/examples/skills/home-economics/nutrition-and-meal-planning Skill

    no license71★ repo

    Household-scale nutrition planning that treats meals as a weekly system, not a series of independent decisions. Covers macronutrient balance, the plate method, weekly rotation, leftover architecture, pantry-to-plate translation, and the food-safety floor that every meal plan must meet. Use when building a weekly menu, adapting a diet to a new household member, planning for a week of predictable meals on a budget, or teaching a learner how a kitchen feeds people over time.

  • Language learning strategies

    Tibsfox/gsd-skill-creator/examples/skills/languages/language-learning-strategies Skill

    no license71★ repo

    Meta-cognitive and practical strategies for learning any language -- learner autonomy, goal setting, strategy taxonomy (Oxford's SILL framework), memory strategies, cognitive strategies (note-taking, summarizing, analyzing, reasoning), compensation strategies, metacognitive strategies (planning, monitoring, evaluating), affective strategies (managing anxiety, self-encouragement), social strategies (collaboration, questioning, empathy), immersion design, study habit optimization, plateau diagnosis, and motivation maintenance. Use when designing a language learning plan, diagnosing a learner's stuck points, selecting study methods, or building self-directed learning skills.

  • Strategy selection

    Tibsfox/gsd-skill-creator/examples/skills/problem-solving/strategy-selection Skill

    no license71★ repo

    Match problems to the right solving strategy. Covers working backwards, pattern recognition, simplification, systematic listing, trial and error, means-ends analysis, analogical transfer, and decomposition. Use after comprehension is complete to narrow from "general problem" to a concrete approach before committing time and effort.