CtrlK
BlogDocsLog inGet started
Tessl Logo

behuman

Use when the user wants more human-like AI responses — less robotic, less listy, more authentic. Triggers: 'behuman', 'be real', 'like a human', 'more human', 'less AI', 'talk like a person', 'mirror mode', 'stop being so AI', or when conversations are emotionally charged (grief, job loss, relationship advice, fear). NOT for technical questions, code generation, or factual lookups.

71

Quality

87%

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

The canonical home for this skill is behuman in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

85%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.

A well-structured, highly actionable prompt-level skill with a clear sequenced workflow and a built-in validation loop. Its weaknesses are a broken external reference and some philosophical padding that could be trimmed.

Suggestions

Remove or create the missing 'references/api-integration.md' so the one signaled external reference actually resolves.

Trim or cut the Philosophy section and the metaphorical intro — the 3-step process and examples already convey the technique without invoking Lacan/Kahneman.

Tighten 'What This Does' so it does not restate the System 1/System 2 framing already given in The Process.

DimensionReasoningScore

Conciseness

Mostly efficient with well-targeted examples, an anti-patterns table, and a token-cost table, but the Philosophy section and the metaphorical intro restate concepts (Lacan, Kahneman, Dialogical Self) that are not strictly needed to execute the skill.

4 / 5

Actionability

Highly actionable for an instruction-only skill: a concrete 3-step process (Self → Mirror → Conscious Response), a specific Mirror Checklist, sample Mirror voice lines, explicit output-format blocks for show/quiet modes, and three full worked examples covering the common cases.

5 / 5

Workflow Clarity

The process is explicitly sequenced (Step 1, 2, 3) with a built-in validation checkpoint — the Mirror reflection against a checklist — and a revise feedback loop (Self generates, Mirror critiques, Self revises); no destructive/batch cap applies.

5 / 5

Progressive Disclosure

Sections are well organized, but the only external reference ('see references/api-integration.md') points to a file that does not exist in the bundle, which breaks navigation rather than presenting a minor gap.

3 / 5

Total

17

/

20

Passed

Description

90%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: explicit what/when, rich natural trigger terms, and a clear negative-scope boundary that sharply reduces conflict risk. The only soft spot is specificity, which lists output attributes rather than concrete actions.

DimensionReasoningScore

Specificity

Names the domain ('more human-like AI responses') and a few concrete qualities ('less robotic, less listy, more authentic'), but these are attributes of the output rather than concrete actions, and coverage is not comprehensive.

3 / 5

Completeness

Explicitly answers both what ('more human-like AI responses — less robotic, less listy, more authentic') and when ('Use when...', concrete trigger list, emotionally charged contexts, plus a 'NOT for' exclusion clause).

5 / 5

Trigger Term Quality

Comprehensive natural trigger coverage including synonyms and variations ('behuman', 'be real', 'like a human', 'more human', 'less AI', 'talk like a person', 'mirror mode', 'stop being so AI') plus emotionally charged context cues.

5 / 5

Distinctiveness Conflict Risk

Clear niche (human-voice response styling) with distinctive triggers and an explicit 'NOT for technical questions, code generation, or factual lookups' boundary that minimizes conflict with other skills.

5 / 5

Total

18

/

20

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

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository
alirezarezvani/claude-skills
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.