ct-metrics-store

Store and query time-series SEO metrics in a persistent SQLite database.

Updated Jan 24, 2026
One-click install
npx skills add https://github.com/jamiegrand/cleo-web --skill ct-metrics-store
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ct-metrics-store
Source: https://github.com/jamiegrand/cleo-web/tree/main/skills/ct-metrics-store
Command: npx skills add https://github.com/jamiegrand/cleo-web --skill ct-metrics-store

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stores and organizes SEO performance data over time to enable reliable historical analysis and trend discovery.

Core Features & Use Cases

  • Audit history storage and retrieval for page-level performance over time.
  • Keyword cache with TTL to accelerate keyword research workflows.
  • GSC snapshot storage for trend analysis and comparative reporting.
  • Use Case: Track monthly audit scores for a key landing page to identify improvements over a quarter.

Quick Start

Initialize the metrics store and begin recording your first audit result for a page.

Frequently Asked Questions about ct-metrics-store

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I store SEO time-series metrics for historical trend analysis?

Store SEO time-series metrics by writing page-level audit results, keyword data, and GSC snapshots into a persistent SQLite database. This enables reliable historical analysis and trend discovery through automatic timestamp indexing.

What is the best way to maintain a local keyword cache and audit history?

Maintaining a local keyword cache and audit history involves storing time-series data in a persistent SQLite database with batched writes. This approach organizes performance data over time to accelerate keyword research workflows.

How do I record Google Search Console snapshots for comparative reporting?

Record GSC snapshots by writing them into a defined SQLite schema that automatically applies timestamp indexing. This stores your performance data over time to enable comparative reporting and trend analysis.

Do I need a local SQLite environment to track page-level audit scores?

Yes, tracking page-level audit scores requires a local SQLite environment. The system uses a defined schema with batched writes and automatic timestamp indexing to store audit_results, keyword_cache, and gsc_snapshots efficiently.

Can SQLite handle batched writes for ongoing site audit data?

Yes, SQLite handles batched writes for ongoing site audit data by using a defined schema to store time-series metrics. This enables historical audits and trend analysis across multiple pages over time.