j.wtf

Clarifies ambiguous or under-specified prompts via a collision-safe alias of the clearify skill.

Updated Aug 3, 2026
One-click install
npx skills add https://github.com/samwelmunga/jenga-npm --skill j-wtf-samwelmunga
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: j.wtf
Source: https://github.com/samwelmunga/jenga-npm/tree/main/.agents/skills/j-wtf
Command: npx skills add https://github.com/samwelmunga/jenga-npm --skill j-wtf-samwelmunga

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a host tool's built-in command shadows the bare /wtf slash command, the clarification flow becomes unreachable. This skill provides a guaranteed, unshadowed directory name (j-wtf) so the same ambiguity-clarification behavior always resolves. ## Core Features & Use Cases - Collision-safe invocation: Resolves /j-wtf (and j.j-wtf) to the same flow as /wtf even when another tool overrides the bare command. - Alias of /clearify: Delegates entirely to skills/clearify/SKILL.md, clarifying ambiguous, dense, or under-specified prompts and conversation context on request. - Generated and synced: Produced by scripts/generate-j-alias.sh wtf from the source skill, keeping behavior identical without manual edits. - Use Case: A user types "wtf does this mean" after a dense agent response; the skill triggers the clearify flow to unpack and clarify the confusing content. ## Quick Start Invoke /j-wtf with a confusing prompt or conversation excerpt and ask the agent to clarify what it means.

Frequently Asked Questions about j.wtf

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I clarify an ambiguous or confusing prompt with an AI agent?▼

Invoke /j-wtf (or /wtf) with the confusing prompt or conversation context attached. The skill delegates to the clearify flow, which analyzes the ambiguity and clarifies dense or under-specified content.

What is the difference between /wtf and /j-wtf?▼

There is no behavioral difference; both run the same clearify flow. The j-wtf directory exists only so the command resolves when a host tool's built-in command shadows the bare /wtf name.

Why is my /wtf command not triggering the skill?▼

Another tool's built-in command of the same name may be shadowing it, since skill resolution is a literal directory-name match. Use /j-wtf instead, which is guaranteed to resolve to this skill.

Can I edit the j-wtf SKILL.md file directly?▼

No, the file is generated and synced by scripts/generate-j-alias.sh from skills/wtf/SKILL.md. Hand edits are overwritten; re-run the generator to pick up source changes.

Does j-wtf implement its own clarification logic?▼

No, it contains no ambiguity-detection logic of its own. It instructs the agent to read skills/clearify/SKILL.md and execute those instructions exactly as written.