Agent skill

Eigenskill Builder

by LeoYeAI in LeoYeAI/openclaw-master-skills

Meta-skill for building and publishing agent skills on ClawHub.

MITAuto-check passedAgent Workflows

Install Eigenskill Builder

skills CLI
$ npx skills add LeoYeAI/openclaw-master-skills --skill eigenskill-builder -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install LeoYeAI/openclaw-master-skills eigenskill-builder --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/eigenskill-builder .claude/skills/eigenskill-builder && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
eigenskill-builder
GitHub stars
2.2k
Token cost
~4.5k tokens
SKILL.md length
1,064 words
Files
2
Skills in repo
1,235
Repo updated
First seen
Licence
MIT

At a glance

Meta-skill for building and publishing agent skills on ClawHub.

  • Works in 10 steps: Skill Anatomy → YAML Frontmatter Specification → References Directory Convention → …
  • Prompt engineering
  • SKILL.md covers When to Use, When NOT to Use, 1. Skill Anatomy and 2. YAML Frontmatter…, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Eigenskill Builder is an agent skill from LeoYeAI/openclaw-master-skills. Meta-skill for building and publishing agent skills on ClawHub. Covers skill structure, YAML frontmatter specification, references directory convention, negative boundaries, installation instructions, ClawHub CLI workflow, and quality checklist. The skill that teaches agents to build skills. Do NOT use for prompt engineering, agent memory, or orchestration — those have their own dedicated skills.

Its SKILL.md is about 4.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `_meta.json`).

It sits in Agent Workflows, covering Agent memory and Prompt engineering. The repository describes itself as: 🧠 Curated collection of 1209+ best OpenClaw skills — weekly updated by MyClaw.ai. The licence is MIT.

When your agent uses it

  • Prompt engineering
  • Orchestration — those have their own dedicated skills

Example prompts

  • “/eigenskill-builder”

Workflow steps

10 steps, taken from the step headings in SKILL.md.

  1. Skill Anatomy
  2. YAML Frontmatter Specification
  3. References Directory Convention
  4. Negative Boundaries
  5. Description Interview Process
  6. Scripts Directory
  7. ClawHub CLI Workflow
  8. Quality Checklist
  9. Version Management
  10. Skill Graphs

What it can do on your machine

Read from SKILL.md and the folder at commit e5199b5. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown, yaml, bash and python).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Eigenskill Builder loads about 4.5k tokens when it runs. Until then it costs about 105 tokens; SKILL.md has 1,064 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~105
When it runs · the whole SKILL.md, loaded when a task matches
~4.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT licence (© LeoYeAI). 1,064 words, ~4,513 tokens.

Download SKILL.mdSave it as .claude/skills/eigenskill-builder/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
eigenskill-builder
description
Meta-skill for building and publishing agent skills on ClawHub. Covers skill structure, YAML frontmatter specification, references directory convention, negative boundaries, installation instructions, ClawHub CLI workflow, and quality checklist. The skill that teaches agents to build skills. Do NOT use for prompt engineering, agent memory, or orchestration — those have their own dedicated skills.
license
MIT

Eigenskill Builder

The meta-skill. This skill teaches AI agents how to build, validate, and publish skills on ClawHub. If you're creating a new skill, this is your blueprint.

When to Use

  • Creating a new skill from scratch
  • Validating an existing skill against quality standards
  • Publishing a skill to ClawHub
  • Designing skill descriptions with proper trigger/exclusion boundaries
  • Setting up references/ directories for supplementary material
  • Planning skill graphs for large skill libraries (50+)

When NOT to Use

  • Writing prompts or prompt templates (use a prompt-engineering skill)
  • Building agent memory systems (use agent-memory-architecture)
  • Orchestrating multiple agents (use agent-orchestration)
  • Fine-tuning models or training data preparation
  • Building MCP servers or tools (that's tool development, not skill development)

1. Skill Anatomy

Every skill is a directory containing at minimum a SKILL.md file. The directory name should be kebab-case and match the skill name.

Directory Structure
skills/
  my-skill-name/
    SKILL.md              # Required: the skill definition
    references/           # Optional: supplementary material
      api-docs.md
      examples.md
      cheatsheet.md
    scripts/              # Optional: automation scripts
      validate.sh
      install.sh
SKILL.md Structure
markdown
---
name: my-skill-name
description: 'One paragraph. What it does. When to trigger. When NOT to trigger.'
license: MIT
metadata:
  openclaw:
    emoji: '🔧'
---

# Skill Title

[Brief overview — 2-3 sentences max]

## When to Use
[Bulleted list of trigger conditions]

## When NOT to Use
[Bulleted list of exclusion conditions — REQUIRED]

---

## Section 1: [Topic]
[Content with examples]

## Section 2: [Topic]
[Content with examples]

...

2. YAML Frontmatter Specification

The frontmatter block is the machine-readable identity of the skill. It must be valid YAML between --- delimiters.

Required Fields
FieldTypeDescriptionExample
namestringKebab-case identifier, unique on ClawHubfinancial-analysis-agent
descriptionstringSingle-quoted paragraph. Must include trigger AND exclusion.See below
licensestringSPDX identifierMIT, Apache-2.0, CC-BY-4.0
Optional Fields
FieldTypeDescriptionExample
versionstringSemver1.0.0
authorstringCreator name or handle@openclaw
tagslistDiscovery tags[finance, analysis, cfp]
dependslistOther skills this depends on[agent-memory-architecture]
metadata.openclaw.emojistringDisplay emoji on ClawHub'💰'
metadata.openclaw.tierstringComplexity tierfoundational, intermediate, advanced
metadata.openclaw.modelslistModels this skill works best with[claude-opus-4-6, claude-sonnet-4-6]
Description Best Practices

The description field is the most important field. It's what agents use to decide whether to load the skill. It must be:

  1. Specific — list the concrete things the skill covers
  2. Bounded — say what it does NOT cover
  3. Trigger-rich — include keywords an agent would search for

Good:

yaml
description: 'Financial analysis skill for AI agents. Covers variance analysis, cash flow forecasting, month-end close automation, CFO commentary generation. Do NOT use for tax preparation, audit opinions, or regulatory filings.'

Bad:

yaml
description: 'A skill for finance stuff.'

Bad:

yaml
description: 'Comprehensive enterprise-grade financial analysis solution leveraging AI-powered insights for transformative business intelligence.'

3. References Directory Convention

The references/ directory holds supplementary material that the skill can point to but that shouldn't be in the main SKILL.md (to keep it focused).

Rules
  1. One level deep only — references/file.md is fine. references/sub/file.md is not.
  2. Never chain references — a reference file should not reference another reference file. References are leaves, not nodes.
  3. Keep references self-contained — each file should make sense on its own without reading SKILL.md first.
  4. Name descriptively — api-authentication.md not ref1.md.
When to Use References vs Inline Content
Content TypeLocationRationale
Core methodologySKILL.mdAgent needs this to execute
Quick reference tablesSKILL.mdFrequently accessed
Detailed API docsreferences/Only needed for specific tasks
Extended examplesreferences/Useful but not essential
Cheat sheetsreferences/Quick lookup, not learning
Historical contextreferences/Background, not action
Example References Directory
skills/financial-analysis-agent/
  SKILL.md
  references/
    gaap-ifrs-differences.md      # Detailed comparison table
    ratio-benchmarks-by-industry.md  # Industry-specific ratio ranges
    asc-606-checklist.md           # Revenue recognition deep dive
    sample-board-package.md        # Example board reporting package

4. Negative Boundaries

Every skill MUST define what it does NOT do. This is not optional — it's the most important part of skill design after the core content.

Why Negative Boundaries Matter

Without negative boundaries:

  • Agents load wrong skills for tasks → bad output
  • Skills overlap silently → conflicts and confusion
  • Users don't know where one skill ends and another begins
The Exclusion Checklist

For every skill, explicitly answer:

  1. Adjacent skills — What similar skills exist that this one is NOT?
  2. Common misconceptions — What do people assume this covers that it doesn't?
  3. Scope ceiling — What's the most complex thing this skill can handle? What's above that ceiling?
  4. Scope floor — What's too simple for this skill? (e.g., "don't use this to add two numbers")
Template
markdown
## When NOT to Use

- [Adjacent skill 1] — use [other-skill-name] instead
- [Adjacent skill 2] — use [other-skill-name] instead
- [Common misconception] — this skill does not cover [X]
- Tasks requiring [thing above scope ceiling] — escalate to [human/specialist]
- Simple [thing below scope floor] — just do it directly, no skill needed
Example
markdown
## When NOT to Use

- Tax preparation or tax advisory — use crypto-tax-agent or consult a CPA
- Audit opinions or attestation — requires human CPA, not an agent skill
- Regulatory filings (SEC 10-K, etc.) — use a compliance-specific skill
- Simple arithmetic or unit conversions — just calculate directly
- Investment advice or stock picks — this is analysis, not advisory

5. Description Interview Process

When building a new skill, interview yourself (or the skill author) with these questions to produce a high-quality description.

The Interview
Step 1: Define Triggers
Q: What specific phrases would someone say that should activate this skill?
A: List 5-10 trigger phrases.

Example:
- "Analyze the variance between budget and actual"
- "Generate a 13-week cash flow forecast"
- "Write CFO commentary for the board package"
- "Review the financial statements before close"
Step 2: Define Exclusions
Q: What phrases sound similar but should NOT activate this skill?
A: List 5-10 exclusion phrases.

Example:
- "File our tax return" → tax skill, not this one
- "Should we invest in X stock?" → not advisory
- "Audit the financial statements" → requires CPA
Step 3: Define Dependencies
Q: What other skills or knowledge does this skill assume?
A: List prerequisites.

Example:
- Basic accounting knowledge (debits/credits)
- Access to financial data (GL, subledger)
- Familiarity with Excel/Sheets for output formatting
Step 4: Write the Description

Combine triggers, exclusions, and dependencies into a single paragraph:

yaml
description: '[What it does — 1 sentence]. Covers [trigger keywords]. Assumes [dependencies]. Do NOT use for [exclusions].'
Step 5: Test the Description

Ask: "If an agent read only this description, would it correctly decide to load or skip this skill for these 10 test queries?"

Test with 5 queries that SHOULD trigger and 5 that should NOT.


Show full SKILL.md (407 more words)Show less

6. Scripts Directory

The scripts/ directory holds automation for skill lifecycle operations.

Common Scripts
bash
# scripts/validate.sh — Check skill quality
#!/bin/bash
set -euo pipefail

SKILL_DIR="$(dirname "$0")/.."
SKILL_FILE="$SKILL_DIR/SKILL.md"

# Check SKILL.md exists
[[ -f "$SKILL_FILE" ]] || { echo "FAIL: SKILL.md not found"; exit 1; }

# Check frontmatter exists
head -1 "$SKILL_FILE" | grep -q "^---$" || { echo "FAIL: Missing frontmatter"; exit 1; }

# Check required fields
grep -q "^name:" "$SKILL_FILE" || { echo "FAIL: Missing name field"; exit 1; }
grep -q "^description:" "$SKILL_FILE" || { echo "FAIL: Missing description field"; exit 1; }
grep -q "^license:" "$SKILL_FILE" || { echo "FAIL: Missing license field"; exit 1; }

# Check negative boundaries exist
grep -q "When NOT to Use" "$SKILL_FILE" || { echo "FAIL: Missing negative boundaries"; exit 1; }

# Check description includes exclusions
DESC=$(grep "^description:" "$SKILL_FILE")
echo "$DESC" | grep -qi "not\|don't\|do not\|except\|exclud" || {
    echo "WARN: Description may lack exclusion language"
}

# Check references depth
if [[ -d "$SKILL_DIR/references" ]]; then
    DEPTH=$(find "$SKILL_DIR/references" -mindepth 2 -type f | wc -l)
    [[ "$DEPTH" -eq 0 ]] || { echo "FAIL: References nested >1 level deep"; exit 1; }
fi

echo "PASS: Skill validation complete"
bash
# scripts/install.sh — Install skill into agent workspace
#!/bin/bash
set -euo pipefail

SKILL_NAME="$(basename "$(dirname "$0")/..")"
TARGET="${1:-$HOME/.openclaw/workspace/skills}"

echo "Installing $SKILL_NAME to $TARGET/$SKILL_NAME"
cp -r "$(dirname "$0")/.." "$TARGET/$SKILL_NAME"
echo "Done. Skill available at $TARGET/$SKILL_NAME/SKILL.md"

7. ClawHub CLI Workflow

ClawHub is the registry for discovering, installing, and publishing skills.

Commands
bash
# Search for skills
clawhub search "financial analysis"
clawhub search --tag finance
clawhub search --emoji 💰

# View skill details
clawhub info financial-analysis-agent
clawhub info financial-analysis-agent --versions

# Install a skill
clawhub install financial-analysis-agent
clawhub install financial-analysis-agent@1.2.0
clawhub install financial-analysis-agent --path ./my-skills/

# Publish a skill
clawhub publish ./skills/my-skill/
clawhub publish ./skills/my-skill/ --dry-run  # Validate without publishing

# Update skills
clawhub update                          # Update all installed skills
clawhub update financial-analysis-agent  # Update specific skill
clawhub outdated                         # List skills with available updates

# List installed skills
clawhub list
clawhub list --format json
Publishing Checklist (Pre-publish)

Before running clawhub publish:

  1. scripts/validate.sh passes
  2. Description includes trigger AND exclusion language
  3. All examples are tested and working
  4. References are one level deep only
  5. No secrets, API keys, or credentials in any file
  6. License is specified and compatible
  7. Version is bumped if updating existing skill
Publishing Flow
1. Author creates skill locally
2. Run: clawhub publish ./skills/my-skill/ --dry-run
3. Fix any validation errors
4. Run: clawhub publish ./skills/my-skill/
5. ClawHub assigns a unique ID and indexes the skill
6. Skill appears in search results within 5 minutes
7. Other agents can install via: clawhub install my-skill

8. Quality Checklist

Score every skill against these 10 criteria before publishing.

#CriterionPass/FailNotes
1SKILL.md exists with valid YAML frontmatterRequiredMust parse without errors
2Name is kebab-case and uniqueRequiredCheck clawhub search first
3Description is specific with triggers AND exclusionsRequired>50 chars, <500 chars
4"When to Use" section with 3+ bullet pointsRequiredConcrete, not vague
5"When NOT to Use" section with 3+ bullet pointsRequiredNames alternative skills
6Actionable content — agent can execute, not just readRequiredInclude templates, formulas, steps
7Examples for every major conceptRecommendedShow input → output
8References one level deep (if references/ exists)RequiredNo nested references
9No secrets or credentials in any fileRequiredScan before publish
10License specified and SPDX-validRequiredMIT, Apache-2.0, etc.
Scoring
10/10 — Ready to publish
8-9/10 — Minor fixes needed, publishable
6-7/10 — Needs work, don't publish yet
<6/10 — Fundamental issues, redesign needed

9. Version Management

Semver for Skills
MAJOR.MINOR.PATCH

MAJOR — Breaking changes to skill structure or content that would change agent behavior
MINOR — New content sections, expanded examples, new references
PATCH — Typo fixes, clarifications, formatting improvements
Version Bump Rules
ChangeBumpExample
Fix a typo in an examplePATCH1.0.0 → 1.0.1
Add a new section on ratio analysisMINOR1.0.1 → 1.1.0
Restructure from 5 sections to 10MAJOR1.1.0 → 2.0.0
Change the description triggersMAJOR2.0.0 → 3.0.0
Add a reference fileMINOR1.0.0 → 1.1.0
Update examples for new API versionMINOR1.1.0 → 1.2.0
Changelog Convention

Add a ## Changelog section at the bottom of SKILL.md for significant versions:

markdown
## Changelog

### 2.0.0 (2026-03-15)
- Restructured from 5 to 9 sections
- Added aging analysis and bank reconciliation
- Breaking: removed deprecated ratio shortcuts

### 1.1.0 (2026-03-01)
- Added CFO commentary templates
- New reference: sample-board-package.md

### 1.0.0 (2026-02-15)
- Initial release

10. Skill Graphs

When your skill library grows past ~50 skills, you need a way to discover relationships between skills. Skill graphs solve this.

Concept

Each skill can declare relationships to other skills using two mechanisms:

  1. YAML depends field — hard dependencies (skill won't work without these)
  2. Wikilinks in content — soft references (related but not required)
YAML Dependencies
yaml
depends:
  - agent-memory-architecture    # Required: this skill uses memory patterns
  - agent-orchestration          # Required: this skill uses orchestration patterns

Use [[skill-name]] syntax to create soft links:

markdown
For memory patterns used in financial analysis workflows, see [[agent-memory-architecture]].

When orchestrating multiple financial analysis agents, apply the patterns in [[agent-orchestration]].
Graph Queries

With a skill graph, you can answer:

"What skills does financial-analysis-agent depend on?"
  → agent-memory-architecture, agent-orchestration

"What skills reference financial-analysis-agent?"
  → eigenskill-builder (as example), cfo-reporting-agent

"What's the shortest path from crypto-tax-agent to agent-orchestration?"
  → crypto-tax-agent → financial-analysis-agent → agent-orchestration

"What are the foundational skills (most depended on)?"
  → agent-memory-architecture (12 dependents)
  → agent-orchestration (8 dependents)
  → eigenskill-builder (6 dependents)
Building the Graph
python
import yaml
import re
from pathlib import Path

def build_skill_graph(skills_dir: Path) -> dict:
    """Build a dependency graph from all skills."""
    graph = {"nodes": {}, "edges": []}

    for skill_dir in skills_dir.iterdir():
        skill_file = skill_dir / "SKILL.md"
        if not skill_file.exists():
            continue

        content = skill_file.read_text()

        # Parse frontmatter
        fm_match = re.search(r'^---\n(.*?)\n---', content, re.DOTALL)
        if not fm_match:
            continue
        fm = yaml.safe_load(fm_match.group(1))

        name = fm.get("name", skill_dir.name)
        graph["nodes"][name] = {
            "description": fm.get("description", ""),
            "emoji": fm.get("metadata", {}).get("openclaw", {}).get("emoji", ""),
        }

        # Hard dependencies (YAML)
        for dep in fm.get("depends", []):
            graph["edges"].append({
                "from": name, "to": dep, "type": "depends"
            })

        # Soft references (wikilinks)
        for link in re.findall(r'\[\[([\w-]+)\]\]', content):
            if link != name:  # No self-links
                graph["edges"].append({
                    "from": name, "to": link, "type": "references"
                })

    return graph
Visualization

For small libraries (<20), a simple ASCII graph works:

eigenskill-builder ──depends──▶ agent-orchestration
       │                              ▲
       │                              │
       ▼                              │
financial-analysis-agent ──references─┘
       │
       ▼
crypto-tax-agent

For larger libraries, export to DOT format and render with Graphviz, or use a JSON graph viewer.

© LeoYeAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in skills/eigenskill-builder of LeoYeAI/openclaw-master-skills.

  • SKILL.md
  • _meta.json

Open the folder on GitHubat commit e5199b5

Compare with similar skills

Eigenskill Builder next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Eigenskill Builder compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Eigenskill Builder this skillLeoYeAI/openclaw-master-skills2.2k—~4.5kAutomated safety check: PassMIT
Claude Code Agent Developmentanthropics/claude-plugins-official38k7 repos~2.8kAutomated safety check: PassApache-2.0
Mem0 CLI Memory Commandsmem0ai/mem067k—~2kAutomated safety check: NotesApache-2.0
Create Agentvectorize-io/hindsight47k—~1.1kAutomated safety check: PassMIT
Memori Long-Term MemoryMemoriLabs/Memori17k—~2kAutomated safety check: PassApache-2.0
Workflow Schema Tuningbreaking-brake/cc-wf-studio5.4k—~1.3kAutomated safety check: PassCustom licence

Similar skills

  • Claude Code Agent Development

    anthropics/claude-plugins-official

    Official

    Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.

    38k GitHub starsUsed in 7 repos~2.8k tokens
    Agent WorkflowsAuto-check passed
  • Adds, searches, lists, updates and deletes memories on the Mem0 platform from the terminal with the mem0 command, including a JSON mode built for agents.

    67k GitHub stars~2k tokensUpdated today
    Agent WorkflowsAuto-check: notes
  • Create Agent

    vectorize-io/hindsight

    Create a new Hindsight-powered subagent with long-term memory.

    47k GitHub stars~1.1k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • Memori Long-Term Memory

    MemoriLabs/Memori

    Adds structured long-term memory to OpenClaw agents, built automatically from sessions, with tools the agent calls to recall facts, summaries and decisions.

    17k GitHub stars~2k tokensUpdated 7 days ago
    Agent WorkflowsAuto-check passed
  • Workflow Schema Tuning

    breaking-brake/cc-wf-studio

    Guides edits to cc-wf-studio's workflow schema so AI agents generate better workflows, treating schema text as prompt engineering rather than validation.

    5.4k GitHub stars~1.3k tokensUpdated 3 days ago
    Agent WorkflowsAuto-check passed
  • Explains how cognee stores session memory by session_id and bridges it into the permanent graph with improve(), including the stages, results and settings.

    32k GitHub stars~3.2k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

More from LeoYeAI/openclaw-master-skills

All 1,235 skills in this repo
  • DevOps Pipeline Management

    LeoYeAI/openclaw-master-skills

    Manages pipelines on a DevOps quality and efficiency platform through its OpenAPI: list workspaces and templates, create, update, run and cancel pipelines, and read run records.

    2.2k GitHub stars~4.2k tokensUpdated 2 mo ago
    Auto-check: notes
  • Feishu Document Collaboration

    LeoYeAI/openclaw-master-skills

    Patches OpenClaw's Feishu extension so an edited document triggers an isolated agent session that reads the doc and replies inline, turning it into a live chat space.

    2.2k GitHub stars~2k tokensUpdated 2 mo ago
    Auto-check passed
  • Files Memory System

    LeoYeAI/openclaw-master-skills

    Multi-context memory management system for OpenClaw agents with group-isolated storage, global shared memory, workspace organization, and group-specific skills isolation.

    2.2k GitHub stars~3.8k tokensUpdated 2 mo ago
    Auto-check passed
  • GEO-Claw AI Visibility Agent

    LeoYeAI/openclaw-master-skills

    Runs a brand's AI-search visibility work end to end: diagnosing how AI platforms represent it, repositioning it, producing AI-optimized content and monitoring ongoing mentions.

    2.2k GitHub stars~4.7k tokensUpdated 2 mo ago
    Auto-check passed
  • Google Workspace CLI

    LeoYeAI/openclaw-master-skills

    Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits.

    2.2k GitHub stars~2.6k tokensUpdated 2 mo ago
    Auto-check: notes
  • HealthFit Health Advisors

    LeoYeAI/openclaw-master-skills

    Runs four advisor roles, a fitness coach, nutritionist, data analyst and TCM practitioner, to build a health profile and track workouts, diet and wellness over time.

    2.2k GitHub stars~4.4k tokensUpdated 2 mo ago
    Auto-check passed

Questions about Eigenskill Builder

What does Eigenskill Builder do?

Meta-skill for building and publishing agent skills on ClawHub. Eigenskill Builder is an agent skill from LeoYeAI/openclaw-master-skills. Meta-skill for building and publishing agent skills on ClawHub.

When should I use Eigenskill Builder?

Eigenskill Builder fits situations like: prompt engineering; orchestration — those have their own dedicated skills.

How do I install Eigenskill Builder in Claude Code?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill eigenskill-builder -a claude-code`. Or copy the skill folder (skills/eigenskill-builder in LeoYeAI/openclaw-master-skills) into .claude/skills/eigenskill-builder in your project. Claude Code loads it when a task matches its description.

How do I install Eigenskill Builder in Codex?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill eigenskill-builder -a codex`. Or copy the skill folder (skills/eigenskill-builder in LeoYeAI/openclaw-master-skills) into .agents/skills/eigenskill-builder in your project. Codex loads it when a task matches its description.

Can I use Eigenskill Builder in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LeoYeAI/openclaw-master-skills --skill eigenskill-builder -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/eigenskill-builder, .gemini/skills/eigenskill-builder, .github/skills/eigenskill-builder and .opencode/skills/eigenskill-builder in your project.

What does Eigenskill Builder need to run?

SKILL.md names no scripts, command-line tools or credentials: Eigenskill Builder is instructions for the agent only.

Does Eigenskill Builder access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Eigenskill Builder safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Eigenskill Builder use?

Eigenskill Builder is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Eigenskill Builder use?

About 4.5k tokens (SKILL.md is roughly 18k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Eigenskill Builder?

Skills that share tags, products or a category with Eigenskill Builder: Claude Code Agent Development (anthropics/claude-plugins-official, 38k stars), Mem0 CLI Memory Commands (mem0ai/mem0, 67k stars), Create Agent (vectorize-io/hindsight, 47k stars) and Memori Long-Term Memory (MemoriLabs/Memori, 17k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Eigenskill Builder?

LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,160 GitHub stars. The repository holds 1,235 skills in this directory. The repository was last updated on July 20, 2026.

Source: LeoYeAI/openclaw-master-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.