MCP server for active-claude-github skill — GitHub operations layer
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"active-claude-github-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# claude-skills-mcp-dev Private dev repo for the [`active-claude-github`](https://github.com/telejester-claude-skills/telejester-claude-skills) Claude Code skill's MCP server. Consumer docs live at the publish target: <https://github.com/telejester-claude-skills/claude-skills-mcp>. This repo is where MCP server development happens — Issues, Discussions, CI, Bazel build graph, tests. Releases are published to the publish-target repo linked above. ## What lives here - **Python package** `active_claude_github_mcp/` implementing the MCP tool surface. - **`tests/`** — Bazel-orchestrated unit and integration tests in two layers: helper-level (#79, ephemeral repos) and tool-level (#89, persistent fixture repo at `telejester-test-org/integration-fixture`). See [`CONTRIBUTING.md`](CONTRIBUTING.md) for the build and test conventions and §Persistent fixture repo for the provisioning protocol. - **`.github/workflows/`** — CI (`bazel test` + `bazel coverage` on every PR; `workflow_dispatch` live-GitHub integration tests). - **Issues / Discussions / Project board** cross-referenced with the skill dev repo at <https://github.com/orgs/telejester-claude-skills/projects/1>. ## Bootstrapping a new project `scaffold_project` is the MCP tool that stands up a new managed project end-to-end: creates the `<org>/<name>` public + `<org>/<name>-dev` private repo pair, seeds the standard label set, enables Discussions on the dev repo, creates a ProjectV2 board (linked to both repos) with the canonical `Backlog → In Progress → In Review → Done / Parked` Status field, seeds the Project and Session-Lock Discussions, and writes `.claude/github-config.json` with every resolved ID. The tool is idempotent and pauses for exactly one manual step: creating the five Discussion categories (`Project`, `Architecture`, `UX / UI`, `Ideas`, `claude-use-only`) via the dev-repo's Settings page, which GitHub exposes no API for. Re-run the tool once the categories exist and it picks up wh…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.