*3. Different philosophy*
- *agentskills.io* = Instructions for agents to read and interpret
- *Enact* = Executable package manifest with Docker images, typed I/O schemas, and containerized execution
*Bottom line:* Enact borrows the SKILL.md filename but extends it into something fundamentally different — a package manager format rather than an agent instruction format. It's not spec-compliant; it's a conceptual fork.
I made enact independently and realized how similar it was to skills when they were released, so tried to go with the flow rather than ask people to understand yet another new concept. Enact.md -> Skill.md
Not really sure what the path forward is but this feedback is very helpful.
## Enact vs agentskills.io Spec — Key Differences
*1. Invalid `name` format* - Spec allows only: lowercase letters, numbers, hyphens (`my-skill`) - Enact uses: namespaced names with slashes (`enact/hello-python`)
*2. Non-standard frontmatter fields* - Spec defines: `name`, `description`, `license`, `compatibility`, `metadata`, `allowed-tools` - Enact adds proprietary fields: `version`, `from`, `build`, `command`, `inputSchema`, `outputSchema`
*3. Different philosophy* - *agentskills.io* = Instructions for agents to read and interpret - *Enact* = Executable package manifest with Docker images, typed I/O schemas, and containerized execution
*4. Directory structure* - Spec expects: `scripts/`, `references/`, `assets/` subdirectories - Enact allows: arbitrary files (`main.py`, `requirements.txt`)
*Bottom line:* Enact borrows the SKILL.md filename but extends it into something fundamentally different — a package manager format rather than an agent instruction format. It's not spec-compliant; it's a conceptual fork.