Lean body that assumes Claude's competence: no padding explaining what a user profile is — just the tool call, an output sample, a field table, and the sensitive-data procedure, with every token earning its place.

Provides fully executable, copy-paste-ready tool.call() snippets for both basic retrieval and the consent-gated sensitive-field flow, plus a concrete field table and example output.

The sensitive-phone flow is explicitly sequenced as Step 1 (ask consent) -> Step 2 (request full number only if consent is given) with a decline branch and a gating constraint ('never pass include_sensitive_fields without prior explicit approval').

A short single-purpose skill (under 50 lines, no bundle files) organized into clearly labeled sections (Basic Usage, Getting the Full Phone Number, Constraints); no nested references are needed.

Lists several concrete data points the skill exposes — name, job title, employee number, email, phone, department — naming specific fields rather than vague language, which for a retrieval skill is the meaningful concrete capability.

Explicitly answers both what it does ('the current user's identity or contact info') and when to use it via the 'Use when...' clause enumerating the relevant fields.

Uses natural user-facing terms ('name', 'job title', 'employee number', 'email', 'phone', 'department') that a user would plausibly request, with good coverage of common variations.

Scoped narrowly to the current session user's identity/contact info with a distinct 'Use when' trigger, making it unlikely to fire for unrelated skills.