skill-system-github
GitHub operations skill for gh CLI issue, label, template, and workflow management. Use when requests include: create issue, list issues, apply label, manage templates, check workflow, or gh operations.
What this skill does
# Skill System GitHub
Run consistent GitHub operations through `gh` with explicit safety checks for workflow writes and predictable return shapes.
## Decision Matrix
| Task Intent | Operation | Primary Backend | Notes |
|---|---|---|---|
| Create/list/comment/close/reopen issues | `manage-issues` | `gh issue` | Check duplicates before creating new issues |
| Create/update/delete labels, apply labels to issue | `manage-labels` | `gh label`, `gh issue edit` | Confirm destructive delete before execution |
| List/create pull requests | `manage-prs` | `gh pr` | Warn on force-push to main/master |
| Bootstrap/update issue templates | `manage-templates` | file read/write tools | Edit `.github/ISSUE_TEMPLATE/*` directly |
| List/check/create/update workflows | `manage-workflows` | `gh workflow`, file read/write tools | Run `safety-check` before pushing workflow changes |
| Decide workflow push path based on token scope | `safety-check` | `gh auth status`, `gh api` | Use API fallback when `workflow` scope is missing |
## Core Patterns
### Pattern 1: Resolve repository and perform issue operation
```bash
gh issue list --repo <owner/repo> --state open --limit 50
gh issue create --repo <owner/repo> --title "<title>" --body "<body>"
```
### Pattern 2: Label lifecycle and issue label application
```bash
gh label create "<name>" --repo <owner/repo> --description "<desc>" --color "<hex>"
gh label edit "<name>" --repo <owner/repo> --new-name "<new>" --description "<desc>" --color "<hex>"
gh issue edit --repo <owner/repo> <number> --add-label "<label1>,<label2>"
```
### Pattern 3: Workflow visibility and recent run checks
```bash
gh workflow list --repo <owner/repo>
gh run list --repo <owner/repo> --workflow "<name>" --limit 5
```
### Pattern 4: Workflow scope gate before writing `.github/workflows/*`
```bash
gh auth status
gh api repos/<owner>/<repo>/contents/.github/workflows/<file> \
--method PUT \
-f message="update workflow via api" \
-f content="<base64-content>" \
-f branch="<branch>"
```
## Guidelines
- Always resolve `owner/repo` first; infer from `git remote get-url origin` when not provided.
- Always check duplicate issue titles before issue creation.
- Always ask for explicit confirmation before label deletion.
- Always run `safety-check` before workflow writes that require push permissions.
- Always use file tools for `.github/ISSUE_TEMPLATE/*` and `.github/workflows/*` edits.
- Never include secrets in issue/comment/template/workflow bodies.
- Return structured output with `status`, `url`, and `error` fields for all operations.
```skill-manifest
{
"schema_version": "2.0",
"id": "skill-system-github",
"version": "1.0.0",
"capabilities": ["github-issue", "github-label", "github-template", "github-workflow", "github-pr", "github-safety"],
"effects": ["net.fetch", "proc.exec", "git.read", "fs.read", "fs.write"],
"operations": {
"manage-issues": {
"description": "Create, list, comment on, close, or reopen GitHub issues with duplicate detection before create.",
"input": {
"action": { "type": "string", "required": true, "description": "One of: create, list, comment, close, reopen" },
"repo": { "type": "string", "required": false, "description": "Target repo in owner/repo format" },
"title": { "type": "string", "required": false, "description": "Issue title for create" },
"body": { "type": "string", "required": false, "description": "Issue body for create or comment body" },
"number": { "type": "number", "required": false, "description": "Issue number for comment/close/reopen" },
"state": { "type": "string", "required": false, "description": "Issue listing state: open, closed, all" },
"limit": { "type": "number", "required": false, "description": "List limit" },
"label": { "type": "string", "required": false, "description": "Optional label filter for listing" }
},
"output": {
"description": "Operation status and issue URL when applicable.",
"fields": { "status": "string", "url": "string", "error": "string" }
},
"entrypoints": {
"agent": "scripts/manage-issues.md"
}
},
"manage-labels": {
"description": "Create, update, delete labels, and apply labels to issues in a GitHub repository.",
"input": {
"action": { "type": "string", "required": true, "description": "One of: create, update, delete, apply" },
"repo": { "type": "string", "required": false, "description": "Target repo in owner/repo format" },
"name": { "type": "string", "required": false, "description": "Label name for create/update/delete" },
"new_name": { "type": "string", "required": false, "description": "New label name for update" },
"description": { "type": "string", "required": false, "description": "Label description for create/update" },
"color": { "type": "string", "required": false, "description": "Hex color without #, for create/update" },
"number": { "type": "number", "required": false, "description": "Issue number for apply" },
"labels": { "type": "string", "required": false, "description": "Comma-separated labels for apply" },
"confirm_delete": { "type": "boolean", "required": false, "description": "Explicit confirmation for delete" }
},
"output": {
"description": "Operation status and optional resource URL.",
"fields": { "status": "string", "url": "string", "error": "string" }
},
"entrypoints": {
"agent": "scripts/manage-labels.md"
}
},
"manage-templates": {
"description": "Bootstrap and update repository issue templates under .github/ISSUE_TEMPLATE.",
"input": {
"action": { "type": "string", "required": true, "description": "One of: bootstrap, update" },
"repo": { "type": "string", "required": false, "description": "Target repo in owner/repo format" },
"template_type": { "type": "string", "required": false, "description": "Template selector: bug_report, feature_request, config" },
"content": { "type": "string", "required": false, "description": "Updated YAML content for update action" }
},
"output": {
"description": "Operation status and changed path details.",
"fields": { "status": "string", "url": "string", "error": "string" }
},
"entrypoints": {
"agent": "scripts/manage-templates.md"
}
},
"manage-workflows": {
"description": "List or check workflow runs and create/update workflow YAML files safely.",
"input": {
"action": { "type": "string", "required": true, "description": "One of: list, check, create, update" },
"repo": { "type": "string", "required": false, "description": "Target repo in owner/repo format" },
"workflow_name": { "type": "string", "required": false, "description": "Workflow display name or filename for check/update" },
"workflow_file": { "type": "string", "required": false, "description": "Workflow filename under .github/workflows" },
"content": { "type": "string", "required": false, "description": "Workflow YAML content for create/update" },
"branch": { "type": "string", "required": false, "description": "Branch for API fallback updates" }
},
"output": {
"description": "Operation status and workflow URL when available.",
"fields": { "status": "string", "url": "string", "error": "string" }
},
"entrypoints": {
"agent": "scripts/manage-workflows.md"
}
},
"manage-prs": {
"description": "List or create GitHub pull requests with branch safety checks.",
"input": {
"action": { "type": "string", "required": true, "description": "One of: list, create" },
"repo": { "type": "string", "required": false, "description": "Target repo in owner/repo format" },
"title": { "type": "string", "required": false, "Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.