Reading order
Read a skill in three layers,in the order an AI agent does.
Example: a skill that organizes chapter characters. Read its name and description first, then the full instructions, and finally the files needed for the task. Skill Hub presents them in the same order.
One line
The chapter-cast description says, “List the characters in a chapter with passage locations.” The agent reads this first to decide whether the skill fits the task.
One page
SKILL.md says, “List characters and aliases first, then include the source location. Mark anything without a source as not found.” The agent reads these steps and limits when the task involves organizing characters.
Files used
references/aliases.md lists the format for matching characters, aliases, and source locations. The agent reads this reference file only when it needs to compare aliases. Other files remain listed alongside it.
Files
Every file is listed,and executable files are marked.
Every file in SKILL.md, scripts/, references/, assets/, and any folders not named in the specification has a recorded path, role, and hash. Files mentioned in SKILL.md but missing from the folder are marked too.

An index is not an endorsement. Read the full text and files before deciding. REZICS stores skills when they are imported and does not run their instructions.
This site
From finding a skillto publishing your own.
Connected to
A skill is text and files;its dependencies have their own pages.
Packages declared by a skill have their own versions in software. A creator’s skills and MCP servers link to the same identity. The local REZICS Wiki toolkit also includes a skill that guides AI agents in proposing sourced facts from books and visual novels.
Start with one line.
Search for a skill on REZICS. Read its full text, files, and records before giving it to your AI agent.
