Agent skill

Denormalized Priority Column Staleness

by divinevideo in divinevideo/divine-mobile

Fix incorrect priority ordering when using denormalized aggregate columns.

MPL-2.0Auto-check passedDevelopment

Install Denormalized Priority Column Staleness

skills CLI
$ npx skills add divinevideo/divine-mobile --skill denormalized-priority-column-staleness -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install divinevideo/divine-mobile denormalized-priority-column-staleness --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/divinevideo/divine-mobile.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/denormalized-priority-column-staleness .claude/skills/denormalized-priority-column-staleness && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
denormalized-priority-column-staleness
GitHub stars
266
Token cost
~1.2k tokens
SKILL.md length
345 words
Files
1
Skills in repo
103
Repo updated
First seen
Licence
MPL-2.0

At a glance

Fix incorrect priority ordering when using denormalized aggregate columns.

  • Works in 4 steps: Initial data migration didn't populate… → Backfill scripts only ran for some records → New source records were added without… → …
  • Records are processed in wrong order despite ORDER BY on count/sum columns
  • SKILL.md covers Problem, Context / Trigger Conditions, Root Cause and Solution, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Denormalized Priority Column Staleness is an agent skill from divinevideo/divine-mobile. Fix incorrect priority ordering when using denormalized aggregate columns. Use when: (1) Records are processed in wrong order despite ORDER BY on count/sum columns, (2) Top items by some metric aren't being selected first, (3) Aggregate columns show 0 or NULL for records that should have high values, (4) Priority queue processes low-value items before high-value ones. The root cause is often that denormalized columns (vinecount, loopcount, totalorders, etc.) weren't backfilled or maintained properly. Solution…

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Root cause analysis. The licence is MPL-2.0.

When your agent uses it

  • Records are processed in wrong order despite ORDER BY on count/sum columns
  • Top items by some metric arent being selected first
  • Aggregate columns show 0
  • NULL for records that should have high values

Example prompts

  • “/denormalized-priority-column-staleness”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Initial data migration didn't populate them
  2. Backfill scripts only ran for some records
  3. New source records were added without updating the denormalized column
  4. The aggregation logic changed but the column wasn't recalculated

What it can do on your machine

Read from SKILL.md and the folder at commit c3d6f7e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are sql).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Denormalized Priority Column Staleness loads about 1.2k tokens when it runs. Until then it costs about 156 tokens; SKILL.md has 345 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~156
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from divinevideo/divine-mobile at commit c3d6f7e, republished under its MPL-2.0 licence (© divinevideo). 345 words, ~1,237 tokens.

Download SKILL.mdSave it as .claude/skills/denormalized-priority-column-staleness/SKILL.md (or your agent's skills folder).
name
denormalized-priority-column-staleness
description
Fix incorrect priority ordering when using denormalized aggregate columns. Use when: (1) Records are processed in wrong order despite ORDER BY on count/sum columns, (2) Top items by some metric aren't being selected first, (3) Aggregate columns show 0 or NULL for records that should have high values, (4) Priority queue processes low-value items before high-value ones. The root cause is often that denormalized columns (vine_count, loop_count, total_orders, etc.) weren't backfilled or maintained properly. Solution: JOIN with source tables to compute actual aggregates at query time.
author
Claude Code
version
1.0.0
date
2026-01-28

Denormalized Priority Column Staleness

Problem

When ordering records by denormalized aggregate columns (like total_loops, vine_count, order_count), the query returns items in the wrong priority order because the denormalized values are stale, unpopulated, or incorrect.

Context / Trigger Conditions

  • A batch job processes items in unexpected order
  • Top items (by some aggregate metric) are processed last or skipped
  • ORDER BY aggregate_column DESC doesn't return expected results
  • Aggregate columns show 0 or NULL for records that should have high values
  • Only a subset of records have the aggregate column populated
  • Backfill scripts may have run for some records but not others

Root Cause

Denormalized columns (copies of aggregated data stored for query performance) can become stale when:

  1. Initial data migration didn't populate them
  2. Backfill scripts only ran for some records
  3. New source records were added without updating the denormalized column
  4. The aggregation logic changed but the column wasn't recalculated

Solution

Option 1: Compute at Query Time (Immediate Fix)

Join with the source table to compute actual aggregates:

sql
-- BEFORE (broken): Uses potentially stale denormalized column
SELECT user_id, username
FROM users
WHERE status = 'pending'
ORDER BY total_loops DESC NULLS LAST;

-- AFTER (fixed): Computes actual aggregate from source
SELECT u.user_id, u.username,
       COALESCE(SUM(vm.loops), 0) as actual_total_loops
FROM users u
LEFT JOIN vine_metadata vm ON u.user_id = vm.user_id
WHERE u.status = 'pending'
GROUP BY u.user_id, u.username
ORDER BY actual_total_loops DESC;
Option 2: Backfill the Denormalized Column (Permanent Fix)

Update the denormalized column from the source data:

sql
UPDATE users u
SET total_loops = subq.actual_loops
FROM (
    SELECT user_id, COALESCE(SUM(loops), 0) as actual_loops
    FROM vine_metadata
    GROUP BY user_id
) subq
WHERE u.user_id = subq.user_id;
Option 3: Use Materialized Views (Best of Both)

Create a materialized view for the aggregates:

sql
CREATE MATERIALIZED VIEW user_stats AS
SELECT user_id,
       COUNT(*) as item_count,
       SUM(loops) as total_loops
FROM vine_metadata
GROUP BY user_id;

-- Refresh periodically
REFRESH MATERIALIZED VIEW user_stats;

Verification

After applying the fix, verify the query returns expected results:

sql
-- Check that top items are actually top items
SELECT user_id, username, actual_total_loops
FROM (your_fixed_query)
LIMIT 10;

-- Compare against direct aggregate
SELECT user_id, SUM(loops) as loops
FROM source_table
GROUP BY user_id
ORDER BY loops DESC
LIMIT 10;

Example

Scenario: Avatar fetcher should process top Viners first (by total loops), but instead processes users with ID prefix "10" (effectively random order).

Investigation:

sql
-- Check if denormalized column is populated
SELECT
    COUNT(*) as total,
    SUM(CASE WHEN loop_count > 0 THEN 1 ELSE 0 END) as has_loop_count
FROM users;
-- Result: Only 29,878 of 119,785 users have loop_count populated

-- Check top users by denormalized vs actual
SELECT u.user_id, u.username, u.loop_count as denormalized,
       SUM(vm.loops) as actual
FROM users u
JOIN vine_metadata vm ON u.user_id = vm.user_id
GROUP BY u.user_id, u.username, u.loop_count
ORDER BY SUM(vm.loops) DESC
LIMIT 5;
-- Result: Top creators show loop_count=0 but actual=1,281,730,353

Fix: Changed the query to JOIN with vine_metadata and ORDER BY the computed sum.

Notes

  • This is a classic denormalization trade-off: faster reads vs. stale data
  • When denormalizing, always implement triggers or application-level updates to keep in sync
  • Consider whether the aggregate query is fast enough to compute at runtime
  • LEFT JOIN ensures records without source data still appear (with 0 values)
  • Use COALESCE(SUM(...), 0) to handle NULL aggregates properly
  • NULLS LAST in ORDER BY prevents NULL values from sorting first in DESC order
  • Event sourcing: Keep source events, compute aggregates as needed
  • CQRS: Separate read models that are explicitly updated
  • Triggers: Automatically update denormalized columns on source changes

© divinevideo, MPL-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/denormalized-priority-column-staleness of divinevideo/divine-mobile.

Open the folder on GitHubat commit c3d6f7e

Compare with similar skills

Denormalized Priority Column Staleness next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Denormalized Priority Column Staleness compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Denormalized Priority Column Staleness this skilldivinevideo/divine-mobile266—~1.2kAutomated safety check: PassMPL-2.0
Code Design Rationale Investigatorcursor/plugins11k9 repos~2.6kAutomated safety check: PassNone
OpenLogi macOS Permissions TriageAprilNEA/OpenLogi23k—~2.5kAutomated safety check: NotesApache-2.0
Bug Finder for daisyUIsaadeghi/daisyui43k—~2.3kAutomated safety check: PassMIT
Root Cause Debugginggarrytan/gstack136k—~1.4kAutomated safety check: PassMIT
Review PRapache/shardingsphere21k—~6.4kAutomated safety check: PassApache-2.0

Similar skills

  • Official

    Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.

    11k GitHub starsUsed in 9 repos~2.6k tokens
    DevelopmentAuto-check passed
  • Decides whether an OpenLogi device problem on macOS is a privacy-permission (TCC) problem, using agent log lines, and says which identity needs which grant.

    23k GitHub stars~2.5k tokensUpdated today
    DevelopmentAuto-check: notes
  • Bug Finder for daisyUI

    saadeghi/daisyui

    Investigates suspected bugs in the daisyUI monorepo through read-only analysis, then writes a decision-ready fix plan in tmp/bugs without changing any product code.

    43k GitHub stars~2.3k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Root Cause Debugging

    garrytan/gstack

    Investigates bugs, errors and stack traces in phases and requires a root-cause hypothesis to be confirmed before any fix is written.

    136k GitHub stars~1.4k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Review PR

    apache/shardingsphere

    Review Apache ShardingSphere or user-authorized downstream pull requests and PR discussions from public or authorized repository evidence.

    21k GitHub stars~6.4k tokensUpdated today
    DevelopmentAuto-check passed
  • Graph-Based Bug Tracing

    tirth8205/code-review-graph

    Traces a bug through a code knowledge graph, following callers, callees and execution flow before opening source files, within a small token budget.

    32k GitHub starsUsed in 1 repo~287 tokens
    DevelopmentAuto-check passed

More from divinevideo/divine-mobile

All 103 skills in this repo
  • Fix ArgoCD ExternalSecret deployment failing with "namespace X is not permitted in project Y".

    266 GitHub stars~931 tokensUpdated today
    Auto-check passed
  • Art Direct

    divinevideo/divine-mobile

    Art direction for any content — reads text, PDF, Word, HTML, PPT, then proposes 2-3 creative directions with photography style, mood, and visual language.

    266 GitHub stars~4.8k tokensUpdated today
    Auto-check passed
  • Async Await Null Race Condition

    divinevideo/divine-mobile

    Fix "Null check operator used on a null value" errors when an object is set to null during an async await.

    266 GitHub stars~881 tokensUpdated today
    Auto-check passed
  • AWS V4 Signing Custom Headers Gcs

    divinevideo/divine-mobile

    Add custom metadata headers (x-amz-meta-) to AWS v4 signed requests for GCS S3-compatible API.

    266 GitHub stars~1k tokensUpdated today
    Auto-check passed
  • Bash Herestring Newline Secrets

    divinevideo/divine-mobile

    Fix password/secret authentication failures caused by trailing newlines when creating Google Cloud secrets (or similar) with bash here-strings.

    266 GitHub stars~791 tokensUpdated today
    Auto-check passed
  • Fix silent video/media processing failures caused by URL extraction code that filters on file extensions (.mp4, .webm, .webp).

    266 GitHub stars~1.1k tokensUpdated today
    Auto-check passed

Categories

Questions about Denormalized Priority Column Staleness

What does Denormalized Priority Column Staleness do?

Fix incorrect priority ordering when using denormalized aggregate columns. Denormalized Priority Column Staleness is an agent skill from divinevideo/divine-mobile. Fix incorrect priority ordering when using denormalized aggregate columns.

When should I use Denormalized Priority Column Staleness?

Denormalized Priority Column Staleness fits situations like: records are processed in wrong order despite ORDER BY on count/sum columns; top items by some metric arent being selected first; aggregate columns show 0; NULL for records that should have high values.

How do I install Denormalized Priority Column Staleness in Claude Code?

Run `npx skills add divinevideo/divine-mobile --skill denormalized-priority-column-staleness -a claude-code`. Or copy the skill folder (.agents/skills/denormalized-priority-column-staleness in divinevideo/divine-mobile) into .claude/skills/denormalized-priority-column-staleness in your project. Claude Code loads it when a task matches its description.

How do I install Denormalized Priority Column Staleness in Codex?

Run `npx skills add divinevideo/divine-mobile --skill denormalized-priority-column-staleness -a codex`. Or copy the skill folder (.agents/skills/denormalized-priority-column-staleness in divinevideo/divine-mobile) into .agents/skills/denormalized-priority-column-staleness in your project. Codex loads it when a task matches its description.

Can I use Denormalized Priority Column Staleness in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add divinevideo/divine-mobile --skill denormalized-priority-column-staleness -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/denormalized-priority-column-staleness, .gemini/skills/denormalized-priority-column-staleness, .github/skills/denormalized-priority-column-staleness and .opencode/skills/denormalized-priority-column-staleness in your project.

What does Denormalized Priority Column Staleness need to run?

SKILL.md names no scripts, command-line tools or credentials: Denormalized Priority Column Staleness is instructions for the agent only.

Does Denormalized Priority Column Staleness access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Denormalized Priority Column Staleness safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Denormalized Priority Column Staleness use?

Denormalized Priority Column Staleness is published under the MPL-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Denormalized Priority Column Staleness use?

About 1.2k tokens (SKILL.md is roughly 4.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Denormalized Priority Column Staleness?

Skills that share tags, products or a category with Denormalized Priority Column Staleness: Code Design Rationale Investigator (cursor/plugins, 11k stars), OpenLogi macOS Permissions Triage (AprilNEA/OpenLogi, 23k stars), Bug Finder for daisyUI (saadeghi/daisyui, 43k stars) and Root Cause Debugging (garrytan/gstack, 136k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Denormalized Priority Column Staleness?

divinevideo (a GitHub organization) maintains it in divinevideo/divine-mobile, which has 266 GitHub stars. The repository holds 103 skills in this directory. The repository was last updated on October 10, 2026.

Source: divinevideo/divine-mobile on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.