Name: github-kernel
Author: Z1-Test

Imported from Z1-Test/temp-dhruv-st7 (.github/skills/github-kernel/SKILL.md). Install upstream with npx skills add Z1-Test/temp-dhruv-st7 --skill github-kernel. Copyright stays with the author.

What is it?

The GitHub Kernel is the foundational skill that defines the "laws of physics" for all other GitHub capability skills. It provides the central source of truth for:

Tool selection strategy (Escalation Ladder).
Safety boundaries and non-negotiable rules.
Conventions for interactions with the GitHub platform.
Mapping of abstract capabilities to concrete MCP tools.

Success Criteria

Foundational rules are applied across all other GitHub skills.
The Tool Escalation Ladder is followed consistently.
Safety rules for destructive operations are respected.
Interaction conventions (naming, commits) are maintained.

When to use this skill

Consult this skill for foundational knowledge when initializing a GitHub-related session.
Refer to this skill whenever you are unsure about which tool to use (MCP vs. CLI vs. API).
Consult this skill to check if an action is considered "safe" or requires user confirmation.

What this skill can do

Explain the Tool Escalation Ladder.
Define Safety Rules for destructive operations.
Map capabilities to specific MCP Tools.
Establish consistent conventions for branch naming, commit messages, and PR titles (see CONVENTIONAL_COMMITS.md).

What this skill will NOT do

Execute any GitHub actions. This skill is purely informational.
Create issues or PRs.
Modify repository state.
Interact with the API directly.

How to use this skill

This skill is a passive reference.

Read the reference documents to understand the operating parameters.
Apply the rules when executing other skills like github-issues or github-pr-flow.

Tool usage rules

All GitHub skills must adhere to the Escalation Ladder:

Primary: Use GitHub MCP Tools (fast, safe, context-aware).
Fallback: Use gh CLI (if MCP is missing/broken).
Last Resort: Use REST API (only for edge cases like metadata fields).

See TOOL_ESCALATION.md for detailed logic.

Examples

Determining Tool Safety

"I need to delete a file. Is this safe?" Check SAFETY_RULES.md -> Destructive operation -> Requires explicit confirmation.

Selecting the Right Tool

"I need to comment on an issue." Check MCP_TOOL_MAP.md -> add_issue_comment is available -> Use MCP.

Limitations

Does not enforce rules programmatically; agents must voluntarily adhere to these guidelines.
Does not contain specific workflow logic for complex tasks (like "release management").

Install github-kernel and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "z1-test-temp-dhruv-st7-github-kernel", "kind": "skill", "name": "github-kernel", "description": "foundational definitions for GitHub skills, safety rules, tool escalation, and security boundaries", "publisher": "Z1-Test", "version": "1.0.0", "capabilities": { "domains": [ "general" ], "tags": [ "skill-md", "github" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "foundational definitions for GitHub skills, safety rules, tool escalation, and security boundaries" ], "primary": false, "metadata": { "source": { "provider": "github", "repository": "https://github.com/Z1-Test/temp-dhruv-st7", "path": ".github/skills/github-kernel/SKILL.md", "ref": "d345cf1631a23ceca7bdf8cbbee7e3e1490a7fbd", "url": "https://github.com/Z1-Test/temp-dhruv-st7/blob/d345cf1631a23ceca7bdf8cbbee7e3e1490a7fbd/.github/skills/github-kernel/SKILL.md", "key": "Z1-Test/temp-dhruv-st7/.github/skills/github-kernel/SKILL.md" } }, "instructions": "## What is it?\n\nThe **GitHub Kernel** is the foundational skill that defines the \"laws of physics\" for all other GitHub capability skills. It provides the central source of truth for:\n\n- Tool selection strategy (Escalation Ladder).\n- Safety boundaries and non-negotiable rules.\n- Conventions for interactions with the GitHub platform.\n- Mapping of abstract capabilities to concrete MCP tools.\n\n## Success Criteria\n- Foundational rules are applied across all other GitHub skills.\n- The Tool Escalation Ladder is followed consistently.\n- Safety rules for destructive operations are respected.\n- Interac", "cost": { "context_tokens": 670 } }

github-kernel

About