authoring-a-skill

Stars5

Forks0

UpdatedJune 1, 2026 at 21:28

Write a new reusable skill (SKILL.md) so korgex gets better at recurring work

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

New1Direction

New1Direction/korgex

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Computer Occupations, All OtherComputer and Mathematical Occupations·SOC 15-1299

SKILL.md

readonly

name	authoring-a-skill
description	Write a new reusable skill (SKILL.md) so korgex gets better at recurring work
version	1
trust	built-in

A skill captures a durable, repeatable procedure so it doesn't have to be re-derived. Write one when you've solved something you'll plausibly hit again.

Is it skill-worthy? Yes if it's a GENERAL, reusable procedure. No if it's a one-off answer or project-specific trivia (that belongs in memory/AGENTS.md).
Location & format. Create ./.korgex/skills/<kebab-name>/SKILL.md (project) or ~/.korgex/skills/<kebab-name>/SKILL.md (global). Frontmatter:
```
---
name: <kebab-name>
description: <one line — used to decide when to load it>
version: 1.0
trust: user
---
```
Write the body as a short numbered procedure: the steps to follow, the order, and the checks. Keep it tight — it's injected by description and loaded on demand, so the body should be actionable, not an essay.
Scope the name well. The description is the only thing the agent sees when deciding to use it, so make it specific and trigger-able.
Leave trust: user. korgex's own learned skills are trust: agent; never hand-edit a built-in.

More from this repository

same repository

react-doctor

New1Direction/korgex

Catch bad React in your changes — run react-doctor's deterministic scan and fix what it flags

2026-06-055

security-scan

New1Direction/korgex

Run a verifiable security scan (vulns, secrets, misconfig) over code you wrote or deps you added, before calling the work done

2026-06-035

browser-automation

New1Direction/korgex

Drive a real browser verifiably — navigate, snapshot, act BY INDEX, extract; every step provable

2026-06-025

verifiable-orchestration

New1Direction/korgex

Run multi-agent work as ONE provable causal DAG — parallel subagents, an Orchestrate graph, an immutable spec-seed

2026-06-025

building-an-mcp-server

New1Direction/korgex

Author or connect a Model Context Protocol server so an agent gains new tools

2026-06-015

ci-cd-pipelines

New1Direction/korgex

Build automated pipelines that gate merges and ship reliably

2026-06-015

name	authoring-a-skill
description	Write a new reusable skill (SKILL.md) so korgex gets better at recurring work
version	1
trust	built-in

A skill captures a durable, repeatable procedure so it doesn't have to be re-derived. Write one when you've solved something you'll plausibly hit again.

Is it skill-worthy? Yes if it's a GENERAL, reusable procedure. No if it's a one-off answer or project-specific trivia (that belongs in memory/AGENTS.md).
Location & format. Create ./.korgex/skills/<kebab-name>/SKILL.md (project) or ~/.korgex/skills/<kebab-name>/SKILL.md (global). Frontmatter:
```
---
name: <kebab-name>
description: <one line — used to decide when to load it>
version: 1.0
trust: user
---
```
Write the body as a short numbered procedure: the steps to follow, the order, and the checks. Keep it tight — it's injected by description and loaded on demand, so the body should be actionable, not an essay.
Scope the name well. The description is the only thing the agent sees when deciding to use it, so make it specific and trigger-able.
Leave trust: user. korgex's own learned skills are trust: agent; never hand-edit a built-in.