user-info

Use when you need the current user's identity or contact info: name, job title, employee number, email, phone, or department.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Quality

Content

92%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 lean, actionable, and well-structured, with a clearly sequenced sensitive-data workflow that includes consent validation and refusal handling. There are no bundle files, so progressive disclosure rests entirely on internal organization, which is strong.

Dimension	Reasoning	Score
Conciseness	Sections are lean and well organized with executable snippets and no padding about concepts Claude already knows; the inline example-output block is justifiable but slightly trimmable.	4 / 5
Actionability	Provides copy-paste-ready code for the basic call and the consent-gated sensitive-field flow, with exact argument names and field tables covering the common cases.	5 / 5
Workflow Clarity	The phone-number flow is explicitly sequenced (ask consent → request → handle decline) with an explicit checkpoint and a "do not ask again" feedback rule.	5 / 5
Progressive Disclosure	Under 50 lines with no external bundle files; content is well split into Basic Usage, Getting the Full Phone Number, and Constraints sections, satisfying the simple-skill exception.	5 / 5
	Total	19 / 20 Passed

Description

92%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 is concise, third-person, and explicitly pairs a capability statement with a natural-language trigger clause and concrete field list. Its only minor gap is limited synonym coverage in trigger terms.

Dimension	Reasoning	Score
Specificity	Enumerates concrete fields — "name, job title, employee number, email, phone, or department" — giving comprehensive coverage of the capability rather than vague language.	5 / 5
Completeness	Explicitly answers both what (retrieve identity/contact info) and when ("Use when you need the current user's identity or contact info") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural terms like "name, job title, employee number, email, phone, department" align with what users say, but synonyms such as "profile" or "contact info" beyond the lead clause are limited.	4 / 5
Distinctiveness Conflict Risk	Scopes to "the current user's" profile, a clear niche with distinct triggers and minimal overlap risk against other skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

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: dtyq/magic
Path: backend/super-magic/agents/skills/user-info/SKILL.md
Commit: f9973c5

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.