ClawKit Logo
ClawKitReliability Toolkit
Back to Registry
Official Verified developer tools Safety 5/5

skill-authoring

Guide for creating effective SKILL.md files that extend agent capabilities. Use when creating new skills, updating existing ones, or teaching the agent specialized workflows.

Why use this skill?

Learn how to create optimized, efficient SKILL.md files for OpenClaw agents. Master the standards for agent capabilities, prompt engineering, and code organization.

skill-install — Terminal

Install via CLI (Recommended)

clawhub install openclaw/skills/skills/kjaylee/skill-authoring
Or

What This Skill Does

The skill-authoring skill provides a standardized framework for developers to create, maintain, and optimize SKILL.md files for OpenClaw agents. It enforces the 'agentskills.io' standards to ensure that agent instructions remain concise, context-aware, and highly functional. By defining clear boundaries between high-freedom and low-freedom tasks, this skill helps authors craft instructions that minimize token usage while maximizing agent reliability. It includes structure templates, directory organization protocols, and best practices for balancing task-specific constraints against general-purpose intelligence.

Installation

To integrate this skill into your environment, run the following command in your terminal:

clawhub install openclaw/skills/skills/kjaylee/skill-authoring

Ensure that your agent environment has write access to your local skills directory, typically located at ~/.clawdbot/skills/. Once installed, you can trigger the authoring assistant to validate your existing or newly created skills.

Use Cases

  • Creating New Skills: Automatically generate a valid SKILL.md boilerplate with the necessary YAML front matter.
  • Refactoring Old Skills: Analyze long, verbose prompt files and condense them into efficient instructions that fit within context window limits.
  • Standardizing Workflows: Implement strict 'low-freedom' constraints for sensitive tasks like file system access or API configuration to ensure consistent execution.
  • Documentation Management: Moving deep technical specifications out of the main instruction file and into the references/ directory to save token space.

Example Prompts

  1. "I'm building a skill for web scraping; help me write a SKILL.md that balances high-level goal setting with strict constraints for the scraper script."
  2. "Review this SKILL.md file and tell me which sections I should move to the references directory to improve performance."
  3. "Generate a template for a new task-automation skill that includes custom metadata and a link to my external Python scripts."

Tips & Limitations

  • Token Budget: Always treat the context window as a shared resource. If your instructions exceed 500 lines, you must refactor to external references.
  • Agent Intelligence: Do not waste space explaining basic programming concepts the agent already knows; focus on your specific domain logic.
  • Security: Always audit scripts in the scripts/ folder before deployment, as these have direct access to your local environment.
  • Structure: Always adhere to the defined directory structure (scripts/, references/, assets/) to ensure seamless integration with the OpenClaw agent runtime.

Metadata

Author@kjaylee
Stars1776
Views0
Updated2026-03-02
View Author Profile
AI Skill Finder

Not sure this is the right skill?

Describe what you want to build — we'll match you to the best skill from 16,000+ options.

Find the right skill
Add to Configuration

Paste this into your clawhub.json to enable this plugin.

{
  "plugins": {
    "official-kjaylee-skill-authoring": {
      "enabled": true,
      "auto_update": true
    }
  }
}

Tags(AI)

#skill-development#prompt-engineering#openclaw#developer-tools#documentation
Safety Score: 5/5

Flags: file-read, file-write

Related Skills

ui-ux-pro-max

UI/UX design intelligence and implementation guidance for building polished interfaces. Use when the user asks for UI design, UX flows, information architecture, visual style direction, design systems/tokens, component specs, copy/microcopy, accessibility, or to generate/critique/refine frontend UI (HTML/CSS/JS, React, Next.js, Vue, Svelte, Tailwind). Includes workflows for (1) generating new UI layouts and styling, (2) improving existing UI/UX, (3) producing design-system tokens and component guidelines, and (4) turning UX recommendations into concrete code changes.

kjaylee 1776

ralph-loop

AI 자율 구현 방법론. 구현/개발/코딩 요청 시 자동 적용. 메인은 마더 서브에이전트를 spawn하고, 마더가 워커들을 관리. specs/ → IMPLEMENTATION_PLAN.md → 1태스크씩 구현 → 2단계 리뷰 → 테스트 → 반복.

kjaylee 1776

game-dev-rust-godot

Game development workflow using Rust+WASM or Godot 4.x for HTML5 games. Use when creating new games, implementing game mechanics, or porting existing games. Follows TDD-based production pipeline v3.1 with asset-first approach. Covers Rust(Macroquad/Bevy), Godot HTML5 Export, asset acquisition, test case writing, and QA automation. Master directive (2026-02-06) - ONLY Rust+WASM or Godot allowed, JS/TS frameworks prohibited.

kjaylee 1776

subagent-dev

Execute implementation plans using fresh subagents per task with two-stage review (spec compliance + code quality). Use when executing multi-task plans with independent work units. Enhances ralph-loop methodology.

kjaylee 1776

systematic-debugging

Root-cause-first debugging methodology. Use when encountering any bug, test failure, or unexpected behavior BEFORE proposing fixes. Prevents random fix attempts that waste time and create new bugs.

kjaylee 1776