analytics-repo-pruning
Flag archived or inactive repos in PatternFly Analytics repos.json for removal. Use when auditing tracked codebases or pruning stale entries from analytics.
What this skill does
# Analytics repo pruning Keep PatternFly Analytics from tracking **archived** repositories and repos with **no meaningful code activity** past a configurable threshold (default **730 days**). ## Plugin placement This skill lives under **pf-workshop** as **cross-repo / analytics inventory** work (repository health and maintenance). ## Input - **File:** `repos.json` (project root or path the user supplies). Expect a top-level `repos` array; each entry has `git` (clone URL) and `name` (display label). ## Outcomes For every row, assign one bucket: | Bucket | Meaning | |--------|---------| | **archived** | Host marks the project archived / read-only | | **stale** | Last code activity is before the cutoff | | **could not verify** | Auth failure, network, or unsupported host—**not** the same as stale | | **active** | Neither archived nor stale | Use the host’s best signal for **real code activity** (e.g. last push to the default branch), not noisy metadata-only updates. Field names and API notes: [reference.md](reference.md). ## How to work 1. Read `repos.json` and collect all `git` URLs with their `name`. 2. For each URL, determine host (**GitHub**, **GitLab** including private instances, or other). 3. Query the host using **whatever authenticated access the user’s environment already provides** (host CLI, REST with tokens, etc.). Prefer a deterministic per-repo lookup; if one path fails, try another before giving up. 4. Do **not** treat auth or network failures as “stale”—bucket those as **could not verify** with a short reason. 5. Produce the report below. **Do not** remove or edit `repos.json` entries unless the user explicitly asks. ## Edge cases - **404 / moved / renamed:** Flag for manual verification; do not assume delete. - **Forks and mirrors:** Same rules; stale mirrors may still be poor analytics targets. - **Unknown hosts:** **could not verify** with explanation—not stale. ## Optional script For a repeatable local run, execute the bundled **Bash** script `scripts/analytics-repo-pruning.sh` next to this skill. Requires `jq` and either `gh` or `curl` (typically pre-installed). Pass the path to `repos.json`; optional `--days <n>` and `--json`. Does not modify `repos.json`. ## Report format Use markdown with: 1. **Threshold** (days) and **run date** 2. **Archived** — table: name, git, notes 3. **Stale** — table: name, git, last activity (and which field was used) 4. **Could not verify** — table: name, git, reason 5. **Active** — brief count or one-line summary **Good output:** Clear buckets, honest “unknown,” timestamps tied to named fields, no silent edits to the JSON file. **Bad output:** Calling repos stale because API calls failed, or pruning the list without explicit user consent. ## Additional resources - [reference.md](reference.md) — host APIs, fields, encoding, and CLI patterns
Related in Data & Analytics
clawarr-suite
IncludedComprehensive management for self-hosted media stacks (Sonarr, Radarr, Lidarr, Readarr, Prowlarr, Bazarr, Overseerr, Plex, Tautulli, SABnzbd, Recyclarr, Unpackerr, Notifiarr, Maintainerr, Kometa, FlareSolverr). Deep library exploration, analytics, dashboard generation, content management, request handling, subtitle management, indexer control, download monitoring, quality profile sync, library cleanup automation, notification routing, collection/overlay management, and media tracker integration (Trakt, Letterboxd, Simkl).
querying-soql
IncludedSOQL query generation, optimization, and analysis with 100-point scoring. Use this skill when the user needs SOQL/SOSL authoring or optimization: natural-language-to-query generation, relationship queries, aggregates, query-plan analysis, and performance or safety improvements for Salesforce queries. TRIGGER when: user writes, optimizes, or debugs SOQL/SOSL queries, touches .soql files, or asks about relationship queries, aggregates, or query performance. DO NOT TRIGGER when: bulk data operations (use handling-sf-data), Apex DML logic (use generating-apex), or report/dashboard queries.
app-store-optimization
IncludedApp Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklists, and tracking ranking changes.
habit-flow
IncludedAI-powered atomic habit tracker with natural language logging, streak tracking, smart reminders, and coaching. Use for creating habits, logging completions naturally ("I meditated today"), viewing progress, and getting personalized coaching.
app-store-optimization
IncludedApp Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklists, and tracking ranking changes.
visualizing-data
IncludedBuilds dashboards, reports, and data-driven interfaces requiring charts, graphs, or visual analytics. Provides systematic framework for selecting appropriate visualizations based on data characteristics and analytical purpose. Includes 24+ visualization types organized by purpose (trends, comparisons, distributions, relationships, flows, hierarchies, geospatial), accessibility patterns (WCAG 2.1 AA compliance), colorblind-safe palettes, and performance optimization strategies. Use when creating visualizations, choosing chart types, displaying data graphically, or designing data interfaces.