OpenParable
Skip to content
← Back to skills

Creating Knowledge Entries

Documents
creating-knowledge-entries

Creating Knowledge Entries is an Agent Skill for documents published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Create GitHub Issue knowledge entries. TRIGGERS - share knowledge, document solution, create how-to, add to knowledge base.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/data/creating-knowledge-entries/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/creating-knowledge-entries, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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 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.

Repository: https://github.com/terrylica/claude-code-skills-github-issues