skills.rest
KingInYellows
KingInYellowsOFFICIAL
Explore all skills by this author →
GitHub

debt-conventions

Define unified debt scoring frameworks and JSON output schemas for scanner agents.

Updated Jan 10, 2026
Search Tags:#safety#engineering#conventions#scoring#debt#scanner#output-schema
One-click install
npx skills add https://github.com/KingInYellows/yellow-plugins --skill debt-conventions
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debt-conventions
Source: https://github.com/KingInYellows/yellow-plugins/tree/main/plugins/yellow-debt/skills/debt-conventions
Command: npx skills add https://github.com/KingInYellows/yellow-plugins --skill debt-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? Defines a unified debt scoring framework and output schemas that standardize how scanners assess and report debt across the plugin, ensuring a single source of truth.

## Core Features & Use Cases

  • Establishes scoring rubrics, category definitions, and safety patterns used by all scanner types.
  • Provides a reference implementation for JSON output schemas and validation, used by the synthesizer and new scanner types.
  • Use case: When adding a new debt-scanning rule, follow the conventions to ensure consistent reporting and risk assessment.

### Quick Start Validate a scanner's output by applying the debt-conventions to enforce the shared schema.

Frequently Asked Questions about debt-conventions

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

FAQPage Schema
How do I standardize scanner output formats for debt scoring across different tools?▼

A unified debt scoring framework provides a single source of truth by enforcing a formal JSON output schema and standardized categories, ensuring all scanner agents report debt consistently.

What conventions should I follow when adding a new debt-scanning rule?▼

When adding a new debt-scanning rule, follow the established scoring rubrics, category definitions, and safety patterns to ensure your scanner provides consistent reporting and accurate risk assessment.

How do I validate a scanner's JSON output against a shared debt schema?▼

You validate a scanner's output by applying the debt-conventions reference implementation, which enforces the shared JSON schema and severity rubric to check structural correctness and risk alignment.

Does debt scoring require a specific severity rubric for engineering scanners?▼

Yes, the framework enforces a formal severity rubric and standardized categories so that all engineering scanners evaluate and report technical debt using a unified risk assessment standard.

When do I need to apply safety patterns in debt scanner development?▼

You apply safety patterns during debt scanner development whenever you need to ensure that new debt-scoring patterns adhere to the formalized conventions and do not produce unsafe or misaligned scanner outputs.

Related Skills

Explore More Software Engineering Skills→
rakhnianskii9rakhnianskii9

tech-debt

Scan codebases for TODO/FIXME/HACK markers and maintain a prioritized debt register.

Community
Advanced
florianbuetowflorianbuetow
12

report

Generate security reports from scanner findings in Markdown, HTML, JSON, and SARIF formats.

Community
Advanced
c3zc3z

weekly-retro

Generate a weekly retrospective from apom JSON data.

Community
Intermediate
ImaginerLabsImaginerLabs

quality-analyst

Assess code quality and quantify technical debt across a codebase.

Official
Intermediate