Defame1297
60be7b3232
Only 12 of 39 skills carried metadata.version, and adoption tracked which plugin a skill lived in rather than any stated rule: core, gitea and lint were consistent adopters, bin and kyberforge were consistent non-adopters, git was split with one outlier. There was no documented convention, and skill-author's own bump logic was already written as if presence were conditional. metadata.version is now required on every skill. The 19 skills here that never carried one (bin, kyberforge, gitea-files) are seeded at 1.0.0, not 0.1.0 -- that value stays reserved for a skill's actual creation point under skill-author's existing convention. The skill-frontmatter pre-commit hook now fails a SKILL.md missing the field, the same class of failure as a missing name/description. Full rationale in the new ADR. The git-plugin skills that also need this field follow in the next commit, bundled with issue #113's rtk normalization since both touch the same files. Refs: #127 ADR: 0022 Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EeH8SCbcrCAQrtymkNuhKP
gitea-files
Read and write individual files and directory/repository trees in a Gitea repository via the Gitea MCP server.
What it does
This skill handles file-domain operations within the Gitea integration suite: reading a single file's contents, listing one directory level, walking a full repository tree (optionally recursive), creating or updating a file, and deleting a file. It owns the SHA-based optimistic-concurrency pattern that Gitea requires for file writes — the domain's sharpest gotcha — and defers branch creation, commit history, and pull request mechanics to gitea-branches and gitea-prs.
Usage
/gitea-files
Describe the file task: read a file or directory, walk a tree, create/update a file, or delete a file. Provide owner/repo/branch (or ask the user if not given) — this skill does not resolve them from a git remote itself.
Files
| File | Purpose |
|---|---|
SKILL.md |
Skill instructions for agents |
references/reading.md |
Loaded for the read flow: the three read tools, ref/tree_sha selection, tree pagination, and why a listing is not a SHA source |
references/writing.md |
Loaded for the write flow: the SHA-first create/update/delete sequences, new_branch_name, the worked branch + file + PR sequence, and failed-write triage |
references/sources.md |
Research sources backing the SHA/concurrency and direct-commit-vs-PR guidance |