Skill Hub

Open a skill,and see everything inside.

The skill page is the second layer: the original SKILL.md and every file it includes. Before giving it to an AI agent, you can read every word the agent will see.

SKILL.md

The first few lines,as REZICS reads them.

Example of a skill folder.

  • name:

    chapter-cast

    The name uses lowercase letters, numbers, and hyphens, and must match the folder name. It identifies a skill, but matching names alone do not prove two skills are the same.

  • description:

    List the characters in a chapter with passage locations. Use when organizing a character list.

    This is the sentence shown in the directory and the first sentence an AI agent reads.

  • license:

    Apache-2.0

    The license is recorded on the version along with who declared it and when. It is a declaration, not a legal review.

  • compatibility:

    Requires an agent that can read local files

    Compatibility conditions written by the author are marked “independent verification needed,” not treated as confirmed.

  • allowed-tools:

    read-file

    Allowed tools are also declarations, marked “independent verification needed.”

  • Other fields

    Fields outside the specification are preserved as written and listed separately.

Files

One row for every file.

Each file has a recorded path, role, and hash. The downloaded bytes match the page record.

  • Instructions

    SKILL.md

    The full text appears exactly as written, without changes.

  • ScriptsExecutable

    scripts/

    Executable files are marked. REZICS stores them on import but does not run them.

  • References

    references/

    Documents the AI agent reads when it needs more detail.

  • Assets

    assets/

    Templates, images, and data files are also listed with their paths and hashes.

  • Other files

    Folders and files not named in the specification are listed too.

  • Missing filesMissing

    Files mentioned in SKILL.md but absent from the folder are marked.

Versions

Every version stays available.

Every change after release becomes a new version. The previous files and hashes stay as they were, and the version you use is never replaced.

Versions are ordered by release date, each with a change record. Browse as far back as you need. People who follow the skill receive these records.

Five sheets fan out from one corner, with lime green in front, each sheet lighter than the last, and ivory at the back.

Version example

One skill,two dated versions.

Example: dates and content for chapter-cast. Each version fixes its files and hashes. A new version does not overwrite the previous one.

  • 1.1.0

    October 19, 2026. Adds rules for matching character aliases and includes the related reference file.

  • 1.0.0

    October 12, 2026. Records where characters first appear. The original files remain unchanged, and reviews and comments still refer to this version.

Packages

Required packages are listed as stated;unclear details are labeled.

  • Separate ecosystems

    Each package is listed under its ecosystem. Packages with the same name in different ecosystems are not treated as the same package.

  • Required and optional

    Each package is marked as required or optional.

  • Missing and unsupported

    Missing declarations and ecosystems outside the supported range are marked as missing or unsupported.

Every skill has a byline. Authors and maintainers are listed by role and linked to their other work and reviews.

Next page

Read its contents, then see who has used it.

Read a skill before giving it to an AI agent.