Author, read, debug, and modify Claude Code hooks — the user-defined shell commands, HTTP endpoints, or LLM prompts that run automatically at lifecycle events like PreToolUse, PostToolUse, Stop, SessionStart, UserPromptSubmit, and many more. Use this skill whenever the user mentions "hooks", "Claude Code hooks", a `.claude/settings.json` hooks block, auto-formatting on edit, blocking dangerous commands, Stop/PreToolUse/PostToolUse/SessionStart/etc., hook input JSON, `hookSpecificOutput`, `permissionDecision`, exit code 2 behavior, `CLAUDE_PROJECT_DIR` in hook scripts, or wants to guard, observe, or automate anything at a specific point in Claude Code's execution. Also use when the user asks to write a script that "runs before/after" a tool call, runs "when Claude finishes", or wants deterministic guardrails the model can't ignore.
- 📄 capability.manifest.json
- 📄 SKILL.md
Generic bioinformatics reproduction playbook for data discovery, execution planning, degradation, and auditable negative or partial results without paper-specific shortcuts.
- 📁 references/
- 📄 .gitignore
- 📄 LICENSE
- 📄 README.md
你是一位专业的微短剧编剧，精通短视频平台的爆款短剧创作方法论。你将引导用户从选题到完稿，完成一部 50-100 集的完整微短剧剧本。
jup is a command-line tool for installing and managing agent skills across different ai agents, scopes, and projects.
- 📁 per-skill-packages/
- 📁 references/
- 📄 CHANGELOG.md
- 📄 IMPORTANT_LESSONS.md
- 📄 install.sh
Comprehensive documentation and assistance for DMTools - an enterprise dark-factory orchestrator with 96+ MCP tools for Jira, Azure DevOps, Figma, Confluence, Teams, and test automation. Use when working with DMTools, configuring integrations, developing JavaScript agents, generating test cases, building reports (ReportGenerator/ReportVisualizer), creating CLI agent workflows, or setting up CI/CD run tracing (ciRunUrl) for Teammate/Expert/TestCasesGenerator jobs.
Codebase health scanner and technical debt tracker. Use when the user asks about code quality, technical debt, dead code, large files, god classes, duplicate functions, code smells, naming issues, import cycles, or coupling problems. Also use when asked for a health score, what to fix next, or to create a cleanup plan. Supports 28 languages.
Manage Architecture Decision Records using the project's ADR CLI tool. Use when the user wants to create, list, view, lint, or index ADRs, or when working with docs/architecture/ files. Triggers on "create an ADR", "new ADR", "list ADRs", "lint ADRs", "what ADRs exist", "ADR domains".
외부 기여자 PR 검토 절차를 적용한다. PR 정보 수집, mydocs/pr/pr_{N}_review.md 작성, 검증, pr_{N}_report.md 작성, 처리 완료 시 archives/ 이동을 수행한다. 외부 기여자 PR 전용 (내부 타스크에는 사용 금지). --- # 외부 기여자 PR 검토 ## 트리거 - 작업지시자가 "PR #N 리뷰" 또는 "외부 PR 검토"를 명시 지시한 경우 - 본 SKILL을 직접 호출한 경우 ## 사전 조건 - 검토 대상 PR이 외부 기여자 fork에서 본 저장소 `{BASE_BRANCH}`(또는 합의된 base)로 열린 상태 - 내부 타스크 PR(`publish/task{N}`)에는 본 SKILL 사용 금지 — 내부 타스크는 일반 단계 절차로 검토 - `gh` CLI 인증 ## 절차 1. PR 메타 수집 ```bash gh pr view {N} --json number,title,state,baseRefName,headRefName,headRepository,mergeable,mergeStateStatus,reviewDecision,labels,body gh pr diff {N} | head -200 gh pr checks {N} ``` - 이슈 연결, base/head, mergeable, CI 상태 모두 확인 2. 검토 문서 작성: `mydocs/pr/pr_{N}_review.md` - 중앙 템플릿 `mydocs/_templates/external_pr_review.md`를 기준으로 작성한다. - 템플릿을 읽을 수 없는 경우에만 다음 최소 섹션을 fallback으로 사용한다: - PR 정보 (번호, 작성자, base/head, 연결 이슈) - 변경 요약 - 영향 범위와 호환성 (FFI, build, 문서) - 코드/문서 점검 결과 - 검증 계획 (필요한 추가 검증) - 권고 (merge / 수정 요청 / 닫기) - 작업지시자 승인 요청 3. 작업지시자 승인 요청 (검토 방향 결정) 4. 필요 시 수정·검증 계획 문서 작성: `mydocs/pr/pr_{N}_review_impl.md` - 중앙 템플릿 `mydocs/_templates/external_pr_review_impl.md`를 기준으로 작성한다. - 본 저장소에서 추가 검증을 직접 수행할 때 사용 - 작성 후 작업지시자 승인 요청 5. 검증 수행 (해당하는 경우만) - 검증은 변경 유형에 따라 `{PROJECT_VALIDATION_GUIDE}` 정책 적용 6. 최종 보고서 작성: `mydocs/pr/pr_{N}_report.md` - 중앙 템플릿 `mydocs/_templates/external_pr_report.md`를 기준으로 작성한다. - 검토 결과, 검증 결과, 최종 권고, GitHub PR 코멘트 본문(또는 링크) 7. 작업지시자 승인 후 GitHub PR에 코멘트/리뷰 등록 (merge 결정은 작업지시자가 수행) 8. 처리 완료 시 문서 보관 이동 ```bash git mv mydocs/pr/pr_{N}_review.md mydocs/pr/archives/ git mv mydocs/pr/pr_{N}_review_impl.md mydocs/pr/archives/ # 존재 시 git mv mydocs/pr/pr_{N}_report.md mydocs/pr/archives/ ``` 9. 단일 또는 단계별 커밋 (외부 PR 검토는 내부 단계 형식 강제 아님) ```bash git commit -m "PR #{N} 검토: {요약}" ``` ## 검증 - `mydocs/pr/pr_{N}_review.md`가 `mydocs/_templates/external_pr_review.md`의 필수 섹션을 채움 - `mydocs/pr/pr_{N}_review_impl.md`를 작성했다면 `mydocs/_templates/external_pr_review_impl.md`의 필수 섹션을 채움 - `mydocs/pr/pr_{N}_report.md`가 `mydocs/_templates/external_pr_report.md`의 필수 섹션
API 和接口设计——稳定合约、清晰边界。使用 cuando 需要设计 REST API、模块接口或数据合约
- 📁 references/
- 📄 qingsheng-upgrade.md
- 📄 SKILL.md
情圣 — 中文男性社交与恋爱私教。帮兄弟读懂女生发的消息、看懂聊天/朋友圈截图、判断对方是不是对自己有意思、想清楚下一步该回什么 / 该不该回 / 该怎么约。覆盖微信、探探、Soul、Bumble、青藤之恋、Tinder 等平台，从加上好友到确立关系的完整流程，包括开场、暧昧期、约见面、升温、表白、修复冷场、被已读不回怎么办、朋友圈怎么评论。当用户问「她这话什么意思」「我该怎么回」「帮我看看这段聊天」「这截图你给我分析一下」「她对我有意思吗」「该约她了吗」「冷场了怎么破」「这条要不要回」之类的问题时，务必使用本 skill。即使用户没明说「教练」「分析」也应触发——只要话题是和某个具体女生的互动就用。
Activate when user wants to find actual companies in a value chain layer, especially Indian proxies for global themes. Always check connected sources first. Always apply SEBI compliance — research framing only. --- ## Design system — mandatory on all HTML artifacts Every HTML artifact generated by this skill MUST follow this design system. No exceptions. Never invent colours, never use dark backgrounds, never use purple or blue as primary backgrounds. **Palette:** - Page background: `#fafaf8` (warm white) - Card background: `white` - Primary text: `#2c2c2c` (soft charcoal) - Secondary text: `#6b6b6b` - Muted text: `#9a9690` - Accent / headers: `#1b5e52` (deep teal) — the ONLY accent colour - Border: `#e0ddd6` - Hover tint: `#f0f7f4` - Warning/amber: `#fff8f0` background, `#f0d090` border, `#5a3a00` text **Typography:** - Body: `'Georgia', serif`, 14px minimum - Monospace labels: `'Courier New', monospace` - Never below 11px anywhere **Component rules:** - All section headers: `background: #1b5e52; color: white` - Cards: `background: white; border: 1px solid #e0ddd6; border-radius: 8px` - Buttons: `background: #1b5e52; color: white` for primary actions - No gradients, no shadows, no dark backgrounds on outer containers **Pill colour system:** - Global company: `background:#e6f1fb; color:#0c447c; border:0.5px solid #85b7eb` - India listed: `background:#eaf3de; color:#27500a; border:0.5px solid #97c459` - India private: `background:#faeeda; color:#633806; border:0.5px solid #ef9f27` - Flagged: `background:#fcebeb; color:#791f1f; border:0.5px solid #f09595` - Neutral segment: `background:#f3f4f6; color:#374151; border:0.5px solid #d1d5db` - Seeded: `background:#eaf3de; color:#27500a` - Discovered: `background:#e6f1fb; color:#0c447c` **Attribution footer — mandatory on every artifact:** ```html <div style="margin-top:32px;padding-top:12px;border-top:1px solid #e0ddd6;
Ansible automation expert for playbooks, roles, inventories, and infrastructure management
