morphiq-track
Pipeline Position
Step 4 of 4 — measurement + flywheel.
- Input: Build Output (JSON) from morphiq-build + MORPHIQ-TRACKER.md (persistent state).
- Output: Delta Report (JSON) → loops back to morphiq-rank.
- Owns: MORPHIQ-TRACKER.md — generates on first run, updates every run.
- Owns:
morphiq-track/state directory — JSON state layer for prompts, results, citations. - Drives: 3 ongoing workflows (Content Optimization, Content Creation, Query Fanout Expansion).
- Data contract: See
PIPELINE.md§4 for the Delta Report, §5 for MORPHIQ-TRACKER.md, §6 for the JSON State Layer.
Purpose
Morphiq Track is the measurement and flywheel skill. It queries AI providers to measure brand visibility, computes GEO scores and Share of Voice, tracks deltas over time, and drives three ongoing workflows that feed back into the pipeline.
Workflow
Step 0: Initialize or Load State
Check if morphiq-track/manifest.json exists in the project root.
More from morphiqlabs/morphiq-labs-skills
morphiq-scan
This skill should be used when the user asks to "audit a website for AI visibility", "scan a domain", "check AI readiness", "evaluate content quality", "run a Morphiq Scan", "check if a site is optimized for LLMs", or mentions scanning a website for LLM citation readiness. Performs a full AI visibility audit across 5 categories (agentic readiness, content quality, chunking & retrieval, query fanout, policy files) and scores the domain on a 100-point rubric.
9morphiq-rank
This skill should be used when the user asks to "create issues from a scan", "prioritize what to fix", "rank the issues", "build a roadmap from scan results", "run Morphiq Rank", or mentions creating a prioritized roadmap from scan results. Consumes a Morphiq Scan Report, applies issue creation criteria with impact/effort weighting, and organizes issues into 4 progressive discovery tiers.
9morphiq-build
This skill should be used when the user asks to "fix the issues", "optimize existing content", "create new content for AI visibility", "run Morphiq Build", "generate schema markup", "create an llms.txt file", "run the content lab", or mentions building content fixes, generating schema, rewriting content for AI citations, or creating policy files. Consumes a Prioritized Roadmap (or user prompt, or existing content) and produces build artifacts through a 6-step content lab pipeline.
9