CtrlK
BlogDocsLog inGet started
Tessl Logo

user-general-facts

Capture and organize general facts about the user by topic

61

Quality

71%

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 ./src/server/api/go/configs/skill_templates/user-general-facts/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%

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-organized, lean, instruction-only skill with concrete file-format guidance and clear organization rules. It models the 'simple skill' case the rubric rewards at the top of the scale across all four dimensions.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: a one-line intro, a concrete file-format template, a short example-topics list, and tight guidelines, with no padding explaining what facts or memory are. Not a score-2 because there is no unnecessary explanation to trim.

3 / 3

Actionability

It gives fully concrete, copy-paste-ready guidance: a literal `[TOPIC].md` file-format template with third-person bullet phrasing, a lowercase kebab-case naming rule, and five named example files. For an instruction-only skill this is as actionable as the score-3 anchor.

3 / 3

Workflow Clarity

This is a simple single-purpose skill under 50 lines with an unambiguous action (create a new topic file for new categories, update existing files for new facts, correct stale facts), which the rubric explicitly allows to score 3 without multi-step workflows or validation checkpoints.

3 / 3

Progressive Disclosure

No bundle files exist in references/scripts/assets, and the skill is short and single-purpose; the body is well-organized into File Structure, File Format, Example Topics, and Guidelines sections, which per the rubric's simple-skill note merits a 3 without external references.

3 / 3

Total

12

/

12

Passed

Description

42%

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 cleanly states the skill's purpose but is missing an explicit trigger/when clause and natural user phrasing, which limits its completeness and trigger-term quality. It is a competent but incomplete description rather than a vague or over-claimed one.

Suggestions

Add a 'Use when...' clause naming natural triggers, e.g. 'Use when the user shares preferences, background, or goals to remember for future interactions'.

Incorporate words users actually say (e.g. 'remember', 'preferences', 'facts about me') to improve trigger-term quality.

Sharpen specificity by listing 2-3 concrete actions (e.g. 'capture, organize, and recall user facts by topic').

DimensionReasoningScore

Specificity

The phrase "Capture and organize general facts about the user by topic" names the domain and two concrete actions (capture, organize) but does not enumerate multiple specific actions, matching the score-2 anchor rather than the score-3 multi-action list.

2 / 3

Completeness

It states what the skill does but lacks any "Use when..." clause or equivalent explicit trigger guidance, so per the rubric guideline completeness is capped at 2 even though the "what" is clear.

2 / 3

Trigger Term Quality

The description offers no natural trigger keywords a user would actually say (no "facts about me", "remember", "preferences"); "general facts about the user by topic" is descriptive rather than user-spoken phrasing, fitting the score-1 anchor of no natural keywords.

1 / 3

Distinctiveness Conflict Risk

"General facts about the user" carves out a recognizable niche but is broad enough to overlap with other memory or personalization skills, matching the score-2 anchor of being somewhat specific yet still potentially overlapping.

2 / 3

Total

7

/

12

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
memodb-io/Acontext
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.