菜单
GitHub issue management with multi-account support. Creates, lists, views, and closes issues with correct labels and conventions per project. Use when user says "create issue", "file bug", "issue for X", "list issues", "open issues", "triage", or "close issue".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Meta-skill that analyzes past session transcripts to derive new skills, CLAUDE.md rules, and MEMORY.md entries from real usage patterns. Use when Use when user says "session learn", "derive skills", "learn from sessions", "what patterns", "analyze sessions", "extract rules", "what should I add to claude md", "improve my setup", or "what have I been doing repeatedly".
Scan running Claude sessions to see what other agents are working on. Use when asked "what are the other agents doing", "check other sessions", "what's running", "scan agents", "who's working on what", or before picking up new work to avoid overlap.
Find restaurants and food delivery options near a location. Searches Swiggy for restaurants, cross-references Google Maps ratings, and recommends the best options. Learns food preferences over time.
Geographic data validator for aviation and travel applications. Use when user says "geo audit", "check airports", "validate routes", "geo skill", "check geographic data", "verify iata codes", "check distances", or when reviewing any code/data that involves airport codes (IATA/ICAO), city-to-airport mappings, country codes (ISO 3166), flight distances, flight time estimates, flag URLs, or route feasibility. Also use for timezone validation, coordinate checks, and geopolitical accuracy (country names, disputed territories, naming conventions).
A set of resources to help write all kinds of internal communications, using the formats that your company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).
Negotiation analyst for high-stakes deals: co-founder exits, business separations, contract terms, salary negotiations, investor terms. Use when the user asks to: (1) analyze a counterparty's position or message, (2) score/review a draft message before sending, (3) draft a counter-offer, (4) structure BATNA/ZOPA analysis, (5) track concessions across rounds, (6) detect traps or information leakage in proposed terms, (7) prepare for a negotiation call or meeting. Triggers: "score this message", "analyze their position", "what's my BATNA", "review before I send", "draft a counter", "is this a trap", "negotiate", "negotiation", "counter-offer", "deal terms".
| name | issue |
| description | GitHub issue management with multi-account support. Creates, lists, views, and closes issues with correct labels and conventions per project. Use when user says "create issue", "file bug", "issue for X", "list issues", "open issues", "triage", or "close issue". |
Manage GitHub issues across multiple accounts. Always use GitHub Issues, never ISSUES.md files.
Determine which project from context (cwd, user mention). If ambiguous, ask.
| Project | Account alias | Repo |
|---|---|---|
| project-a | gh-project-a | auto-detect from cwd |
| project-b | gh-project-b | org/repo-name |
| personal | gh-personal | auto-detect from cwd |
Check current account first:
gh auth status
Switch to correct account before any gh command.
gh issue create --title "..." --label "LABELS" --body "BODY"
For projects with strict labeling: ALWAYS include required labels. Ask the user for priority if not provided.
For repos you're not in the directory of:
gh issue create --repo org/repo-name --title "..." --body "..."
gh issue list --state open
gh issue list --label "P0" --state open
gh issue list --label "P0,frontend" --state open
gh issue view 123
Always close with a comment explaining the resolution:
gh issue close 123 --comment "Fixed in commit abc123. Verified on live site."
| Type | Labels |
|---|---|
| Priority | P0 (critical), P1 (high), P2 (medium), P3 (low) |
| Area | frontend, backend, pipeline |
Always include one from each group. If user doesn't specify priority, ask.
For bug reports:
**Steps to reproduce:**
1.
2.
**Expected:**
**Actual:**
**Context:** [URL, env, user account if relevant]
For feature requests:
**Problem:**
**Proposed solution:**
**Acceptance criteria:**
- [ ]
Keep bodies concise. No filler. Facts only.