dhdna-profiler
by K-Dense-AIdhdna-profiler extracts cognitive patterns and thinking fingerprints from text or speech. Use it to profile how someone reasons, decides, values, and communicates, compare thinking styles, or answer “what’s my thinking style?” It is especially useful for structured analysis, repeated comparisons, and deeper insight into the mind behind a passage.
This skill scores 68/100, which means it is listable but best presented with caveats. Directory users get a real, triggerable workflow for profiling cognitive patterns from text, but they should expect a concept-heavy skill with limited operational scaffolding and only modest guidance for execution details.
- Clear trigger language for when to use the skill, including profiling thinking style, reasoning, and speech/writing patterns.
- Substantial SKILL.md content plus a reference file with domain-specific presets, which improves reuse beyond a generic prompt.
- No placeholder markers or test-only signals; the repository shows a substantive workflow rather than a stub.
- No install command or supporting scripts, so adoption depends on reading and applying the text instructions manually.
- The framework is theory-heavy and repository evidence shows limited practical constraints or step-by-step execution guidance, which may leave edge cases ambiguous.
Overview of dhdna-profiler skill
dhdna-profiler is a text-analysis skill for extracting a cognitive fingerprint from writing or speech. Use the dhdna-profiler skill when you need more than sentiment or topic tagging: it is built to profile how an author reasons, decides, values, and frames ideas. The best fit is a user who wants a practical cognitive profile from a sample, a comparison between two thinkers, or a sharper read on the mind behind a passage.
What makes dhdna-profiler useful for dhdna-profiler for Data Analysis is its structured lens. It does not just summarize content; it organizes observations across defined dimensions, which helps when you need repeatable analysis rather than a one-off impression. It is strongest when the input text is long enough to show patterns, not just opinions.
What dhdna-profiler is best for
This skill is a good match for:
- author or speaker profiling
- comparing two writing samples
- identifying reasoning, decision style, and cognitive habits
- analyzing journaling, essays, strategy notes, or reflective text
- answering “what’s my thinking style?” with evidence from text
Where it adds real value
Compared with a generic prompt, dhdna-profiler gives a clearer analytic frame. That matters when you want:
- consistent labels instead of loose commentary
- a profile you can reuse across samples
- a structured way to inspect ambiguity, logic, emotion, and metacognition
- a result that is easier to compare across people or documents
When not to expect too much
dhdna-profiler is not ideal for short, factual, or highly formulaic text. If the sample has little personal voice, few decisions, or no reasoning trail, the output will be thin. It is also a poor substitute for psychological diagnosis, legal analysis, or identity claims that require direct evidence.
How to Use dhdna-profiler skill
dhdna-profiler install and setup
Install with the repo’s skill workflow, then open the skill files in the source tree. The most useful entry point is scientific-skills/dhdna-profiler/SKILL.md; then read references/advanced-profiling.md for the profiling presets and scoring logic. If you are adapting the skill into another agent system, keep the same analysis intent but rewrite the orchestration around your environment.
A practical dhdna-profiler install check is whether your platform can supply a long enough text sample and preserve the exact wording of the source. The skill works best when the input is not pre-digested into bullet notes before analysis.
What input the skill needs
Give the skill:
- the text to analyze
- the context of the text type, if known
- the comparison target, if you want one
- the output format you want, if your workflow has constraints
Stronger input example:
Analyze this 1,200-word strategy memo as a business communication sample. Profile the author’s reasoning style, confidence level, ambiguity tolerance, and decision framing. Compare it with this second memo and highlight the most meaningful differences.
Weaker input example:
Profile this text.
Recommended workflow
- Feed the raw sample first.
- State the purpose: profile, compare, or interpret.
- If relevant, name the domain: academic, creative, business, technical, or reflective.
- Ask for the dimensions that matter most to you.
- Request a concise summary plus evidence-based observations.
If you are new to dhdna-profiler usage, start with one sample and one question. Add comparison only after the first profile is stable.
Files to read first
For fast adoption, read in this order:
SKILL.mdfor the core framingreferences/advanced-profiling.mdfor preset dimensions and deeper profiling cues
That is usually enough to understand the dhdna-profiler guide without scanning the whole repo.
dhdna-profiler skill FAQ
Is dhdna-profiler better than a normal prompt?
Usually yes, if you want a repeatable cognitive profile. A normal prompt can summarize text, but dhdna-profiler gives you a stable lens for reasoning style, emotional processing, and decision patterns. If you only need a plain summary, the skill may be more structured than necessary.
Does dhdna-profiler work for beginners?
Yes. The main requirement is a real sample of text and a clear goal. Beginners get the best results when they ask for one profile at a time instead of multiple abstract interpretations.
What kind of text is a poor fit?
Very short messages, purely transactional writing, and content with no personal reasoning are weak inputs. dhdna-profiler is strongest when the author’s choices, tone, and logic are visible.
Is it useful outside psychology-like analysis?
Yes. It can support editorial review, founder communication analysis, UX writing review, research-note comparison, and dhdna-profiler for Data Analysis when the dataset includes qualitative text. It is less useful for numeric-only analysis.
How to Improve dhdna-profiler skill
Give the skill the right evidence
The biggest quality jump comes from better source text. Use a longer sample, keep the original wording, and avoid summarizing it before analysis. If you want a profile of how someone thinks, provide text where their reasoning is visible, not just their conclusions.
Name the target dimensions
If you care about one angle, say so. For example:
- “Focus on analytical depth and metacognition.”
- “Compare strategic thinking and emotional processing.”
- “Profile the author as if this were a technical documentation sample.”
This helps dhdna-profiler avoid generic comments and produce a sharper read.
Watch for common failure modes
The most common mistakes are:
- asking for a profile from too little text
- mixing several goals in one request
- omitting the domain, which makes preset selection weaker
- expecting certainty where the evidence is only partial
If the output feels broad, the fix is usually not a different prompt—it is a better sample or a narrower question.
Iterate with a second pass
After the first run, ask for refinement based on what matters most:
- “Show only the strongest evidence for the profile.”
- “Re-rank the dimensions for an executive audience.”
- “Compare this sample against the previous one and explain the biggest shift.”
- “Turn this into a short decision-useful summary.”
That is the most reliable dhdna-profiler usage pattern: first profile, then tighten, then compare.