write-sdlc-trigger
Writes a 트리거(Initiative) document in Notion "Triggers" DB through interactive Q&A. Conducts section-by-section dialogue with the user following a 7-section bet structure: TL;DR, Problem, DIBB, Fat Marker Sketch, Appetite, Rabbit Holes/No-gos, Success/Kill Criteria. Each section has sentence stems, good/bad examples, and self-check questions that structurally prevent vague or performative writing ("AI will be useful" is literally unwriteable here). Use when the user says "이니셔티브 써줘", "트리거 작성", "write trigger", "write initiative", "베팅 문서 만들자", or wants to document a large bet that requires 2–6 weeks of team time. Do NOT use for small feature additions, bug fixes, or chores: those are Specs, not Triggers.
fastapi-best-practices
A skill for following best practices when developing FastAPI applications. It covers guidelines for project structure, code organization, and common patterns to ensure maintainable and scalable FastAPI projects.
react-state-orchestration
Clean architecture patterns for TanStack Query v5 + Zustand 5 in React/Next.js applications. Use this skill when writing, reviewing, or refactoring state management code — especially when touching server data fetching, Zustand stores, or async mutations. Triggers on tasks involving React Query hooks, Zustand selectors, optimistic updates, or cache management.
write-sdlc-prd
Writes a Product Requirements Document (PRD) section-by-section through interactive Q&A, designed to surface decisions that get expensive when discovered late (pricing, multi-tenancy, i18n, audit, permissions). Trigger whenever the user mentions PRD, 기획서, 요구사항 문서, 제품 기획, 프로덕트 스펙 — and also when they describe wanting to plan out a new product or feature in writing, even without naming the artifact. Use for any feature serious enough to warrant a written spec, not for one-line memos.
git-commit
Use this skill whenever the user wants to commit changes, asks to split working-tree changes into multiple commits, or wants help organizing messy unstaged work — even if they don't explicitly say "commit". Writes Conventional Commits + Gitmoji messages. Strictly never runs `git add .`, `git add -A`, or `git commit -a`; commits only what the user has staged or what an approved grouping plan specifies.
git-pull-request
Generates a polished Pull Request body by analyzing git commit logs, branch lineage, and diffs against the correct parent branch (develop vs main). Use this skill whenever the user asks to "PR 만들어줘", "PR 내용 정리", "PR 본문 작성", "Create a PR", "Summarize commits", "merge 준비", "릴리스 노트", or wraps up work on `features/*`, `feature/*`, `feat/*`, `hotfix/*`, `release/*`, `fix/*`, or `bugfix/*` branches — even if they don't say the word "PR" explicitly.
decompose-sdlc-trigger
Decomposes a 트리거(Initiative) document into N sub-Requests in the Notion Requests DB via AI-draft + Human-edit loop. Reads the parent Trigger's Fat Marker Sketch, Success Criteria, Appetite, and Rabbit Holes; proposes 3–7 candidate sub-Requests aligned with INVEST criteria (Independent, Negotiable, Valuable, Estimable, Small, Testable); lets the human review/edit/reject/add in a single approval gate; then batch-writes to Notion with proper relations. Use when the user says "트리거 분해", "하위 요구사항 나눠줘", "이 Trigger를 Requests로 쪼개줘", "decompose trigger", "break down initiative", or after a Trigger's Phase 8 Review has completed and sub-work items need to exist in Requests DB. Do NOT use for small Requests that directly map to a single Spec (bypass to write-sdlc-spec) or for Triggers without a completed Fat Marker Sketch.
notion-api
Read, query, and write Notion pages and databases via the Notion API (version 2026-03-11) using bundled bash + curl scripts. Use this skill whenever the task touches Notion in any way — reading an arbitrary page to gather development context, looking up a page by title, listing items from a team database, creating a new page, updating properties or content, moving a page to trash. Prefer these scripts over any MCP or ad-hoc curl so behavior stays consistent across the datamktkorea team. Requires `~/.datamktkorea/config.json` (with `notion_token` and `notion_dbs` map) and `jq`.
task-writer
Writes a new Request page in Notion's Requests DB from a free-form description, sizing the body to match the actual work. Use when the user wants to formalize a 업무 지시 / 티켓 / 작업 요청 / hand-off — including "업무 지시 써줘", "티켓 작성해줘", "task 만들어줘". Also trigger when the user describes a task to delegate without explicitly asking for a document. Do NOT use for 2–6주 strategic bets (`write-sdlc-trigger`), implementation specs (`write-sdlc-spec`), or meeting notes (`write-meeting-notes`).
arach
Personal meta-skill for Arach. Use this as the entry point to understand Arach's projects, conventions, available skills, and preferred agent workflows. Activates on "arach's projects", "what does arach work on", when working in any arach/* repo, or when Arach asks to explain something with context, send it to a Scout/ACP-enabled reviewer, collect the review, and decide the next step.
humanizer
|
dewey-docs
Generate AI-agent-ready documentation and static doc sites using Dewey. Use when asked to "set up docs", "create documentation", "make docs agent-friendly", "generate AGENTS.md", "add llms.txt", or "create a doc site".
typescript
>
commit-pr
>
aurora-ux
>
aurora-sheets-sync
>
aurora-schema
>
aurora-project-structure
>
aurora-origin-merge
>
tailwind-4
>
angular-19
>
aurora-cli
>
angular-material-19
>
aurora-development
>
tailwind-3
>
prettier
>
conventional-commits
>
commit
>
Brand Name Oracle
Use this skill when the user wants to forecast a brand name's success. Checks domain availability, social handles, trademarks, pronunciation, international meanings, similar companies, and AI perception prophecy.
Brand Name Comparison
Use this skill when the user wants to compare multiple brand name fates side-by-side to divine which is destined for success.
Brand Name Divination
Use this skill when the user wants to divine or generate brand name ideas for a company, product, or project.
dashform
Create and manage AI-powered smart forms, surveys, and quizzes through the Dashform MCP server. Supports open-ended, single-choice, multiple-choice, and rating questions with AI-powered conversational experiences.
update-skill
修改现有的skill
browser-test
Generate Playwright test scripts for browser-based acceptance verification. Load when DAG tasks touch UI, routes, or user-facing API responses.
intent-router
Classify intent, assess complexity, generate task DAGs. Activates on /go or when user describes work.
market-recon
Guide for using Reddit MCP to gather community sentiment, pain points, and adoption trends. Load this skill when a DAG contains research tasks about market validation, developer experience, or community opinions.
cm
Start, check, or continue any work. Analyzes intent, plans tasks, and orchestrates execution via subagents (L2) or Agent Teams (L3).
escalation-router
决定升级路径（研究员 vs 人工）并格式化适当的交接。当fix-engine耗尽重试次数时使用。
execution-manager
使用git worktrees为并行子协调器生成和管理tmux会话。当各部分准备好执行时使用。
fix-engine
从验收标准创建检查清单，编排executor→validator循环并带重试逻辑。当子协调器开始实现或收到验证失败时使用。
merge-resolver
自动合并所有已完成部分，解决冲突，验证集成。仅当执行管理器检测到所有部分完成时调用。
prd-orchestrator
解析PRD，决定水平拆分策略，生成带验收标准的mini-PRD。当主协调器收到初始PRD或需要重新拆分工作时使用。
create-agent
创建新的subagent，如果需要会自动初始化插件结构
create-command
创建新的slash command，如果需要会自动初始化插件结构
create-hook
创建或添加event hooks到插件
create-skill
创建新的skill，如果需要会自动初始化插件结构
global-setup
一次性配置SkillForge的marketplace设置
init-plugin
插件结构知识库（仅供其他skills引用，不直接调用）
sync-to-marketplace
将插件发布到marketplace
update-agent
修改现有的agent
Page 1559 of 1700 · 84968 results
