agentleFS
DataWithBaraaDataWithBaraa/claude-code-data-engineering-skills/skills/quality/SKILL.md

quality

Skill84 starsChanged 13 days agoMITView on GitHub

Use to see which checks failed or warned, what was quarantined, how fresh the tables are, and whether each table is safe to use today.

12 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use tasks, analyze and 4 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • genomewalkerSkill

    tasks

    Browse and resume tasks, threads, and background jobs across sessions

    Also in 3 projects that use this

  • AnthropicSkill

    analyze

    Answer data questions -- from quick lookups to full analyses. Use when looking up a single metric, investigating what's driving a trend or drop, comparing segments over time, or preparing a formal data report for stakeholders.

    Also in 3 projects that use this

  • MicrosoftSkill

    report

    Turn an exploration (threads, findings, charts) into a single Markdown report — note, blog post, executive summary, KPI dashboard, slide brief, or multi-section analytical report, with embedded charts.

    Also in 3 projects that use this

  • AnthropicSkill

    debug

    Structured debugging session — reproduce, isolate, diagnose, and fix. Trigger with an error message or stack trace, "this works in staging but not prod", "something broke after the deploy", or when behavior diverges from expected and the cause isn't obvious.

    Also in 4 projects that use this

  • SentrySkill

    review

    Fixture review skill.

    Also in 5 projects that use this

  • BlockSkill

    plan

    Draft a TDD, PRD, or lightweight plan in the conversation without committing it.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every check, layer by layer: passed, warned or failed, with the table and the rows it affects.

    line 16
  2. Distinctive:

    Never changes a check, never reruns a job, never releases a quarantined row.

    line 39

“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Quality

The job: say what the checks stopped and why, and whether each table can be trusted today. It reads, it never changes a check.

Input: a date or a period, the last month by default.

Steps

  1. The status of the runs: succeeded or failed, the check that failed a run, and the tasks that were skipped.
  2. Every check, layer by layer: passed, warned or failed, with the table and the rows it affects.
  3. The quarantine: every stopped file and row, with the rule it broke.
  4. Freshness: when every table the consumers read was last rebuilt, against its service level.
  5. The reconciliation with the source, when the project has one: the counts and the totals on both sides.
  6. The checks that fail most, and the ones that warn every day and nobody looks at anymore.
  7. The checks that never failed: when each one was last tested with bad data, so you know it still works.
  8. The verdict per table: safe to use, use with care, or do not use, with the reason.
  9. Give the result as one web page.

Output

One HTML file, like references/quality.html: the numbers of the period, the verdict per table, when the data was ready, every check on every day, the checks that failed most, the quarantine per day and the stale tables. Read it for the layout before you write the page.

Reads

  • the run records, the check results, the quarantine, the reconciliation

Writes

  • the web page only

Never

  • Never changes a check, never reruns a job, never releases a quarantined row.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.