cf-analytics

Solid

Render an ASCII analytics dashboard of ContentForge production history — quality score trends, phase-by-phase pipeline timing, brand and content-type comparisons, compliance and citation metrics, outlier detection, and triggered alerts over a 7/30/90-day window. Triggers on "/contentforge:cf-analytics", "are our quality scores improving", "which pipeline phase is slowest", "show content production stats", "compare brands by quality". Reads tracking records written by Phase 8 to the brand's tracking backend (local JSON, Google Sheets, or Airtable) and alert rules from config/analytics-config.json; needs 10+ tracked pieces for meaningful trends. Analysis only — invokes no agents and never reads or stores content text.

AI & Automation 28 stars 5 forks Updated 3 weeks ago MIT

Install

View on GitHub

Quality Score: 84/100

Stars 20%
49
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Content Analytics Dashboard Track ContentForge production quality, pipeline timing, brand-specific patterns, and compliance trends over configurable time periods with automated insights and alert flags. ## When to Use Use `/contentforge:cf-analytics` when you need: - **Quality trend visibility** — Are scores improving or declining over time? - **Pipeline performance audit** — Which phases are slowest? Where are bottlenecks? - **Brand comparison** — Which brands consistently score highest/lowest? - **Content type analysis** — Are articles scoring better than whitepapers? - **Compliance monitoring** — Citation rates, brand adherence, loop frequency - **Capacity planning** — Average throughput for estimating batch timelines **For real-time batch monitoring**, use the Progress Tracker (built into `/contentforge:batch-process`). **For individual content production**, use [`/contentforge:create-content`](../../commands/create-content.md). ## What This Command Does Loads historical production data from the brand's configured tracking backend (Google Sheets, Airtable, or local — see `tracking.backend` in the brand profile), calculates aggregate metrics across configurable dimensions, identifies statistical outliers and concerning trends, generates an ASCII dashboard with actionable recommendations, and flags alerts when performance degrades. **Process Flow:** 1. **Load Data** — Read tracking records from the brand's tracking backend (Google Sheets / Airtable / local JSON) 2...

Details

Author
indranilbanerjee
Repository
indranilbanerjee/contentforge
Created
6 months ago
Last Updated
3 weeks ago
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Listed

cf-analytics

Render an ASCII analytics dashboard of ContentForge production history — quality score trends, phase-by-phase pipeline timing, brand and content-type comparisons, compliance and citation metrics, outlier detection, and triggered alerts over a 7/30/90-day window. Triggers on "/contentforge:cf-analytics", "are our quality scores improving", "which pipeline phase is slowest", "show content production stats", "compare brands by quality". Reads tracking records written by Phase 8 to the brand's tracking backend (local JSON, Google Sheets, or Airtable) and alert rules from config/analytics-config.json; needs 10+ tracked pieces for meaningful trends. Analysis only — invokes no agents and never reads or stores content text.

1 Updated 3 weeks ago
teachskillofskills-ai
AI & Automation Solid

cf-audit

Audit an existing content library for freshness decay and coverage gaps — scores every piece 0-100 on age, statistic currency, link health, and citation recency, maps covered topics against target keywords, and produces a prioritized report: top refresh candidates, gap topics, retire candidates, and the exact follow-up commands. Triggers on "/contentforge:cf-audit", "which content needs refreshing", "content health check", "what topics are we missing", "audit our blog library". Reads inventory from a Google Drive folder, WordPress REST API, or CSV; pulls performance data only if Google Analytics/Search Console MCPs are connected. Audit only — refreshing happens via /contentforge:content-refresh and new pieces start at /contentforge:cf-brief.

28 Updated 3 weeks ago
indranilbanerjee
Data & Documents Listed

cf-audit

Audit an existing content library for freshness decay and coverage gaps — scores every piece 0-100 on age, statistic currency, link health, and citation recency, maps covered topics against target keywords, and produces a prioritized report: top refresh candidates, gap topics, retire candidates, and the exact follow-up commands. Triggers on "/contentforge:cf-audit", "which content needs refreshing", "content health check", "what topics are we missing", "audit our blog library". Reads inventory from a Google Drive folder, WordPress REST API, or CSV; pulls performance data only if Google Analytics/Search Console MCPs are connected. Audit only — refreshing happens via /contentforge:content-refresh and new pieces start at /contentforge:cf-brief.

1 Updated 3 weeks ago
teachskillofskills-ai