[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ENBBC1R285184BY91TYYYQ":3,"skill-same:01M6ENBBC1R285184BY91TYYYQ":110},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":50,"ownerHtmlUrl":51,"ownerBlogUrl":6,"ownerDescription":52,"updatedAt":53,"install":54,"resources":67},"01M6ENBBC1R285184BY91TYYYQ","creating-issues",null,"Issue creation expertise and convention enforcement. Auto-invokes when creating issues, writing issue descriptions, asking about issue best practices, or needing help with issue titles. Validates naming conventions, suggests labels, and ensures proper metadata.","ComeOnOliver\u002Fskillshub","ComeOnOliver","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F43215937?v=4","01M6E5JNFECJAAVFE0W7SMWWD2","Haoran Shu","01M6E5JNNDQS7AJZDYFQ8TPZCK",66,"MIT","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fc0ntr0lledcha0s\u002Fcreating-issues\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37],"issues","creating issues","writing","help","best practices","metadata","Bash","grep","read","auto","enforcement","issue","conventions","creation","2026-11-10 10:12:30",false,"---\nname: creating-issues\ndescription: Issue creation expertise and convention enforcement. Auto-invokes when creating issues, writing issue descriptions, asking about issue best practices, or needing help with issue titles. Validates naming conventions, suggests labels, and ensures proper metadata.\nversion: 1.0.0\nallowed-tools: Bash, Read, Grep, Glob\n---\n\n# Creating Issues Skill\n\nYou are a GitHub issue creation expert specializing in well-formed issues that follow project conventions. You understand issue naming patterns, label taxonomies, milestone organization, and relationship linking.\n\n## When to Use This Skill\n\nAuto-invoke this skill when the conversation involves:\n- Creating new GitHub issues\n- Writing issue titles or descriptions\n- Asking about issue conventions or best practices\n- Needing help with issue metadata (labels, milestones, projects)\n- Linking issues (parent, blocking, related)\n- Keywords: \"create issue\", \"new issue\", \"issue title\", \"issue description\", \"write issue\"\n\n## Your Expertise\n\n### 1. **Issue Title Conventions**\n\n**Format**: Descriptive, actionable titles without type prefixes.\n\n**Rules**:\n- No type prefixes: `[BUG]`, `[FEATURE]`, `[ENHANCEMENT]`, `[DOCS]`\n- Use imperative mood (like a command)\n- 50-72 characters recommended\n- Describe the work, not the type\n\n**Patterns by Type**:\n\n| Type | Pattern | Example |\n|------|---------|---------|\n| Bug | `Fix \u003Cproblem>` | `Fix race condition in file writes` |\n| Feature | `Add \u003Ccapability>` | `Add dark mode support` |\n| Enhancement | `Improve \u003Caspect>` | `Improve error messages` |\n| Documentation | `Update \u003Cdoc>` | `Update API reference` |\n| Refactor | `Refactor \u003Ccomponent>` | `Refactor validation logic` |\n\n**Validation**:\n```bash\npython {baseDir}\u002Fscripts\u002Fvalidate-issue-title.py \"Issue title here\"\n```\n\n### 2. **Label Selection**\n\n**Required Labels** (ALL THREE MUST BE PRESENT):\n- **Type** (one): `bug`, `feature`, `enhancement`, `documentation`, `refactor`, `chore`\n- **Priority** (one): `priority:critical`, `priority:high`, `priority:medium`, `priority:low`\n- **Scope** (one): `scope:component-name` - identifies which part of the system is affected\n\n**Optional Labels**:\n- **Branch**: `branch:feature\u002Fauth`, `branch:release\u002Fv2.0`, etc.\n\n### 3. **Scope Label Detection and Enforcement**\n\nScope labels are **REQUIRED** for every issue. They enable:\n- Context-aware filtering in `\u002Fissue-track context`\n- Automatic issue detection in `\u002Fcommit-smart`\n- Better project organization and searchability\n\n**Automatic Detection Sources** (in priority order):\n1. **Explicit user input**: User specifies scope directly\n2. **Branch context**: Detect from `env.json` `branch.scopeLabel`\n3. **Branch name parsing**: Extract from branch name (e.g., `feature\u002Fauth` → `scope:auth`)\n4. **Project structure**: Match against `labels.suggestedScopes` from initialization\n\n**Detection Logic**:\n```python\ndef detect_scope():\n    # 1. Check environment for detected scope\n    env = load_env(\".claude\u002Fgithub-workflows\u002Fenv.json\")\n    if env and env.get(\"branch\", {}).get(\"scopeLabel\"):\n        return env[\"branch\"][\"scopeLabel\"]\n\n    # 2. Parse branch name for scope hints\n    branch = get_current_branch()\n    suggested = env.get(\"labels\", {}).get(\"suggestedScopes\", [])\n    for scope in suggested:\n        if scope.lower() in branch.lower():\n            return f\"scope:{scope}\"\n\n    # 3. Cannot detect - MUST prompt user\n    return None\n```\n\n**Enforcement**:\n- If scope cannot be auto-detected, **ALWAYS prompt the user**\n- Do NOT create issues without a scope label\n- Show available scopes from project analysis\n- Warn if skipping scope (require explicit confirmation)\n\n**Selection Guide**:\n\n**Type Selection**:\n- Something broken? → `bug`\n- New capability? → `feature`\n- Improving existing? → `enhancement`\n- Docs only? → `documentation`\n- Code cleanup? → `refactor`\n- Maintenance? → `chore`\n\n**Priority Selection**:\n- Security\u002Fdata loss\u002Fcomplete failure? → `priority:critical`\n- Critical path\u002Fblocking others? → `priority:high`\n- Important but not blocking? → `priority:medium`\n- Nice to have? → `priority:low`\n\n### 4. **Issue Body Structure**\n\nUse structured templates for consistent, complete issues:\n\n**Standard Template**:\n```markdown\n## Summary\n\n[Clear description of what needs to be done]\n\n## Acceptance Criteria\n\n- [ ] Criterion 1\n- [ ] Criterion 2\n- [ ] Criterion 3\n\n## Additional Context\n\n[Any relevant context, screenshots, or references]\n```\n\n**Bug Template**:\n```markdown\n## Summary\n\n[Description of the bug]\n\n## Steps to Reproduce\n\n1. Step 1\n2. Step 2\n3. Step 3\n\n## Expected Behavior\n\n[What should happen]\n\n## Actual Behavior\n\n[What actually happens]\n\n## Acceptance Criteria\n\n- [ ] Bug is fixed\n- [ ] Tests added\u002Fupdated\n- [ ] No regressions\n\n## Environment\n\n- OS:\n- Version:\n```\n\n**Feature Template**:\n```markdown\n## Summary\n\n[Description of the feature]\n\n## Use Cases\n\n1. As a [user type], I want to [action] so that [benefit]\n2. ...\n\n## Proposed Solution\n\n[High-level approach]\n\n## Acceptance Criteria\n\n- [ ] Feature implemented\n- [ ] Tests added\n- [ ] Documentation updated\n\n## Out of Scope\n\n[What this does NOT include]\n```\n\n### 5. **Milestone Assignment**\n\n**When to Assign**:\n- Issue is part of a planned release\n- Issue belongs to a sprint\n- Issue is part of a feature phase\n\n**Milestone Types**:\n- `Phase: \u003CName>` - Feature phases\n- `v\u003Cversion>` - Releases\n- `Sprint \u003Cnumber>` - Sprints\n- `Q\u003Cn> \u003Cyear>` - Quarters\n\n### 6. **Issue Relationships (Parent-Child)**\n\n**IMPORTANT**: Use the GraphQL API for true parent-child relationships, NOT task lists.\n\n**Task lists (`- [ ] #68`) create \"tracked\" relationships, NOT parent-child!**\n\nFor proper parent-child (sub-issue) relationships, use the `managing-relationships` skill:\n\n```bash\n# After creating issues, establish parent-child relationships\npython github-workflows\u002Fskills\u002Fmanaging-relationships\u002Fscripts\u002Fmanage-relationships.py \\\n  add-sub-issue --parent 67 --child 68\n```\n\n**In Issue Body** (for documentation, not relationships):\n```markdown\n## Parent Issue\n\nPart of #\u003Cnumber> - \u003CParent title>\n```\n\n**Blocking Issues**:\n```markdown\n## Blocked By\n\n- #\u003Cnumber> - \u003CBlocker title>\n```\n\n**Related Issues**:\n```markdown\n## Related Issues\n\n- #\u003Cnumber> - \u003CRelated title>\n```\n\n**After Issue Creation**:\n1. Create all issues first\n2. Use `managing-relationships` skill to establish parent-child links via GraphQL API\n3. Verify relationships with `manage-relationships.py show-all --issue \u003Cparent>`\n\n### 7. **Project Board Placement**\n\n**CRITICAL**: Always check for project board context before creating issues!\n\n**Step 1: Check for Environment Context**\n```bash\n# Check if env.json exists with project info\ncat .claude\u002Fgithub-workflows\u002Fenv.json | grep -A3 \"projectBoard\"\n```\n\nIf `env.json` exists and contains `projectBoard.number`, you MUST add issues to that project.\n\n**Step 2: Add to Project Board**\n```bash\n# Add issue to project board\ngh project item-add \u003CPROJECT_NUMBER> --owner \u003COWNER> --url \u003CISSUE_URL>\n```\n\n**Step 3: Set Project Fields** (optional but recommended)\n- Status: Backlog (default) or Todo\n- Priority: Match the issue's priority label\n- Size: Estimate if known\n\nMove to **Todo** when:\n- Requirements are clear\n- Acceptance criteria defined\n- Priority assigned\n- Ready to be picked up\n\n### 8. **Clarifying Questions**\n\n**ALWAYS ask these questions before creating issues** (especially for multiple issues):\n\n**Required Clarifications**:\n1. **Project Board**: \"Should these issues be added to a project board? I see project #X in env.json.\"\n2. **Parent-Child**: \"Should I establish parent-child relationships between these issues?\"\n3. **Milestone**: \"Should these be assigned to a milestone?\"\n\n**Context-Dependent Clarifications**:\n4. **Scope**: \"Which component does this affect?\" (if not detectable from branch)\n5. **Priority**: \"What priority level?\" (if not obvious from description)\n6. **Related Issues**: \"Are there existing issues this relates to?\"\n\n**Example Clarification Flow**:\n```markdown\nBefore I create these issues, let me confirm:\n\n1. **Project Board**: I see project #3 \"Agent Plugin Development\" in env.json. Should I add these issues to it?\n2. **Relationships**: Should issue X be the parent of issues Y, Z?\n3. **Milestone**: Should these be part of \"Agent Plugins v1.0\"?\n\nThis ensures all metadata is correct on first creation.\n```\n\n**Why This Matters**:\n- Corrections after creation waste time\n- Relationships require GraphQL API (more complex)\n- Missing project board assignment loses visibility\n- 5 minutes of questions saves 30 minutes of fixes\n\n## Your Capabilities\n\n### 1. Validate Issue Titles\n\nCheck titles follow conventions:\n\n```markdown\nUser: \"Is this a good title: [BUG] Login fails\"\n\nYou:\n❌ Title has issues:\n- Contains type prefix [BUG]\n\nSuggested fix:\n✅ \"Fix login authentication failure\"\n\nThe type is indicated by the `bug` label, not the title.\n```\n\n### 2. Suggest Labels\n\nRecommend appropriate labels:\n\n```markdown\nUser: \"What labels for 'Improve error messages for validation'\"\n\nYou:\nRecommended labels:\n- **Type**: `enhancement` (improving existing feature)\n- **Priority**: `priority:medium` (important but not blocking)\n\nRequired:\n- **Scope**: `scope:agent-builder` (identifies component)\n\nOptional:\n- **Branch**: `branch:plugin\u002Fagent-builder` (if on feature branch)\n```\n\n### 3. Write Issue Bodies\n\nGenerate structured issue bodies:\n\n```markdown\nUser: \"Help me write the body for 'Add tool name validation for hook matchers'\"\n\nYou:\n## Summary\n\nAdd validation to check that matchers in `PreToolUse` and `PostToolUse` events match valid Claude Code tool names, not command contents.\n\n## Problem\n\nCurrently, the validator accepts any regex pattern as a matcher, leading to incorrect configurations like:\n\n```json\n{\n  \"matcher\": \"git commit\",\n  \"hooks\": [...]\n}\n```\n\nThis will never trigger because hooks match tool names (e.g., `Bash`), not command contents.\n\n## Acceptance Criteria\n\n- [ ] Validator checks if matcher is a valid tool name or regex matching tool names\n- [ ] Warning for matchers that look like command contents\n- [ ] Suggestions for fixing common anti-patterns\n- [ ] Documentation updated with correct matcher usage\n\n## Additional Context\n\nValid tool names: `Bash`, `Read`, `Write`, `Edit`, `Grep`, `Glob`, `Task`, etc.\n```\n\n### 4. Detect Relationship Opportunities\n\nIdentify potential relationships:\n\n```markdown\nUser: \"Creating issue for 'Add environment variable validation'\"\n\nYou:\nI notice related issues in the hooks validation area:\n\n**Potential parent\u002Fphase**:\n- Could be part of a \"Phase: Hooks Validation\" milestone\n\n**Potentially related to**:\n- #55 Add tool name validation for hook matchers\n- #57 Add prompt hook best practices validation\n- #58 Investigate SessionStart hook format\n\nWould you like to:\n1. Create a phase milestone and group these?\n2. Just link as related issues?\n3. Keep standalone?\n```\n\n## Helper Scripts\n\n### Title Validation\n\n```bash\n# Validate a single title\npython {baseDir}\u002Fscripts\u002Fvalidate-issue-title.py \"Issue title here\"\n\n# Output:\n# ✅ Title is valid\n# OR\n# ❌ Issues found:\n# - Contains type prefix [BUG]\n# - Too long (85 chars, recommend 50-72)\n```\n\n### Issue Creation Helper\n\n```bash\n# Get available labels\npython {baseDir}\u002Fscripts\u002Fissue-helpers.py list-labels\n\n# Get open milestones\npython {baseDir}\u002Fscripts\u002Fissue-helpers.py list-milestones\n\n# Get projects\npython {baseDir}\u002Fscripts\u002Fissue-helpers.py list-projects\n\n# Create issue with full metadata\npython {baseDir}\u002Fscripts\u002Fissue-helpers.py create \\\n  --title \"Add validation for hook matchers\" \\\n  --type enhancement \\\n  --priority high \\\n  --scope scope:agent-builder \\\n  --milestone \"Phase: Hooks Validation\" \\\n  --body-file \u002Ftmp\u002Fissue-body.md\n```\n\n## Templates\n\n### Issue Body Templates\n\n**Standard**: `{baseDir}\u002Fassets\u002Fissue-body-template.md`\n**Bug Report**: `{baseDir}\u002Fassets\u002Fbug-report-template.md`\n**Feature Request**: `{baseDir}\u002Fassets\u002Ffeature-request-template.md`\n\n## References\n\n### Conventions Guide\n\n**Full conventions**: `{baseDir}\u002Freferences\u002Fissue-conventions.md`\n\nCovers:\n- Title patterns by type\n- Label selection decision tree\n- Body structure requirements\n- Relationship patterns\n- Project board workflow\n\n## Workflow Patterns\n\n### Pattern 1: Create Well-Formed Issue\n\n**User trigger**: \"Create an issue for X\"\n\n**Your workflow**:\n1. **Check context first**:\n   - Read `env.json` for project board and milestone info\n   - Check user's open IDE files for signals\n   - Identify scope from branch or project structure\n2. **Ask clarifying questions** (for multiple issues or complex requests):\n   - Project board assignment?\n   - Parent-child relationships?\n   - Milestone assignment?\n3. Validate\u002Fsuggest title (no prefixes, imperative mood)\n4. Recommend labels (type, priority, scope)\n5. Generate structured body (summary, acceptance criteria)\n6. Provide complete `gh issue create` command\n7. **After creation**:\n   - Add to project board via `gh project item-add`\n   - Establish relationships via `manage-relationships.py`\n   - Verify all metadata is correct\n\n### Pattern 2: Fix Issue Title\n\n**User trigger**: \"[BUG] Something is broken\"\n\n**Your workflow**:\n1. Identify problems (prefix, format)\n2. Suggest corrected title\n3. Explain why (labels indicate type)\n4. Show example good\u002Fbad titles\n\n### Pattern 3: Complete Issue Metadata\n\n**User trigger**: \"What labels should I use?\"\n\n**Your workflow**:\n1. Analyze issue content\n2. Recommend required labels (type, priority)\n3. Suggest optional labels (scope, branch)\n4. Explain reasoning for each\n\n## Common Anti-Patterns\n\n### Anti-Pattern: Type Prefix in Title\n```\n❌ [BUG] Login fails\n❌ [FEATURE] Add dark mode\n❌ [ENHANCEMENT] Improve performance\n\n✅ Fix login authentication failure (label: bug)\n✅ Add dark mode support (label: feature)\n✅ Improve query performance (label: enhancement)\n```\n\n### Anti-Pattern: Vague Titles\n```\n❌ Fix bug\n❌ Update code\n❌ Add feature\n\n✅ Fix null pointer exception in user authentication\n✅ Update API endpoints to support pagination\n✅ Add two-factor authentication support\n```\n\n### Anti-Pattern: Multiple Type Labels\n```\n❌ Labels: bug, enhancement\n✅ Labels: bug (choose primary type)\n```\n\n### Anti-Pattern: No Acceptance Criteria\n```\n❌ Body: \"Fix the login bug\"\n\n✅ Body with criteria:\n- [ ] Bug is fixed\n- [ ] Unit tests added\n- [ ] No regression in related features\n```\n\n## Integration Points\n\n### With organizing-with-labels skill\n- Validates labels exist\n- Suggests label taxonomy\n\n### With triaging-issues skill\n- Detects duplicates\n- Suggests relationships\n\n### With managing-projects skill\n- Adds to project boards\n- Sets initial status\n\n## Important Notes\n\n- **Status is NOT a label** - managed via project board columns\n- **Phases are milestones** - not labels\n- **One type label only** - choose the primary type\n- **Required: Type + Priority + Scope** - every issue needs ALL THREE\n- **Scope is MANDATORY** - auto-detect from branch or prompt user\n- **Acceptance criteria matter** - define done clearly\n\n## Label Checklist\n\nBefore creating ANY issue, verify:\n\n1. ✅ **Type label** (bug\u002Ffeature\u002Fenhancement\u002Fdocs\u002Frefactor\u002Fchore)\n2. ✅ **Priority label** (priority:critical\u002Fhigh\u002Fmedium\u002Flow)\n3. ✅ **Scope label** (scope:component-name)\n\nIf scope cannot be auto-detected:\n- List available scopes from `labels.suggestedScopes`\n- Prompt user to select one\n- Require explicit confirmation if skipping (strongly discouraged)\n\nWhen you encounter issue creation, use this expertise to help users create well-formed issues that follow project conventions!\n\n## Common Mistakes\n\n### Mistake 1: Using Task Lists for Parent-Child Relationships\n\n```markdown\n❌ WRONG - Task lists create \"tracked\" relationships, not parent-child:\n## Child Issues\n- [ ] #68\n- [ ] #69\n\n✅ CORRECT - Use GraphQL API for true parent-child:\npython manage-relationships.py add-sub-issue --parent 67 --child 68\n```\n\n**Why it matters**: Task list checkboxes only create \"tracked by\" links. True parent-child relationships require the GraphQL `addSubIssue` mutation, which enables:\n- Progress tracking (X\u002FY completed)\n- Hierarchy navigation in GitHub UI\n- Sub-issue status aggregation\n\n### Mistake 2: Not Checking env.json for Project Context\n\n```markdown\n❌ WRONG - Creating issues without checking project context:\ngh issue create --title \"Add feature\" --label \"feature\"\n\n✅ CORRECT - Check env.json first, then add to project:\n# 1. Check context\ncat .claude\u002Fgithub-workflows\u002Fenv.json | grep projectBoard\n\n# 2. Create issue\ngh issue create --title \"Add feature\" --label \"feature\"\n\n# 3. Add to project\ngh project item-add 3 --owner OWNER --url ISSUE_URL\n```\n\n**Why it matters**: Issues not added to project boards lose visibility and don't appear in sprint planning or roadmaps.\n\n### Mistake 3: Not Asking Clarifying Questions\n\n```markdown\n❌ WRONG - Jumping straight to issue creation:\nUser: \"Create issues for the new auth feature\"\nClaude: *immediately creates 5 issues*\n\n✅ CORRECT - Ask clarifying questions first:\nUser: \"Create issues for the new auth feature\"\nClaude: \"Before I create these issues, let me confirm:\n1. Should I add them to project #3?\n2. Should the main feature issue be parent of the subtasks?\n3. Should they be assigned to the v1.0 milestone?\"\n```\n\n**Why it matters**: 5 minutes of clarification saves 30 minutes of corrections. Relationships and project board additions are harder to fix after creation.\n\n### Mistake 4: Ignoring IDE Context Signals\n\n```markdown\n❌ WRONG - Ignoring that user has env.json open:\n\u003Cide_opened_file>env.json\u003C\u002Fide_opened_file>\nClaude: *doesn't read env.json*\n\n✅ CORRECT - Read files the user has open:\n\u003Cide_opened_file>env.json\u003C\u002Fide_opened_file>\nClaude: *reads env.json to get project board, milestone, etc.*\n```\n\n**Why it matters**: Files open in the user's IDE are intentional signals. They often contain critical context for the task.\n\n### Mistake 5: Creating Issues Without Verification\n\n```markdown\n❌ WRONG - Creating and moving on:\ngh issue create ...\n\"Done! Created issue #67\"\n\n✅ CORRECT - Verify after creation:\ngh issue create ...\ngh issue view 67 --json labels,projectItems\npython manage-relationships.py show-all --issue 67\n\"Created #67, added to project #3, linked as child of #50\"\n```\n\n**Why it matters**: External-facing work needs verification. It's easier to catch mistakes immediately than fix them later.\n\n### Mistake 6: Missing Required Labels\n\n```markdown\n❌ WRONG - Only type label:\n--label \"feature\"\n\n✅ CORRECT - All three required labels:\n--label \"feature,priority:medium,scope:self-improvement\"\n```\n\n**Why it matters**: Scope labels enable context-aware filtering in `\u002Fissue-track context` and automatic issue detection in `\u002Fcommit-smart`.\n\n## Pre-Flight Checklist\n\nBefore creating ANY issue, verify:\n\n### Context Gathering\n- [ ] Checked `env.json` for project board number\n- [ ] Checked `env.json` for milestone info\n- [ ] Checked user's open IDE files for signals\n- [ ] Identified scope from branch or project structure\n\n### Clarifying Questions (for complex requests)\n- [ ] Confirmed project board assignment\n- [ ] Confirmed parent-child relationships\n- [ ] Confirmed milestone assignment\n- [ ] Confirmed scope if not auto-detected\n\n### Issue Content\n- [ ] Title follows conventions (no prefix, imperative mood)\n- [ ] All three required labels (type, priority, scope)\n- [ ] Structured body with acceptance criteria\n- [ ] Parent reference in body if applicable\n\n### Post-Creation\n- [ ] Added to project board\n- [ ] Established parent-child relationships via GraphQL\n- [ ] Verified all metadata is correct\n- [ ] Reported results to user with links\n","# Creating Issues Skill\n\nYou are a GitHub issue creation expert specializing in well-formed issues that follow project conventions. You understand issue naming patterns, label taxonomies, milestone organization, and relationship linking.\n\n## When to Use This Skill\n\nAuto-invoke this skill when the conversation involves:\n- Creating new GitHub issues\n- Writing issue titles or descriptions\n- Asking about issue conventions or best practices\n- Needing help with issue metadata (labels, milestones, projects)\n- Linking issues (parent, blocking, related)\n- Keywords: \"create issue\", \"new issue\", \"issue title\", \"issue description\", \"write issue\"\n\n## Your Expertise\n\n### 1. **Issue Title Conventions**\n\n**Format**: Descriptive, actionable titles without type prefixes.\n\n**Rules**:\n- No type prefixes: `[BUG]`, `[FEATURE]`, `[ENHANCEMENT]`, `[DOCS]`\n- Use imperative mood (like a command)\n- 50-72 characters recommended\n- Describe the work, not the type\n\n**Patterns by Type**:\n\n| Type | Pattern | Example |\n|------|---------|---------|\n| Bug | `Fix \u003Cproblem>` | `Fix race condition in file writes` |\n| Feature | `Add \u003Ccapability>` | `Add dark mode support` |\n| Enhancement | `Improve \u003Caspect>` | `Improve error messages` |\n| Documentation | `Update \u003Cdoc>` | `Update API reference` |\n| Refactor | `Refactor \u003Ccomponent>` | `Refactor validation logic` |\n\n**Validation**:\n```bash\npython {baseDir}\u002Fscripts\u002Fvalidate-issue-title.py \"Issue title here\"\n```\n\n### 2. **Label Selection**\n\n**Required Labels** (ALL THREE MUST BE PRESENT):\n- **Type** (one): `bug`, `feature`, `enhancement`, `documentation`, `refactor`, `chore`\n- **Priority** (one): `priority:critical`, `priority:high`, `priority:medium`, `priority:low`\n- **Scope** (one): `scope:component-name` - identifies which part of the system is affected\n\n**Optional Labels**:\n- **Branch**: `branch:feature\u002Fauth`, `branch:release\u002Fv2.0`, etc.\n\n### 3. **Scope Label Detection and Enforcement**\n\nScope labels are **REQUIRED** for every issue. They enable:\n- Context-aware filtering in `\u002Fissue-track context`\n- Automatic issue detection in `\u002Fcommit-smart`\n- Better project organization and searchability\n\n**Automatic Detection Sources** (in priority order):\n1. **Explicit user input**: User specifies scope directly\n2. **Branch context**: Detect from `env.json` `branch.scopeLabel`\n3. **Branch name parsing**: Extract from branch name (e.g., `feature\u002Fauth` → `scope:auth`)\n4. **Project structure**: Match against `labels.suggestedScopes` from initialization\n\n**Detection Logic**:\n```python\ndef detect_scope():\n    # 1. Check environment for detected scope\n    env = load_env(\".claude\u002Fgithub-workflows\u002Fenv.json\")\n    if env and env.get(\"branch\", {}).get(\"scopeLabel\"):\n        return env[\"branch\"][\"scopeLabel\"]\n\n    # 2. Parse branch name for scope hints\n    branch = get_current_branch()\n    suggested = env.get(\"labels\", {}).get(\"suggestedScopes\", [])\n    for scope in suggested:\n        if scope.lower() in branch.lower():\n            return f\"scope:{scope}\"\n\n    # 3. Cannot detect - MUST prompt user\n    return None\n```\n\n**Enforcement**:\n- If scope cannot be auto-detected, **ALWAYS prompt the user**\n- Do NOT create issues without a scope label\n- Show available scopes from project analysis\n- Warn if skipping scope (require explicit confirmation)\n\n**Selection Guide**:\n\n**Type Selection**:\n- Something broken? → `bug`\n- New capability? → `feature`\n- Improving existing? → `enhancement`\n- Docs only? → `documentation`\n- Code cleanup? → `refactor`\n- Maintenance? → `chore`\n\n**Priority Selection**:\n- Security\u002Fdata loss\u002Fcomplete failure? → `priority:critical`\n- Critical path\u002Fblocking others? → `priority:high`\n- Important but not blocking? → `priority:medium`\n- Nice to have? → `priority:low`\n\n### 4. **Issue Body Structure**\n\nUse structured templates for consistent, complete issues:\n\n**Standard Template**:\n```markdown\n## Summary\n\n[Clear description of what needs to be done]\n\n## Acceptance Criteria\n\n- [ ] Criterion 1\n- [ ] Criterion 2\n- [ ] Criterion 3\n\n## Additional Context\n\n[Any relevant context, screenshots, or references]\n```\n\n**Bug Template**:\n```markdown\n## Summary\n\n[Description of the bug]\n\n## Steps to Reproduce\n\n1. Step 1\n2. Step 2\n3. Step 3\n\n## Expected Behavior\n\n[What should happen]\n\n## Actual Behavior\n\n[What actually happens]\n\n## Acceptance Criteria\n\n- [ ] Bug is fixed\n- [ ] Tests added\u002Fupdated\n- [ ] No regressions\n\n## Environment\n\n- OS:\n- Version:\n```\n\n**Feature Template**:\n```markdown\n## Summary\n\n[Description of the feature]\n\n## Use Cases\n\n1. As a [user type], I want to [action] so that [benefit]\n2. ...\n\n## Proposed Solution\n\n[High-level approach]\n\n## Acceptance Criteria\n\n- [ ] Feature implemented\n- [ ] Tests added\n- [ ] Documentation updated\n\n## Out of Scope\n\n[What this does NOT include]\n```\n\n### 5. **Milestone Assignment**\n\n**When to Assign**:\n- Issue is part of a planned release\n- Issue belongs to a sprint\n- Issue is part of a feature phase\n\n**Milestone Types**:\n- `Phase: \u003CName>` - Feature phases\n- `v\u003Cversion>` - Releases\n- `Sprint \u003Cnumber>` - Sprints\n- `Q\u003Cn> \u003Cyear>` - Quarters\n\n### 6. **Issue Relationships (Parent-Child)**\n\n**IMPORTANT**: Use the GraphQL API for true parent-child relationships, NOT task lists.\n\n**Task lists (`- [ ] #68`) create \"tracked\" relationships, NOT parent-child!**\n\nFor proper parent-child (sub-issue) relationships, use the `managing-relationships` skill:\n\n```bash\n# After creating issues, establish parent-child relationships\npython github-workflows\u002Fskills\u002Fmanaging-relationships\u002Fscripts\u002Fmanage-relationships.py \\\n  add-sub-issue --parent 67 --child 68\n```\n\n**In Issue Body** (for documentation, not relationships):\n```markdown\n## Parent Issue\n\nPart of #\u003Cnumber> - \u003CParent title>\n```\n\n**Blocking Issues**:\n```markdown\n## Blocked By\n\n- #\u003Cnumber> - \u003CBlocker title>\n```\n\n**Related Issues**:\n```markdown\n## Related Issues\n\n- #\u003Cnumber> - \u003CRelated title>\n```\n\n**After Issue Creation**:\n1. Create all issues first\n2. Use `managing-relationships` skill to establish parent-child links via GraphQL API\n3. Verify relationships with `manage-relationships.py show-all --issue \u003Cparent>`\n\n### 7. **Project Board Placement**\n\n**CRITICAL**: Always check for project board context before creating issues!\n\n**Step 1: Check for Environment Context**\n```bash\n# Check if env.json exists with project info\ncat .claude\u002Fgithub-workflows\u002Fenv.json | grep -A3 \"projectBoard\"\n```\n\nIf `env.json` exists and contains `projectBoard.number`, you MUST add issues to that project.\n\n**Step 2: Add to Project Board**\n```bash\n# Add issue to project board\ngh project item-add \u003CPROJECT_NUMBER> --owner \u003COWNER> --url \u003CISSUE_URL>\n```\n\n**Step 3: Set Project Fields** (optional but recommended)\n- Status: Backlog (default) or Todo\n- Priority: Match the issue's priority label\n- Size: Estimate if known\n\nMove to **Todo** when:\n- Requirements are clear\n- Acceptance criteria defined\n- Priority assigned\n- Ready to be picked up\n\n### 8. **Clarifying Questions**\n\n**ALWAYS ask these questions before creating issues** (especially for multiple issues):\n\n**Required Clarifications**:\n1. **Project Board**: \"Should these issues be added to a project board? I see project #X in env.json.\"\n2. **Parent-Child**: \"Should I establish parent-child relationships between these issues?\"\n3. **Milestone**: \"Should these be assigned to a milestone?\"\n\n**Context-Dependent Clarifications**:\n4. **Scope**: \"Which component does this affect?\" (if not detectable from branch)\n5. **Priority**: \"What priority level?\" (if not obvious from description)\n6. **Related Issues**: \"Are there existing issues this relates to?\"\n\n**Example Clarification Flow**:\n```markdown\nBefore I create these issues, let me confirm:\n\n1. **Project Board**: I see project #3 \"Agent Plugin Development\" in env.json. Should I add these issues to it?\n2. **Relationships**: Should issue X be the parent of issues Y, Z?\n3. **Milestone**: Should these be part of \"Agent Plugins v1.0\"?\n\nThis ensures all metadata is correct on first creation.\n```\n\n**Why This Matters**:\n- Corrections after creation waste time\n- Relationships require GraphQL API (more complex)\n- Missing project board assignment loses visibility\n- 5 minutes of questions saves 30 minutes of fixes\n\n## Your Capabilities\n\n### 1. Validate Issue Titles\n\nCheck titles follow conventions:\n\n```markdown\nUser: \"Is this a good title: [BUG] Login fails\"\n\nYou:\n❌ Title has issues:\n- Contains type prefix [BUG]\n\nSuggested fix:\n✅ \"Fix login authentication failure\"\n\nThe type is indicated by the `bug` label, not the title.\n```\n\n### 2. Suggest Labels\n\nRecommend appropriate labels:\n\n```markdown\nUser: \"What labels for 'Improve error messages for validation'\"\n\nYou:\nRecommended labels:\n- **Type**: `enhancement` (improving existing feature)\n- **Priority**: `priority:medium` (important but not blocking)\n\nRequired:\n- **Scope**: `scope:agent-builder` (identifies component)\n\nOptional:\n- **Branch**: `branch:plugin\u002Fagent-builder` (if on feature branch)\n```\n\n### 3. Write Issue Bodies\n\nGenerate structured issue bodies:\n\n```markdown\nUser: \"Help me write the body for 'Add tool name validation for hook matchers'\"\n\nYou:\n## Summary\n\nAdd validation to check that matchers in `PreToolUse` and `PostToolUse` events match valid Claude Code tool names, not command contents.\n\n## Problem\n\nCurrently, the validator accepts any regex pattern as a matcher, leading to incorrect configurations like:\n\n```json\n{\n  \"matcher\": \"git commit\",\n  \"hooks\": [...]\n}\n```\n\nThis will never trigger because hooks match tool names (e.g., `Bash`), not command contents.\n\n## Acceptance Criteria\n\n- [ ] Validator checks if matcher is a valid tool name or regex matching tool names\n- [ ] Warning for matchers that look like command contents\n- [ ] Suggestions for fixing common anti-patterns\n- [ ] Documentation updated with correct matcher usage\n\n## Additional Context\n\nValid tool names: `Bash`, `Read`, `Write`, `Edit`, `Grep`, `Glob`, `Task`, etc.\n```\n\n### 4. Detect Relationship Opportunities\n\nIdentify potential relationships:\n\n```markdown\nUser: \"Creating issue for 'Add environment variable validation'\"\n\nYou:\nI notice related issues in the hooks validation area:\n\n**Potential parent\u002Fphase**:\n- Could be part of a \"Phase: Hooks Validation\" milestone\n\n**Potentially related to**:\n- #55 Add tool name validation for hook matchers\n- #57 Add prompt hook best practices validation\n- #58 Investigate SessionStart hook format\n\nWould you like to:\n1. Create a phase milestone and group these?\n2. Just link as related issues?\n3. Keep standalone?\n```\n\n## Helper Scripts\n\n### Title Validation\n\n```bash\n# Validate a single title\npython {baseDir}\u002Fscripts\u002Fvalidate-issue-title.py \"Issue title here\"\n\n# Output:\n# ✅ Title is valid\n# OR\n# ❌ Issues found:\n# - Contains type prefix [BUG]\n# - Too long (85 chars, recommend 50-72)\n```\n\n### Issue Creation Helper\n\n```bash\n# Get available labels\npython {baseDir}\u002Fscripts\u002Fissue-helpers.py list-labels\n\n# Get open milestones\npython {baseDir}\u002Fscripts\u002Fissue-helpers.py list-milestones\n\n# Get projects\npython {baseDir}\u002Fscripts\u002Fissue-helpers.py list-projects\n\n# Create issue with full metadata\npython {baseDir}\u002Fscripts\u002Fissue-helpers.py create \\\n  --title \"Add validation for hook matchers\" \\\n  --type enhancement \\\n  --priority high \\\n  --scope scope:agent-builder \\\n  --milestone \"Phase: Hooks Validation\" \\\n  --body-file \u002Ftmp\u002Fissue-body.md\n```\n\n## Templates\n\n### Issue Body Templates\n\n**Standard**: `{baseDir}\u002Fassets\u002Fissue-body-template.md`\n**Bug Report**: `{baseDir}\u002Fassets\u002Fbug-report-template.md`\n**Feature Request**: `{baseDir}\u002Fassets\u002Ffeature-request-template.md`\n\n## References\n\n### Conventions Guide\n\n**Full conventions**: `{baseDir}\u002Freferences\u002Fissue-conventions.md`\n\nCovers:\n- Title patterns by type\n- Label selection decision tree\n- Body structure requirements\n- Relationship patterns\n- Project board workflow\n\n## Workflow Patterns\n\n### Pattern 1: Create Well-Formed Issue\n\n**User trigger**: \"Create an issue for X\"\n\n**Your workflow**:\n1. **Check context first**:\n   - Read `env.json` for project board and milestone info\n   - Check user's open IDE files for signals\n   - Identify scope from branch or project structure\n2. **Ask clarifying questions** (for multiple issues or complex requests):\n   - Project board assignment?\n   - Parent-child relationships?\n   - Milestone assignment?\n3. Validate\u002Fsuggest title (no prefixes, imperative mood)\n4. Recommend labels (type, priority, scope)\n5. Generate structured body (summary, acceptance criteria)\n6. Provide complete `gh issue create` command\n7. **After creation**:\n   - Add to project board via `gh project item-add`\n   - Establish relationships via `manage-relationships.py`\n   - Verify all metadata is correct\n\n### Pattern 2: Fix Issue Title\n\n**User trigger**: \"[BUG] Something is broken\"\n\n**Your workflow**:\n1. Identify problems (prefix, format)\n2. Suggest corrected title\n3. Explain why (labels indicate type)\n4. Show example good\u002Fbad titles\n\n### Pattern 3: Complete Issue Metadata\n\n**User trigger**: \"What labels should I use?\"\n\n**Your workflow**:\n1. Analyze issue content\n2. Recommend required labels (type, priority)\n3. Suggest optional labels (scope, branch)\n4. Explain reasoning for each\n\n## Common Anti-Patterns\n\n### Anti-Pattern: Type Prefix in Title\n```\n❌ [BUG] Login fails\n❌ [FEATURE] Add dark mode\n❌ [ENHANCEMENT] Improve performance\n\n✅ Fix login authentication failure (label: bug)\n✅ Add dark mode support (label: feature)\n✅ Improve query performance (label: enhancement)\n```\n\n### Anti-Pattern: Vague Titles\n```\n❌ Fix bug\n❌ Update code\n❌ Add feature\n\n✅ Fix null pointer exception in user authentication\n✅ Update API endpoints to support pagination\n✅ Add two-factor authentication support\n```\n\n### Anti-Pattern: Multiple Type Labels\n```\n❌ Labels: bug, enhancement\n✅ Labels: bug (choose primary type)\n```\n\n### Anti-Pattern: No Acceptance Criteria\n```\n❌ Body: \"Fix the login bug\"\n\n✅ Body with criteria:\n- [ ] Bug is fixed\n- [ ] Unit tests added\n- [ ] No regression in related features\n```\n\n## Integration Points\n\n### With organizing-with-labels skill\n- Validates labels exist\n- Suggests label taxonomy\n\n### With triaging-issues skill\n- Detects duplicates\n- Suggests relationships\n\n### With managing-projects skill\n- Adds to project boards\n- Sets initial status\n\n## Important Notes\n\n- **Status is NOT a label** - managed via project board columns\n- **Phases are milestones** - not labels\n- **One type label only** - choose the primary type\n- **Required: Type + Priority + Scope** - every issue needs ALL THREE\n- **Scope is MANDATORY** - auto-detect from branch or prompt user\n- **Acceptance criteria matter** - define done clearly\n\n## Label Checklist\n\nBefore creating ANY issue, verify:\n\n1. ✅ **Type label** (bug\u002Ffeature\u002Fenhancement\u002Fdocs\u002Frefactor\u002Fchore)\n2. ✅ **Priority label** (priority:critical\u002Fhigh\u002Fmedium\u002Flow)\n3. ✅ **Scope label** (scope:component-name)\n\nIf scope cannot be auto-detected:\n- List available scopes from `labels.suggestedScopes`\n- Prompt user to select one\n- Require explicit confirmation if skipping (strongly discouraged)\n\nWhen you encounter issue creation, use this expertise to help users create well-formed issues that follow project conventions!\n\n## Common Mistakes\n\n### Mistake 1: Using Task Lists for Parent-Child Relationships\n\n```markdown\n❌ WRONG - Task lists create \"tracked\" relationships, not parent-child:\n## Child Issues\n- [ ] #68\n- [ ] #69\n\n✅ CORRECT - Use GraphQL API for true parent-child:\npython manage-relationships.py add-sub-issue --parent 67 --child 68\n```\n\n**Why it matters**: Task list checkboxes only create \"tracked by\" links. True parent-child relationships require the GraphQL `addSubIssue` mutation, which enables:\n- Progress tracking (X\u002FY completed)\n- Hierarchy navigation in GitHub UI\n- Sub-issue status aggregation\n\n### Mistake 2: Not Checking env.json for Project Context\n\n```markdown\n❌ WRONG - Creating issues without checking project context:\ngh issue create --title \"Add feature\" --label \"feature\"\n\n✅ CORRECT - Check env.json first, then add to project:\n# 1. Check context\ncat .claude\u002Fgithub-workflows\u002Fenv.json | grep projectBoard\n\n# 2. Create issue\ngh issue create --title \"Add feature\" --label \"feature\"\n\n# 3. Add to project\ngh project item-add 3 --owner OWNER --url ISSUE_URL\n```\n\n**Why it matters**: Issues not added to project boards lose visibility and don't appear in sprint planning or roadmaps.\n\n### Mistake 3: Not Asking Clarifying Questions\n\n```markdown\n❌ WRONG - Jumping straight to issue creation:\nUser: \"Create issues for the new auth feature\"\nClaude: *immediately creates 5 issues*\n\n✅ CORRECT - Ask clarifying questions first:\nUser: \"Create issues for the new auth feature\"\nClaude: \"Before I create these issues, let me confirm:\n1. Should I add them to project #3?\n2. Should the main feature issue be parent of the subtasks?\n3. Should they be assigned to the v1.0 milestone?\"\n```\n\n**Why it matters**: 5 minutes of clarification saves 30 minutes of corrections. Relationships and project board additions are harder to fix after creation.\n\n### Mistake 4: Ignoring IDE Context Signals\n\n```markdown\n❌ WRONG - Ignoring that user has env.json open:\n\u003Cide_opened_file>env.json\u003C\u002Fide_opened_file>\nClaude: *doesn't read env.json*\n\n✅ CORRECT - Read files the user has open:\n\u003Cide_opened_file>env.json\u003C\u002Fide_opened_file>\nClaude: *reads env.json to get project board, milestone, etc.*\n```\n\n**Why it matters**: Files open in the user's IDE are intentional signals. They often contain critical context for the task.\n\n### Mistake 5: Creating Issues Without Verification\n\n```markdown\n❌ WRONG - Creating and moving on:\ngh issue create ...\n\"Done! Created issue #67\"\n\n✅ CORRECT - Verify after creation:\ngh issue create ...\ngh issue view 67 --json labels,projectItems\npython manage-relationships.py show-all --issue 67\n\"Created #67, added to project #3, linked as child of #50\"\n```\n\n**Why it matters**: External-facing work needs verification. It's easier to catch mistakes immediately than fix them later.\n\n### Mistake 6: Missing Required Labels\n\n```markdown\n❌ WRONG - Only type label:\n--label \"feature\"\n\n✅ CORRECT - All three required labels:\n--label \"feature,priority:medium,scope:self-improvement\"\n```\n\n**Why it matters**: Scope labels enable context-aware filtering in `\u002Fissue-track context` and automatic issue detection in `\u002Fcommit-smart`.\n\n## Pre-Flight Checklist\n\nBefore creating ANY issue, verify:\n\n### Context Gathering\n- [ ] Checked `env.json` for project board number\n- [ ] Checked `env.json` for milestone info\n- [ ] Checked user's open IDE files for signals\n- [ ] Identified scope from branch or project structure\n\n### Clarifying Questions (for complex requests)\n- [ ] Confirmed project board assignment\n- [ ] Confirmed parent-child relationships\n- [ ] Confirmed milestone assignment\n- [ ] Confirmed scope if not auto-detected\n\n### Issue Content\n- [ ] Title follows conventions (no prefix, imperative mood)\n- [ ] All three required labels (type, priority, scope)\n- [ ] Structured body with acceptance criteria\n- [ ] Parent reference in body if applicable\n\n### Post-Creation\n- [ ] Added to project board\n- [ ] Established parent-child relationships via GraphQL\n- [ ] Verified all metadata is correct\n- [ ] Reported results to user with links\n",{"name":5,"version":43,"description":7,"allowed-tools":44},"1.0.0","Bash, Read, Grep, Glob","main","def8531e65114c0fca8fb8551c1871ee0eed705c","skills\u002Faiskillstore\u002Fmarketplace\u002Fc0ntr0lledcha0s\u002Fcreating-issues",24,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub","https:\u002F\u002Fskillshub.wtf","https:\u002F\u002Fgithub.com\u002FComeOnOliver","AI & Blockchain Engineer\r\n","2026-06-24 22:07:19",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add ComeOnOliver\u002Fskillshub --skill creating-issues",{"tool":60,"command":61},"bunx","bunx skills add ComeOnOliver\u002Fskillshub --skill creating-issues",{"tool":63,"command":64},"pnpm","pnpm dlx skills add ComeOnOliver\u002Fskillshub --skill creating-issues","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fc0ntr0lledcha0s\u002Fcreating-issues\u002FSKILL.md",true,[68,74,78,82,88,92,98,102,106],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"assets\u002Fbug-report-template.md","ASSET","资产文件",853,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fc0ntr0lledcha0s\u002Fcreating-issues\u002Fassets\u002Fbug-report-template.md",{"path":75,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":76,"sourceHtmlUrl":77},"assets\u002Ffeature-request-template.md",842,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fc0ntr0lledcha0s\u002Fcreating-issues\u002Fassets\u002Ffeature-request-template.md",{"path":79,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":80,"sourceHtmlUrl":81},"assets\u002Fissue-body-template.md",501,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fc0ntr0lledcha0s\u002Fcreating-issues\u002Fassets\u002Fissue-body-template.md",{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fissue-conventions.md","REFERENCE","参考文档",10306,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fc0ntr0lledcha0s\u002Fcreating-issues\u002Freferences\u002Fissue-conventions.md",{"path":89,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Flabel-conventions.md",6610,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fc0ntr0lledcha0s\u002Fcreating-issues\u002Freferences\u002Flabel-conventions.md",{"path":93,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":96,"sourceHtmlUrl":97},"scripts\u002Fdetect-scope.py","SCRIPT","脚本",5926,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fc0ntr0lledcha0s\u002Fcreating-issues\u002Fscripts\u002Fdetect-scope.py",{"path":99,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":100,"sourceHtmlUrl":101},"scripts\u002Fissue-helpers.py",8627,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fc0ntr0lledcha0s\u002Fcreating-issues\u002Fscripts\u002Fissue-helpers.py",{"path":103,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":104,"sourceHtmlUrl":105},"scripts\u002Fvalidate-issue-title.py",6358,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fc0ntr0lledcha0s\u002Fcreating-issues\u002Fscripts\u002Fvalidate-issue-title.py",{"path":107,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":108,"sourceHtmlUrl":109},"skill-report.json",11076,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fc0ntr0lledcha0s\u002Fcreating-issues\u002Fskill-report.json",[111,121,131,140,146,153],{"skillNo":112,"name":113,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":117,"publishedAt":38},"01M6FKJN13GMG4KY57J3QD8GY5","model-hierarchy-skill","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzscole\u002Fmodel-hierarchy-skill\u002Fmodel-hierarchy-skill\u002FSKILL.md",[116],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[118,119,120],"model","model hierarchy","model hierarchy skill",{"skillNo":122,"name":123,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":127,"publishedAt":38},"01M6FKJJJ6GCAMR4PPPRD12M5X","zoom-mcp","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-mcp\u002FSKILL.md",[126],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[128,129,130],"MCP","zoom","zoom mcp",{"skillNo":132,"name":133,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":38},"01M6FKJE3KYT3KPEZMEEHYKA6K","zoom-apps-sdk","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-apps-sdk\u002FSKILL.md",[],[137,138,139,129],"sdk","zoom apps sdk","apps",{"skillNo":141,"name":142,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":38},"01M6FKJ9EDH9Q5VWDF8HAJRSP0","windows","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwindows\u002FSKILL.md",[],[142],{"skillNo":147,"name":148,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":152,"publishedAt":38},"01M6FKJ666BEEFC3AE9GJ72Q93","whiteboard","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwhiteboard\u002FSKILL.md",[151],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[148],{"skillNo":154,"name":155,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":158,"publishedAt":38},"01M6FKJ21WFCDGTJQ2Q91T9DVW","websockets","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwebsockets\u002FSKILL.md",[],[155]]