creating-knowledge-entries
Create GitHub Issue knowledge entries. TRIGGERS - share knowledge, document solution, create how-to, add to knowledge base.
What this skill does
# Creating Knowledge Entries
One-shot knowledge capture with full automation.
## Trigger Detection
Activate this skill when user says:
- "I want to share knowledge"
- "Let me document this"
- "Add to knowledge base"
- "Share a tip"
- "Document this solution"
- "Create how-to"
## Workflow
### Step 1: Minimal Prompt
```
Just paste what you want to share (any format is fine):
```
**Critical:** Do NOT ask user about types, categories, or labels. User shares freely, AI decides everything autonomously.
### Step 2: Autonomous Processing
Process user input completely autonomously:
1. **Analyze existing labels** in repo (understand current taxonomy)
2. **Detect content type** via AI (tip, how-to, troubleshooting, reference, example, question)
3. **Extract title** via AI
4. **Format content** with appropriate template
5. **Suggest labels** based on existing taxonomy (or create new if empty)
6. **Link to related knowledge** via automated search
7. **Create GitHub Issue** with all decisions made
See [REFERENCE.md](REFERENCE.md) for complete automation pipeline.
### Step 3: Confirmation (What Was Decided)
```
โ
Created Issue #{number}!
๐ What I decided:
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
Title: "{AI-extracted-title}"
Type: {type-emoji} {type-name}
Labels: {label1, label2, label3}
(based on existing repo labels)
Format: Structured with sections
{auto-generated-sections}
Related: Linked to #{n1}, #{n2}
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
๐ {issue-url}
Search: gh search issues "{keywords}" --label={primary-label}
```
## Quick Example
**Input:**
```
tmux is great for persistent sessions. ctrl-b d to detach and
tmux attach to reattach. Useful when ssh connections drop.
```
**Output:**
Formatted GitHub Issue:
- **Title:** "Terminal: Using tmux for Persistent SSH Sessions"
- **Labels:** terminal, tips, workflow
- **Content:** Structured with "What It Does", "When to Use It", "Key Commands" sections
- **Related:** Auto-linked to similar terminal tips
## Dependencies
- `gh` CLI (issue creation)
- `gh-models` extension (AI labeling, title extraction)
- `jq` (JSON processing)
## Error Handling
Content too short (< 20 chars):
```
I need more content to create a useful knowledge entry.
Could you provide at least a sentence or two?
```
API fails:
```
โ ๏ธ Couldn't create issue automatically. Here's the formatted content:
[formatted markdown shown]
Create manually: gh issue create --title "..." --body-file content.md
```
## Complete Reference
For detailed automation pipeline, templates, and examples, see [REFERENCE.md](REFERENCE.md).
---
**Repository:** <https://github.com/terrylica/claude-code-skills-github-issues>
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.