CtrlK
BlogDocsLog inGet started
Tessl Logo

create-profile

Creates or updates a personal developer profile at ~/.claude/PROFILE.md. Run this once to tell Claude about your role, experience, and preferences so that explanations and other skills can tailor their output to you.

67

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/create-profile/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 tightly structured, highly actionable interview script with clear sequencing and good organization; the only meaningful gap is minor repetition and the absence of an explicit write-verification feedback loop.

Suggestions

State the 'DO NOT use AskUserQuestion options; accept free-form answers' rule once near the top instead of repeating it under questions 2, 3, and 4.

Add an explicit post-write verification step (e.g. re-read ~/.claude/PROFILE.md to confirm it parsed and sections are populated) to strengthen the workflow's feedback loop.

Trim the editorializing phrase about the profile 'feeling written by the person, not a form' to save tokens without losing the intent.

DimensionReasoningScore

Conciseness

Mostly efficient with verbatim headers and a tight template, but 'DO NOT USE AskUserQuestion options for this — let them answer in their own words' is repeated three times and the 'feels like it was written by the person, not a form' line is mild padding.

4 / 5

Actionability

Fully actionable: exact question headers, enumerated options, free-form vs. AskUserQuestion directives, a complete profile markdown template, and a verbatim confirmation message — copy-paste ready for an instruction-only skill.

5 / 5

Workflow Clarity

Clear sequence (read existing profile first → interview one question at a time → write file → confirm) with a read-before-overwrite checkpoint and a skip-on-'no' rule, but lacks an explicit post-write verification step.

4 / 5

Progressive Disclosure

Well-organized into Interview and Writing-the-Profile sections with no external references needed; content is appropriately self-contained and easy to navigate, satisfying the simple-skill exception.

5 / 5

Total

18

/

20

Passed

Description

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

The description clearly conveys a distinct, concrete purpose with reasonable trigger phrasing, but loses points for second-person voice and a 'when' clause that is functional rather than crisply explicit.

Suggestions

Rewrite in third person to avoid the second-person penalty, e.g. 'Creates or updates a personal developer profile... Use when setting up Claude to tailor explanations and skill output to the user's role and preferences.'

Add an explicit 'Use when...' trigger clause naming the natural user phrasing (e.g. 'Use when the user wants to personalize Claude, set up their profile, or tailor output to their role').

Consider mentioning natural synonyms like 'personalize', 'set up', or 'onboarding' to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names concrete actions ('Creates or updates a personal developer profile at ~/.claude/PROFILE.md', 'tell Claude about your role, experience, and preferences'), but the second-person voice ('your role', 'to you') triggers the rubric's −1 specificity penalty, capping this at 3.

3 / 5

Completeness

Clearly states what it does ('Creates or updates a personal developer profile at ~/.claude/PROFILE.md') and provides explicit trigger guidance ('Run this once to tell Claude about...'), but the 'when' could be more sharply phrased as a Use-when clause.

4 / 5

Trigger Term Quality

Includes natural phrases a user would say ('developer profile', 'role, experience, and preferences', 'tailor their output') with good coverage, though a few common synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

Targets a distinct niche — a single named file (~/.claude/PROFILE.md) for capturing user role/preferences — with minimal overlap risk against other skills.

5 / 5

Total

16

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
RoleModel/rolemodel-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.