OE

open-edge-platform/skills

Developer tools
6 stars Quality 46 Trend 22

Repository for Open Edge Platform Agent Skills

Overview

This repository is the central hub for to be used by the customers to build solutions with Open Edge Platform products. The update-skills-index workflow keeps this repository's README and .agents/skills/ directory in sync automatically. It: - Runs on a to pick up upstream skill changes. - Can be triggered via workflow_dispatch for on-demand syncs or dry-run previews. - Reads skills-config.json as the for which skills to install. - Installs or updates each skill via npx skills add/update, then rebuilds the skills table in the README between the / sentinels. 1. skills that are no longer in skills-config.json or whose configured source (repo / ref / path) has changed. 2. remaining installs/updates by (repo, ref) so each source repository is cloned only once per run, regardless of how many skills it contains. 3. each installed skill appears in skills-lock.json at the expected path; falls back to a path-scoped retry if a skill is nested too deeply for the CLI's default scan depth.

README

Open Edge Platform — Agent Skills Index

This repository is the central hub for External facing agent skills to be used by the customers to build solutions with Open Edge Platform products.



Documentation

Guide Description
Overview What skills are and key features of this repository
Get Started Install, list, update, and remove skills via npx skills
How It Works Skill loading, index maintenance CI workflow, and lock file
Release Notes Changelog and release history

Maintaining the Index

The update-skills-index workflow keeps this repository’s README and .agents/skills/ directory in sync automatically. It:

  • Runs on a daily schedule to pick up upstream skill changes.
  • Can be triggered manually via workflow_dispatch for on-demand syncs or dry-run previews.
  • Reads skills-config.json as the single source of truth for which skills to install.
  • Installs or updates each skill via npx skills add/update, then rebuilds the skills table in the README between the / sentinels.

Reconciliation Logic

On each run the workflow:

  1. Removes skills that are no longer in skills-config.json or whose configured source (repo / ref / path) has changed.
  2. Batches remaining installs/updates by (repo, ref) so each source repository is cloned only once per run, regardless of how many skills it contains.
  3. Verifies each installed skill appears in skills-lock.json at the expected path; falls back to a path-scoped retry if a skill is nested too deeply for the CLI’s default scan depth.

Contributing a Skill

See CONTRIBUTING.md for contribution guidelines.

To add a skill to the org index:

  1. Create a SKILL.md in your repo with all the required artifacts. Supported locations (in order of convention):

    Scenario Path
    Standard (GitHub Copilot / VS Code) **/.github/skills//SKILL.md
    Agent-agnostic **/.agents/skills//SKILL.md
    Skills folder **/skills//SKILL.md
    Repo root, single skill SKILL.md

    Go through some of the guidelines documented at SKILLS_GUIDE.md for defining, creating, validating and managing skills.

  2. Run skill validator and skillspector against your skills to have a clean report.

    # Run skill-validator tool
    skill-validator check --allow-dirs=evals,benchmark,example-prompts /path/to/your-skill
    # Run skillspector tool
    skillspector scan /path/to/your-skill --no-llm
    
  3. Evaluate and benchmark your skill using tools/run_multi_cli_eval.py. This runs your skill’s evals/evals.json across GitHub Copilot CLI, Claude Code CLI, and OpenAI Codex CLI per configuration, grades each run with an LLM judge, and produces per-CLI and cross-CLI benchmark reports:

    python3 tools/run_multi_cli_eval.py \
      --skill-path /path/to/your-skill \
    

    See tools/README.md for the full option reference, including how to run multiple coding agents CLIs, pin specific models, skip grading, or point at non-default CLI binary paths.

  4. Add an entry to skills-config.json in this repo and open a PR against main.

    On every PR that touches skills-config.json, the Check Skills Config workflow runs automatically. It validates the config against its JSON schema and verifies that every newly added skill actually exists at the declared path in its source repository. This check is a required status check — the PR cannot be merged until it passes.

    Once the PR is merged, the Update Skills Index workflow triggers automatically on the push to main. It installs or updates each skill via npx skills add/update and rebuilds the skills table in this README. The workflow also runs on a daily schedule to pick up upstream skill changes, and can be triggered manually via workflow_dispatch for on-demand syncs or dry-run previews.

View the full README on GitHub

Recommended Tools

Try a different keyword or remove a filter.

Install

npx skillfish add open-edge-platform/skills
New to MCP? Start with the mcpskill.org guide →