askill
pipeline-rubrics

pipeline-rubricsSafety 95Repository

Scoring rubrics for all 5 pipeline layers (Vision, Architecture, IA, BE, FE). Use when auditing specs, running self-checks, or remediating ambiguity gaps.

2 stars
1.2k downloads
Updated 3/6/2026

Package Files

Loading files...
SKILL.md

Pipeline Rubrics

Standardized scoring rubrics for every pipeline layer. Used by audit workflows, self-checks in compilation workflows, and remediation workflows.

When to Use This Skill

  • During /audit-ambiguity — load the rubric for the layer being audited
  • During document compilation self-checks — load the relevant rubric to validate before presenting
  • During /remediate-pipeline — load rubrics for adversarial scoring
  • Any time a two-implementer test is needed on a pipeline document

How to Use

  1. Identify the pipeline layer being scored
  2. Load the matching reference file from references/
  3. Score each dimension using the ✅ / ⚠️ / ❌ criteria
  4. Apply the scoring formula from references/scoring.md

Reference Files

LayerFileDimensions
Visionreferences/vision-rubric.md7
Architecturereferences/architecture-rubric.md9
IAreferences/ia-rubric.md8
BEreferences/be-rubric.md10
FEreferences/fe-rubric.md10
Scoringreferences/scoring.mdFormula + cross-layer checks

Two-Implementer Test

For every dimension: "Would two different developers, reading only this spec with no other context, make the same decision?"

  • If YES with a specific citation → ✅
  • If MAYBE or requires inference → ⚠️
  • If NO or content is absent → ❌

Related Skills

  • resolve-ambiguity — resolve gaps found by rubric scoring
  • technical-writer — rewrite sections that score ⚠️ or ❌
  • code-review-pro — adversarial review methodology

Install

Download ZIP
Requires askill CLI v1.0+

AI Quality Score

50/100Analyzed 3/2/2026

Moderate quality skill with good structure but significant completeness gap. Provides clear usage instructions and a useful two-implementer test principle, but the actual scoring rubrics (the core content) are missing - only references to external files. Tags help discoverability. Located in internal .agent folder suggesting repo-specific use.

95
80
50
25
55

Metadata

Licenseunknown
Version-
Updated3/6/2026
PublisherRepairYourTech

Tags

ci-cdtesting