GitHub collection
jsonbored/metagraphed
Imported from GitHub — is this yours?
6 skills imported from this repository.
contributor-pipeline-gardening
Maintenance of the contributor issue pipeline for JSONbored/metagraphed — closing issues that are already done but not marked so, and keeping the contributor-available backlog at its 50-100+ steady-state floor with well-scoped new issues. Runs every ~8h via the scheduled task (ra
error-tracking-upload-source-maps-vite
Upload source maps to PostHog Error Tracking for Vite
frontend-visual-qa
Systematic visual QA sweep of the live metagraphed frontend (apps/ui, served at metagraph.sh) — actually browsing pages at real viewports and looking for defects only visible on inspection (crowding, overflow, truncation, misalignment), not catchable by reading code or trusting a
mcp-analytics
Add PostHog MCP analytics to a TypeScript, JavaScript, or Python MCP server. Instruments the server so every tool call, agent intent, and failure is captured as a $mcp_* event — the @posthog/mcp Node SDK for TS/JS, or posthog.mcp (shipped inside the posthog package) for Python. D
metagraphed
Use when writing, validating, or preparing ANY contribution or pull request to the JSONbored/metagraphed repo — adding/enriching a subnet's public surfaces (the most common contribution), a code/schema change to the Worker API or build scripts, picking an issue, running the local
bittensor
Use when a developer asks what a Bittensor subnet does, whether it's up right now, how to call/integrate its API, or what mining/validating one costs and earns — e.g. "which subnet does image generation", "is subnet 7 healthy", "call the Beam API for me", "does mining subnet 3 ne
Commands (1)
-
/lineage-discovery— Discover testnet↔mainnet subnet lineage from repo configs and open a PR for review (pass --dry-run to report only) source