CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dhdna-profiler

Applies the DHDNA framework as an exploratory rubric for reasoning and writing patterns in supplied text. Used for explicit requests for DHDNA, cognitive-style reflection, a thinking-pattern profile, or comparisons of textual reasoning. Scores describe evidence in the sample, not validated psychological traits or personal identity.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 body is a well-structured, highly actionable instruction skill with an explicit verification step in its workflow and an appropriately split one-level reference file. Its weakest point is conciseness: the validity disclaimer is restated in at least five places and could be consolidated into the Boundaries section.

Suggestions

Consolidate the repeated "scores are not validated traits" disclaimers into the Boundaries section and state it once elsewhere by reference, trimming several sentences from the workflow, worked example, and Comparing samples sections.

Move the advanced-profiling.md pointer into a short dedicated "Advanced" section or add it to the top-level structure so readers can find genre lenses and longitudinal guidance without reading the Comparing samples prose.

DimensionReasoningScore

Conciseness

The body mostly respects token budget with no generic concept explanations, but the core caveat that scores are not validated traits is repeated across "Sources and scope", the workflow, the worked example, "Comparing samples", and "Boundaries". It is mostly efficient but includes repeated disclaimer sections that could be consolidated, fitting anchor 3 better than the noticeably padded anchor 2.

3 / 5

Actionability

For an instruction-only skill the guidance is fully executable: a five-step workflow, a per-dimension evidence table, declared numeric anchors (1-3/4-7/8-10/N/A), HIGH/MEDIUM/LOW confidence rules, a copy-paste output template, and a worked example with a synthetic sample. This matches anchor 5's copy-paste-ready coverage of the common case.

5 / 5

Workflow Clarity

The five numbered steps (establish sample, collect evidence, annotate, synthesize, review and return) are clearly sequenced, and step 5 is an explicit verification checkpoint ("Verify every quotation against the sample, every observation against the cited passage, and every N/A against the available context") acting as a feedback loop. The skill is analytical rather than destructive or batch, so no validation cap applies.

5 / 5

Progressive Disclosure

The body is well sectioned and the single bundle file is one level deep and clearly signaled with its content described ("See [advanced profiling](references/advanced-profiling.md) for genre lenses, longitudinal limits, and compact notation"); the referenced file exists and introduces no further nesting. However the only pointer sits mid-prose inside "Comparing samples" rather than a clearly labeled advanced section, a minor organization gap that keeps it below anchor 5.

4 / 5

Total

17

/

20

Passed

Description

82%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 description with an explicit trigger clause and concrete trigger phrases answering both what and when, written in third person. Its main weakness is specificity: it names the domain and only 1-2 actions without listing the concrete outputs the skill produces.

Suggestions

Enumerate the concrete deliverables in the description (e.g., produces a twelve-dimension annotation with confidence ratings, pair comparisons, and an output profile) to raise specificity from naming the domain to listing several specific actions.

Add one or two natural trigger synonyms such as "writing-pattern profile" or "reasoning-style analysis" to broaden keyword coverage.

DimensionReasoningScore

Specificity

"Applies the DHDNA framework as an exploratory rubric for reasoning and writing patterns in supplied text" plus "comparisons of textual reasoning" name the domain and 1-2 concrete actions, but the description does not enumerate the concrete deliverables (twelve-dimension annotation, confidence ratings, pair comparisons, output profile). Anchor 4 requires several specific actions listed, which this lacks.

3 / 5

Completeness

It clearly answers both: the what ("Applies the DHDNA framework as an exploratory rubric for reasoning and writing patterns in supplied text") and the when ("Used for explicit requests for DHDNA, cognitive-style reflection, a thinking-pattern profile, or comparisons of textual reasoning") with concrete trigger phrases, matching the anchor-5 pattern.

5 / 5

Trigger Term Quality

"explicit requests for DHDNA, cognitive-style reflection, a thinking-pattern profile, or comparisons of textual reasoning" covers the natural phrases a user would say for this niche well, but a few plausible variations (e.g., "writing-pattern profile", "reasoning-style analysis") are missing. It clearly exceeds anchor 3 and falls short of the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

DHDNA is a unique named framework and the triggers are niche-specific (cognitive-style reflection, thinking-pattern profile), giving a clear niche with minimal risk of triggering for the wrong skill.

5 / 5

Total

17

/

20

Passed

Validation

100%

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

K-Dense-AI/scientific-agent-skills

Path

skills/dhdna-profiler/SKILL.md

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.