aps-doc-staging

Expert documentation generation for staging transformation layers. Auto-detects SQL engine (Presto/Trino vs Hive), documents transformation rules, PII handling, deduplication strategies, and data quality rules. Use when documenting staging transformations.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./aps-doc-skills/staging/SKILL.md

Quality

Content

60%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill delivers concrete, actionable template guidance with a clear pre-flight workflow, but inlines a very large template that should live in a reference file and carries redundant summary padding.

Suggestions

Move the full documentation template into a references/ file (e.g. references/template.md) and keep only a compact overview plus a one-level-deep link in SKILL.md to raise progressive disclosure.

Trim the restated closing Summary and tighten the 'MANDATORY: Codebase Access Required' prose to remove dramatic repetition ('Period.') and redundant 'NO placeholders' lines.

Add an explicit validate-then-fix feedback loop for the generated documentation (e.g. verify all template sections contain real extracted data before finalizing) to lift workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and does not over-explain basic concepts, but the ~140-line placeholder template and the restated Summary section add noticeable bulk that could be tightened; not a level-2 because the padding is template material rather than conceptual fluff.	3 / 5
Actionability	Provides a concrete documentation template and specific pre-flight steps ('Use Glob to verify SQL files exist', 'STOP if cannot read files'); as an instruction-only skill the structural guidance is actionable, with only minor gaps.	4 / 5
Workflow Clarity	Sequences a clear pre-flight (ask for path, Glob-verify, STOP) before template-driven generation, with an explicit validation gate; falls short of 5 because there is no validate-then-fix feedback loop on the produced documentation.	4 / 5
Progressive Disclosure	No bundle files exist, and the entire large template is inlined in SKILL.md — content that clearly belongs in a separate reference file is buried inline, matching the inlining anchor; not a level-1 because section headers give minimal structure.	2 / 5
	Total	13 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that names concrete actions and an explicit trigger, with a clear niche that minimizes conflict risk. Its only weakness is slightly narrow trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Auto-detects SQL engine (Presto/Trino vs Hive)', 'documents transformation rules, PII handling, deduplication strategies, and data quality rules' — covering the domain comprehensively.	5 / 5
Completeness	Clearly answers 'what' (enumerated documentation actions) and 'when' ('Use when documenting staging transformations') with concrete trigger phrasing.	5 / 5
Trigger Term Quality	Includes natural phrases like 'staging transformations' and 'documenting' plus engine names, but is missing broader synonyms a user might say; not a level-5 comprehensive set of natural terms.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche — staging-layer documentation for Presto/Trino/Hive — with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: treasure-data/td-skills
Path: aps-doc-skills/staging/SKILL.md
Commit: ff38137

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.