geeksfino/openskills · Archived

openskills-skill-authoring

Create and refine OpenSkills-compatible skills (SKILL.md + optional resources) with strong metadata, clear activation triggers, and reliable execution guidance.

First seen Mar 4, 2026

Installation

$ npx skills add geeksfino/openskills --skill openskills-skill-authoring

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from geeksfino/openskills · top by installs.

npx skills add geeksfino/openskills

Browse all from geeksfino/openskills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 60
License LICENSE
Default branch main
Open issues 0
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,338 B
  • docs SUMMARY.md 194 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 3 installs

SKILL.md

OpenSkills Skill Authoring

Use this skill when creating or updating skills under examples/skills or any OpenSkills-compatible skill directory.

Authoring Standard

Each skill directory should include:

  • SKILL.md (required)
  • optional scripts/, references/, assets/

SKILL.md Requirements

  • YAML frontmatter with:

- name - description

  • Body with concise instructions and practical execution flow.
  • Description must include both:

- what the skill does - when to activate it

Writing Guidance

  1. Keep core instructions short; move details to references/.
  2. Prefer deterministic scripts for fragile or repetitive steps.
  3. Include explicit input/output expectations.
  4. Avoid vague names and ambiguous activation phrases.

Validation Flow

  1. Ensure directory name matches skill name semantics.
  2. Verify skill discovery and activation behavior in runtime or example agent.
  3. If scripts are present, verify paths and execution assumptions.

Output Format

  • Skill metadata quality review
  • Instruction clarity review
  • Activation trigger quality review
  • Suggested revisions