CtrlK
BlogDocsLog inGet started
Tessl Logo

document-quality-check

Document Quality Check skill for Datasite deal rooms. Use this skill whenever a deal team wants to audit document quality before going live to buyers. Triggers include: "check document quality", "flag bad documents", "find password protected files", "check for blank documents", "PII check", "redaction review", "find corrupted files", "document audit", "quality check the data room", "are there any blank or broken files", "check for unredacted personal data", or any request to verify that documents in the data room are complete, accessible, and safe to share. Use this skill proactively before a data room goes live. Do not use for renaming files (use smart-file-renaming) or for identifying missing sections (use gap-analysis).

68

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

65%Weight 40%Scale 1-3

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

A thorough, highly actionable skill with concrete tool calls and clear user-gate checkpoints, but it is verbose and monolithic: checks are repeated across three sections, the full dashboard HTML/CSS spec is inline, and the check numbering is internally inconsistent (Phase B 'Checks 8–10' vs actual numbers 3/4/11; 'six categories' vs 12 checks). Splitting the dashboard spec and check catalog into reference files and reconciling the numbering would lift the weaker dimensions.

Suggestions

Reconcile check numbering: align the Blueflame block's 'Phase A (Checks 1–7)' / 'Phase B (Checks 8–10)' labels with the actual check numbers (PII=4, redaction=3, broken references=11) and fix the intro's 'six categories' to match the 10 capabilities / 12 checks.

Move the detailed Step 4b dashboard HTML/CSS spec and the per-check definitions into reference files (e.g. references/dashboard-spec.md, references/checks.md) and keep SKILL.md as a concise overview, reducing the ~456-line monolith and the triple enumeration of checks.

Add a consolidated verification gate before reporting (e.g. 'review Phase A findings against filename/folder context and drop false positives before compiling') so the batch audit has an explicit validate-fix-retry loop rather than scattered context-check notes.

DimensionReasoningScore

Conciseness

The ~456-line body is accurate and domain-specific (no basic-concept padding), but materially verbose and repetitive: the checks are enumerated three times (Feature Requirements table, the Phase A bullet list, then each Check 1–12 section), and Step 4b embeds a full HTML/CSS spec (hex colors, fonts, tile icons). It could be tightened without losing clarity, fitting the 'mostly efficient but could be tightened' anchor rather than the lean score-3 case.

2 / 3

Actionability

Highly actionable: every check ships concrete, copy-paste-ready tool calls with exact filter syntax (e.g. listFolderContents(projectId, query="*", filter=["status:EQ:FAILED", "type:EQ:DOCUMENT"])) and specific searchDocuments queries, plus per-issue severity and recommended actions — matching the 'fully executable, copy-paste ready' anchor.

3 / 3

Workflow Clarity

Steps are clearly sequenced with explicit user-gate checkpoints (the Blueflame activation 'wait for response' gate, the Step 4 dashboard confirmation) and error-recovery in Common Issues, but the check numbering is internally inconsistent — the Blueflame block labels Phase B as 'Checks 8–10' while the actual PII/redaction/broken-reference checks are numbered 3, 4, and 11, and the intro says 'six categories' against 10 table capabilities and 12 numbered checks. That mismatch, plus scattered rather than consolidated validation for a batch operation, caps it below the clean score-3 anchor.

2 / 3

Progressive Disclosure

No bundle files exist and the entire skill is one monolithic ~456-line document; it is well-sectioned (Terminology, Steps 1–5, Checks 1–12, Operating Principles, Common Issues) so it is not a disorganized wall, but content that could be split out (the detailed dashboard spec in Step 4b, the per-check definitions) is inline with no one-level references, fitting the score-2 'content that should be separate is inline' anchor rather than the under-50-lines score-3 exception.

2 / 3

Total

9

/

12

Passed

Description

100%Weight 40%Scale 1-3

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 description: it states a concrete purpose, provides abundant natural trigger phrases, gives explicit 'use when' guidance, and proactively disambiguates from sibling skills. Its only weakness is verbosity from the long trigger enumeration, but the content is relevant rather than fluff.

DimensionReasoningScore

Specificity

Names concrete actions via its trigger list — 'find password protected files', 'check for blank documents', 'PII check', 'redaction review', 'find corrupted files' — and a clear purpose ('audit document quality', 'verify that documents... are complete, accessible, and safe to share'), matching the 'lists multiple specific concrete actions' anchor rather than the partial score-2 anchor.

3 / 3

Completeness

Explicitly answers both 'what' (audit/verify document quality) and 'when' ('Use this skill whenever a deal team wants to audit document quality before going live', 'Use this skill proactively before a data room goes live'), satisfying the explicit-trigger score-3 anchor and well above the missing-'when' score-2 cap.

3 / 3

Trigger Term Quality

Eleven natural trigger phrases a deal-team user would actually say ('check document quality', 'flag bad documents', 'are there any blank or broken files', 'PII check'), giving strong coverage of common variations rather than the sparse score-2 case.

3 / 3

Distinctiveness Conflict Risk

A clear niche (Datasite deal rooms, pre-go-live document audit) with explicit disambiguation — 'Do not use for renaming files (use smart-file-renaming) or for identifying missing sections (use gap-analysis)' — making conflict with adjacent skills unlikely.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

Total

15

/

16

Passed

Repository
openai/plugins
Reviewed

Table of Contents

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.