# Intrikata Topology — self-evolving knowledge graph platform > 39 Claude Code skills (+ commands and agents) from the live Intrikata Topology > plugin, packaged for discovery and installation by humans and agents. - Install (all paths): https://topology.intrikata.com/install.md - Machine-readable catalog: https://topology.intrikata.com/skills/index.json - Raw skill fetch: https://topology.intrikata.com/skills/.SKILL.md - Package: https://topology.intrikata.com/pkg/intrikata-topology-skills.zip - Git (dumb-HTTP, marketplace-addable): https://topology.intrikata.com/git/intrikata-topology-skills.git - Non-Claude-Code harnesses: https://topology.intrikata.com/AGENTS.md - Live graph API (read surfaces, proxied to origin): /api/* ## Skills - intrikata-topology:api-and-mcp-guide: This skill should be used when the user asks about Intrikata Topology's MCP tools, HTTP API endpoints, metagraph layers, observer chain, system health, knowledg - intrikata-topology:capabilities-guide: This skill should be used when a user needs to know what Intrikata Topology can do, how to use a specific capability, what tools are available, or needs guidanc - intrikata-topology:cloudflare-deployment: This skill should be used when working with Intrikata Topology's Cloudflare deployment, multi-tenant architecture, D1 databases, Worker configuration, user auth - intrikata-topology:cloudflare-deployment-validator: Use when validating that deployed Cloudflare Workers and Pages serve valid HTML/JS/CSS, diagnosing deployment failures, running post-deploy health checks, or ap - intrikata-topology:cloudflare-free-tier-optimization: Use when optimizing a Cloudflare Workers + D1 + R2 + Pages deployment for cost and performance within free tier limits - intrikata-topology:cloudflare-image-cache: Use when implementing image caching, proxying, or CDN optimization on Cloudflare - intrikata-topology:cloudflare-incident-response: Use when a Cloudflare Workers/Pages/D1 deployment is broken in production, returning errors, showing stale content, or behaving unexpectedly - intrikata-topology:cloudflare-pages-deploy: Use when deploying any static frontend project to Cloudflare Pages with optional backend tunnel - intrikata-topology:cloudflare-rss-aggregator: Use when building an RSS/Atom feed aggregator, news aggregation, content pipeline, or scheduled content ingestion on Cloudflare Workers - intrikata-topology:cloudflare-security-hardening: Use when securing a Cloudflare Workers/Pages/D1 deployment against attacks, adding rate limiting, input validation, CORS policy, Content Security Policy, SQL in - intrikata-topology:cloudflare-storage-decision-matrix: Use when choosing between Cloudflare D1, KV, R2, Durable Objects, or Cache API for a data storage need - intrikata-topology:cloudflare-worker-api-patterns: Use when building a REST API on Cloudflare Workers with D1 - intrikata-topology:cloudflare-zero-downtime-deploy: Use when deploying updates to Cloudflare Workers/Pages/D1 without downtime, managing gradual rollouts, blue-green deployments, safe database migrations, or roll - intrikata-topology:colorblind-safe-design: Use when choosing colors for maps, charts, legends, tags, badges, or any UI where color encodes meaning - intrikata-topology:css-theme-toggle: Use when adding light/dark mode toggle to a website, theming with CSS custom properties, handling product image backgrounds across themes, or building a persist - intrikata-topology:d1-migration-strategy: Use when managing Cloudflare D1 database schemas, running migrations, seeding data, importing from SQLite/PostgreSQL, or handling schema evolution - intrikata-topology:d1-query-performance: Use when D1 queries are slow, API responses take too long, optimizing database performance, understanding D1 query plans, creating indexes, tuning FTS5, or redu - intrikata-topology:datastore-enrichment: This skill should be used when improving a datastore by adding new graphs, expanding coverage, filling gaps in domain knowledge, assessing what a datastore is m - intrikata-topology:deployment-pipeline: This skill should be used when deploying Intrikata Topology to Cloudflare, running database migrations, syncing data between local and D1, validating deployment - intrikata-topology:graph-creation: This skill should be used when creating new knowledge graphs, filling graphs with content, enriching existing graphs, connecting orphan nodes, building ontologi - intrikata-topology:knowledge-graph-ops: Use when working with knowledge graphs - creating nodes, connections, analyzing structure, or building ontologies - intrikata-topology:megapraxis: Session-start bootstrap briefing - intrikata-topology:meta-caramello-bridges: META SKILL — Use when you've solved a problem in one part of a system and need to apply the same pattern elsewhere - intrikata-topology:metagraph-awareness: Use when Claude needs context about Intrikata Topology's own architecture, capabilities, or self-improvement system - intrikata-topology:metamegapraxis: Meta-orchestrator that audits and evolves megapraxis itself + the praxis stack (megapraxis + metamethodologist + ASEC + Fusion Complex) - intrikata-topology:metamethodologist-deployment-audit: Use BEFORE any other deployment skill - intrikata-topology:metamethodology-convergence: Sideload proxy (Pattern 3) for the metamethodology-convergence-agent - intrikata-topology:project-production-hardening: Use on ANY project (not just Cloudflare) to systematically harden it for production - intrikata-topology:purpose-and-value: This skill should be used when understanding what Intrikata Topology is for, what it does for users, how to maximize the value of knowledge graphs, when to use - intrikata-topology:self-perfection: This skill should be used when running self-improvement cycles, spawning new ops, balancing capabilities, expanding graphs, connecting orphan nodes, enriching k - intrikata-topology:serverless-spa-architecture: Use when building a full-stack web application entirely on Cloudflare with no servers - intrikata-topology:shadow-asset-integrity: SHADOW SKILL — Use when a site references files that don't exist: broken favicons, missing OG images, manifest icons 404, CSS/JS 404, broken image src attribute - intrikata-topology:shadow-data-quality: SHADOW SKILL — Use when database content is incomplete, user-facing fields are NULL, search returns no results, or seeded data doesn't cover all categories - intrikata-topology:shadow-image-proxy-bypass: SHADOW SKILL — Use when a project has a worker/edge image proxy with R2 cache (`/api/img?url=...` pattern) but some code path still emits direct third-party CDN - intrikata-topology:shadow-localstorage-resilience: SHADOW SKILL — Use when a web app uses localStorage/sessionStorage for state persistence, offline data, or caching - intrikata-topology:shadow-silent-failures: SHADOW SKILL — Use when code appears to work but produces no visible output, buttons hang, or features silently fail - intrikata-topology:shadow-todo-scanner: SHADOW SKILL — Use before any deployment to find TODO comments, placeholder text, hardcoded credentials, lorem ipsum, example.com URLs, and other pre-launch deb - intrikata-topology:universal-introspection: This skill should be used when applying the Self-Introspecting Meta Graph pattern to any graph, making graphs self-aware, generating META/SHADOW layers for user - intrikata-topology:wix-migration-convergence: Sideload proxy (Pattern 3) for the wix-migration-convergence-agent