How do I install the Super Help skill?

Run npx skillmds@latest add lichens-innovation/super-help in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Super Help safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Super Help?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Super Help free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Super Help?

Lichens-Innovation (@lichens-innovation) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Super Help by lichens-innovation — Agent Skill

Name: Super Help
Author: Lichens-Innovation

Super Help

Answer questions about the Claude Code AI Dev Tools ecosystem — plugins, skills, subagents, hooks, marketplaces, rules, MCP, memory, and CLI commands. Use when the user asks how something works, wants to understand a concept, or needs guidance on any Claude Code tooling topic.

Lichens-Innovation 58a04ea 2 files · 3.1 KB Updated Sep 17, 2026

File contents

Help

Answer any question about the Claude Code AI Dev Tools ecosystem by consulting the relevant reference docs.

Topic → Doc Mapping

Pick only the doc(s) relevant to the user's question — do not read all of them.

Topic	Doc
Plugins (structure, manifest, enabling, updating)	`${CLAUDE_SKILL_DIR}/../../../../docs/plugins.md`
Skills (format, creating, installing, popular repos)	`${CLAUDE_SKILL_DIR}/../../../../docs/skills.md`
Subagents (AGENTS.md, coordination, delegation)	`${CLAUDE_SKILL_DIR}/../../../../docs/subagents.md`
Hooks (PreToolUse, PostToolUse, lifecycle, scripts)	`${CLAUDE_SKILL_DIR}/../../../../docs/hooks.md`
Marketplace (registering, publishing, versioning, auto-updates)	`${CLAUDE_SKILL_DIR}/../../../../docs/marketplace.md`
Rules (format, scope, .clinerules)	`${CLAUDE_SKILL_DIR}/../../../../docs/rules.md`
MCP servers (configuration, tools)	`${CLAUDE_SKILL_DIR}/../../../../docs/mcp.md`
Memory (persistent memory for subagents)	`${CLAUDE_SKILL_DIR}/../../../../docs/memory.md`
Skills CLI (`skills add`, `skills list`, `npx skills`)	`${CLAUDE_SKILL_DIR}/../../../../docs/skills-cli.md`
Claude Code settings, commands, IDE integrations	`${CLAUDE_SKILL_DIR}/../../../../docs/claude-code.md`

Workflow

Identify the topic from the user's question.
Read the relevant doc(s) using the table above — read only the sections needed.
Answer directly with concrete steps, examples, or clarifications. Reference doc sections and file paths where useful.
If the question spans multiple docs, read each one and synthesize a unified answer.

Answer Style

Lead with the direct answer, then add supporting context.
Include concrete examples (file snippets, CLI commands) when they help.
If the user's question implies they want to do something (not just understand it), suggest the matching skill: /create-skill, /create-plugin, /create-subagent, /manage-marketplace.

---name: super-helpdescription: Answer questions about the Claude Code AI Dev Tools ecosystem — plugins, skills, subagents, hooks, marketplaces, rules, MCP, memory, and CLI commands. Use when the user asks how something works, wants to understand a concept, or needs guidance on any Claude Code tooling topic.---# HelpAnswer any question about the Claude Code AI Dev Tools ecosystem by consulting the relevant reference docs.## Topic → Doc MappingPick only the doc(s) relevant to the user's question — do not read all of them.| Topic | Doc ||---|---|| Plugins (structure, manifest, enabling, updating) | `${CLAUDE_SKILL_DIR}/../../../../docs/plugins.md` || Skills (format, creating, installing, popular repos) | `${CLAUDE_SKILL_DIR}/../../../../docs/skills.md` || Subagents (AGENTS.md, coordination, delegation) | `${CLAUDE_SKILL_DIR}/../../../../docs/subagents.md` || Hooks (PreToolUse, PostToolUse, lifecycle, scripts) | `${CLAUDE_SKILL_DIR}/../../../../docs/hooks.md` || Marketplace (registering, publishing, versioning, auto-updates) | `${CLAUDE_SKILL_DIR}/../../../../docs/marketplace.md` || Rules (format, scope, .clinerules) | `${CLAUDE_SKILL_DIR}/../../../../docs/rules.md` || MCP servers (configuration, tools) | `${CLAUDE_SKILL_DIR}/../../../../docs/mcp.md` || Memory (persistent memory for subagents) | `${CLAUDE_SKILL_DIR}/../../../../docs/memory.md` || Skills CLI (`skills add`, `skills list`, `npx skills`) | `${CLAUDE_SKILL_DIR}/../../../../docs/skills-cli.md` || Claude Code settings, commands, IDE integrations | `${CLAUDE_SKILL_DIR}/../../../../docs/claude-code.md` |## Workflow1. **Identify the topic** from the user's question.2. **Read the relevant doc(s)** using the table above — read only the sections needed.3. **Answer directly** with concrete steps, examples, or clarifications. Reference doc sections and file paths where useful.4. **If the question spans multiple docs**, read each one and synthesize a unified answer.## Answer Style- Lead with the direct answer, then add supporting context.- Include concrete examples (file snippets, CLI commands) when they help.- If the user's question implies they want to *do* something (not just understand it), suggest the matching skill: `/create-skill`, `/create-plugin`, `/create-subagent`, `/manage-marketplace`.

Frequently asked questions