changed to skill provider

docs/contracts/skill_contract.md

@@ -40,9 +40,9 @@ Rules:
 
 ## Metadata Location Constraint
 
-1. Skill metadata is embedded in YAML frontmatter in `SKILL.md`.
-2. No `metadata.yaml` sidecar exists in the end state.
-3. Reference lookup metadata is documented and explicit: top-level `references/*.md` are auto-discovered from filenames, while `SKILL.md` frontmatter declares overrides and nested mappings when needed.
+1. `SKILL.md` frontmatter contains only standard `name` and `description` fields.
+2. No `metadata.yaml` sidecar or repository-specific skill metadata block exists.
+3. The provider discovers supporting files recursively; their real relative paths are published in the generated `_manifest`.
 
 ## Skill Id Contract
 
@@ -52,8 +52,8 @@ Rules:
 2. Character set: `a-z`, `0-9`, and `-`.
 3. Must start with a letter.
 4. No underscores, spaces, dots, or uppercase characters.
-5. Directory name should equal `skill-id` in each committed revision.
-6. Frontmatter `id` should equal directory name in each committed revision.
+5. Directory name equals `skill-id` in each committed revision.
+6. Frontmatter `name` equals the directory name.
 7. Treat `skill-id` as immutable after release; any rename is a breaking replacement and clients must move to the new id.
 
 Valid examples:
@@ -68,6 +68,16 @@ Invalid examples:
 2. `Zensical-Docs`
 3. `docs.zensical`
 
+## Provider Publication
+
+[`SkillsDirectoryProvider`](https://gofastmcp.com/servers/providers/skills) scans `docs/skills/` with `supporting_files="template"` and publishes:
+
+1. `skill://<skill-id>/SKILL.md`
+2. `skill://<skill-id>/_manifest`
+3. `skill://<skill-id>/{path*}` for supporting files
+
+Only the main file and manifest appear in `resources/list`. Clients inspect the manifest before reading supporting paths.
+
 ## Direct Documentation Inclusion
 
 1. For direct API documentation, use mkdocstrings directives rather than pasting large code blocks.