j.help

Lists all available skills with descriptions as a slash-command table.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a host tool's built-in command shadows the bare /help alias, users lose a reliable way to discover which skills and commands are available in their project. This skill provides a collision-safe alias that always reaches the help flow. ## Core Features & Use Cases - Skill Discovery: Lists every available skill with a short description, formatted as a table of slash commands and descriptions. - Shadow-Proof Alias: Works even when another tool's native /help command overrides the bare form, via the /j-help or j.j-help invocation. - Dynamic MCP Discovery: Ships an MCP server that scans .claude/skills or .agents/skills at runtime and returns the folder names it finds. - Use Case: You installed the Jenga agent framework and want to know what commands exist. Invoke /j-help to get a table of every skill and what it does, even if Claude Code's own help command is shadowing /help. ## Quick Start Ask the agent to list all available skills and commands using the j-help alias.

Frequently Asked Questions about j.help

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

FAQPage Schema
How do I list all available skills in my project?▼

Invoke the help skill to get a table of every available slash command with a short description. If the bare /help form is shadowed by another tool, use /j-help or j.j-help instead for the same output.

Why is my /help command not showing project skills?▼

Some host tools like Claude Code resolve commands by literal directory-name matching, so a built-in /help can shadow the project's help skill. Use the collision-safe /j-help alias, which is guaranteed to reach the project's help flow.

Can I discover skills dynamically at runtime with MCP?▼

Yes, the jenga-agent package ships an MCP server at mcp/help that scans for a .claude/skills directory, falling back to .agents/skills, and returns all skill folder names. Run it with node index.js or wire it into .claude/settings.json.

What directories does the help MCP server check for skills?▼

It first looks for a .claude/skills directory at the given path (defaulting to the current working directory), then falls back to .agents/skills. If neither exists, it returns a message listing the paths it checked.

Should I edit the j-help SKILL.md file directly?▼

No, the file is generated and synced by scripts/generate-j-alias.sh from the source skills/help/SKILL.md. Re-run the generator to pick up source changes instead of hand-editing.