| name | ai-help |
| description | Show what features and AI tools are available in the tcl-lsp extension across VS Code, other editors, Claude Code skills, and the MCP server. Answers 'what can you do?' questions. Use when asking about tcl-lsp features, finding available AI tools, discovering Claude Code skills, or getting help with the tcl-lsp extension. |
| allowed-tools | Bash, Read |
AI Help -- tcl-lsp feature guide
Answer questions about what features the tcl-lsp extension provides and how
to use them across VS Code, other editors, Claude Code, and the MCP server.
Steps
- Read the feature catalogue built into the server:
uv run --no-dev python ai/claude/tcl_ai.py help
- If the tool fails, fall back to reading the README.md for feature information
- If the user asked about a specific topic (e.g. "how do I validate?",
"what MCP tools exist?", "how do I set up Neovim?"), focus on that area
and read the relevant editor README if needed:
- VS Code:
editors/vscode/package.json (commands, settings, chat participants)
- Neovim:
editors/neovim/README.md
- Emacs:
editors/emacs/README.md
- Zed:
editors/zed/README.md
- Helix:
editors/helix/README.md
- Sublime Text:
editors/sublime-text/README.md
- JetBrains:
editors/jetbrains/README.md
- If the user asked a general question ("what can you do?", "help"),
give an overview of all feature areas with brief descriptions.
- Always mention that the same analysis engine powers all surfaces:
the LSP server, the MCP tools, the Claude Code skills, and the VS Code
chat participants.
Output format
- Group features by surface area: Editor (LSP), AI Chat (VS Code),
Claude Code Skills, MCP Tools
- Use concise bullet lists
- Highlight the most useful commands for the user's context
- If the user's question is about a specific editor, include setup
instructions from the relevant README
$ARGUMENTS
