hk

Mutate GitHub issues into linked knowledge graph nodes via gh api.

47|9|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/juspay/kolu --skill hk-juspay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hk
Source: https://github.com/juspay/kolu/tree/main/.apm/skills/hk
Command: npx skills add https://github.com/juspay/kolu --skill hk-juspay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turn GitHub issues into interlinked knowledge nodes in a Zettelkasten-like system, enabling automatic backlinks and cross-references across your repo set.

Core Features & Use Cases

  • One repository = one kasten; every issue is a distinct node.
  • #N references create backlinks and GitHub auto-tracks backlinks via CrossReferencedEvent.
  • Mutate and create nodes from natural language prompts using /hk invocations.

Quick Start

Type /hk #N <prompt> or /hk owner/repo#N <prompt> or /hk <prompt> to create or mutate a linked node.

Frequently Asked Questions about hk

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I link GitHub issues to create a knowledge graph?

Link GitHub issues into a knowledge graph by using #N references and owner/repo#N syntax within issue bodies. GitHub automatically tracks these cross-references via CrossReferencedEvent to generate backlinks.

What is a Zettelkasten system for GitHub issues?

A Zettelkasten for GitHub issues treats every issue as a distinct knowledge node and each repository as a separate kasten. This structure enables interlinked knowledge management with automatic backlinks across your repository set.

How do I create and mutate GitHub issues from natural language?

Create and mutate GitHub issues from natural language by invoking /hk with a prompt. The Skill enforces fresh reads before edits and mutates nodes via the gh api without requiring extra confirmation.

Do I need the GitHub CLI to automate backlinks across repositories?

Automating backlinks across repositories relies on the gh api to mutate issues and GitHub's CrossReferencedEvent to track links. You need access to the GitHub API environment to enforce fresh reads and apply issue-structure conventions.

Can I reference issues in a different repository for knowledge management?

Reference issues in different repositories using the owner/repo#N syntax. This creates cross-references that GitHub automatically tracks, linking knowledge nodes across your entire repository set.