Add the ttg-ops plugin: six skills for the forge estate
The marketplace held only MCP servers so far. These are skills for the work that keeps costing manual effort and quietly breaking: - ttg-publish-module — releasing a library, and verifying from a clean external project that the release is actually fetchable. Encodes the trap that cost the most: Gitea redirects old repo paths, but not Go module paths, so a repo can be reachable while `go get` fails. - ttg-move-repo — moving a repo and following it through every place that names it, including the ones redirects do not cover. - ttg-new-repo — creating one in the right org and registering it, so it cannot end up absent from the clone list the way batocera-store did. - ttg-ci-enroll — wiring a repo into the build, and the usual failure where the config exists but the repo was never registered. - ttg-audit-forge — the drift check between forge, clone list, wiki, catalog and CI. - ttg-update-docs — README, wiki page and the public site (Vue page plus both locale files) after a change. The rules stay in REPO_REFACT.md, WIKI_CONNECTION.md and ECOSYSTEM_PLAN.md; the skills read them instead of carrying a second copy that drifts. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -1,9 +1,10 @@
|
||||
# TTG Marketplace
|
||||
|
||||
Claude Code plugin marketplace with two plugins:
|
||||
Claude Code plugin marketplace with three plugins:
|
||||
|
||||
- **redmine-mcp** — dependency-free Node.js MCP server for the [Redmine REST API](https://www.redmine.org/projects/redmine/wiki/rest_api)
|
||||
- **grav-mcp** — dependency-free Node.js MCP server for the [Grav CMS REST API](https://learn.getgrav.org/20/api/endpoints)
|
||||
- **ttg-ops** — skills for running the forge estate: releasing libraries, moving and creating repos, enrolling CI, auditing consistency, and updating the docs after a change
|
||||
|
||||
## Installation
|
||||
|
||||
@@ -11,6 +12,7 @@ Claude Code plugin marketplace with two plugins:
|
||||
/plugin marketplace add /Users/tasi/Work/TTG/ttg-marketplace
|
||||
/plugin install redmine-mcp@ttg-marketplace
|
||||
/plugin install grav-mcp@ttg-marketplace
|
||||
/plugin install ttg-ops@ttg-marketplace
|
||||
```
|
||||
|
||||
(From a git repo: `/plugin marketplace add <git-url>`.)
|
||||
@@ -63,9 +65,28 @@ Settings requested at install time:
|
||||
|
||||
**Other:** `grav_scheduler` (jobs, status, history, run), `grav_dashboard` (stats, popularity, notifications), `grav_manage_webhooks`, flex objects: `grav_list_flex`, `grav_get_flex_object`, `grav_save_flex_object`, `grav_delete_flex_object`
|
||||
|
||||
## ttg-ops
|
||||
|
||||
No settings — the skills drive the tools that are already on the machine: the
|
||||
`tea` CLI (Gitea API, login `ttg`), `git`, `go` and `gem`.
|
||||
|
||||
| Skill | What it does |
|
||||
|---|---|
|
||||
| `ttg-publish-module` | Releases a library: checks the module path against the repo's org, tags, and verifies from a clean external project that the release is fetchable. Knows that Gitea's redirect does **not** cover Go module paths or package namespaces. |
|
||||
| `ttg-move-repo` | Moves or renames a repo and follows the change through: clone list, local remotes, wiki links and link text, `go.mod`, `Gemfile`, CI config, docs. |
|
||||
| `ttg-new-repo` | Creates a repo in the right org and registers it everywhere — clone list, `WIKI_CONNECTION.md`, wiki page, CI. Includes the org/team setup a new org needs. |
|
||||
| `ttg-ci-enroll` | Wires a repo into the Woodpecker build and proves it runs. Covers the usual failure: the config is there, the repo is not registered, nothing happens silently. |
|
||||
| `ttg-audit-forge` | Audits drift between forge, clone list, wiki, catalog and CI. Reports first, fixes only on approval. |
|
||||
| `ttg-update-docs` | After a change, updates the README of the repo that changed, its wiki page in `wiki-pages`, and the public site in `teletypegames` (Vue page plus **both** locale files). |
|
||||
|
||||
The rules these skills follow are not duplicated inside them: the org taxonomy
|
||||
lives in `REPO_REFACT.md`, the repo→wiki mapping in `devarea/WIKI_CONNECTION.md`,
|
||||
and the ecosystem status in `ECOSYSTEM_PLAN.md`, all in the workspace root. The
|
||||
skills read those rather than carry a second copy that drifts.
|
||||
|
||||
## Notes
|
||||
|
||||
- Neither server has any npm dependencies (Node 18+ built-in `fetch`), and there is no build step.
|
||||
- Neither MCP server has any npm dependencies (Node 18+ built-in `fetch`), and there is no build step.
|
||||
- Manual testing without the plugin:
|
||||
```sh
|
||||
REDMINE_URL=https://redmine.example.com REDMINE_API_KEY=xxx \
|
||||
|
||||
Reference in New Issue
Block a user