Back to skills
SkillHub ClubAnalyze Data & AIFull StackData / AI
claude.ai
Imported from https://github.com/InSelfControll/ai-agent-skills.
Packaged view
This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.
Stars
0
Hot score
74
Updated
March 20, 2026
Overall rating
C0.0
Composite score
0.0
Best-practice grade
F0.0
Install command
npx @skill-hub/cli install inselfcontroll-ai-agent-skills-claude-ai
Repository
InSelfControll/ai-agent-skills
Skill path: claude.ai
Imported from https://github.com/InSelfControll/ai-agent-skills.
Open repositoryBest for
Primary workflow: Analyze Data & AI.
Technical facets: Full Stack, Data / AI.
Target audience: everyone.
License: Unknown.
Original source
Catalog source: SkillHub Club.
Repository owner: InSelfControll.
This is still a mirrored public skill entry. Review the repository before installing into production workflows.
What it helps with
- Install claude.ai into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
- Review https://github.com/InSelfControll/ai-agent-skills before adding claude.ai to shared team environments
- Use claude.ai for development workflows
Works across
Claude CodeCodex CLIGemini CLIOpenCode
Favorites: 0.
Sub-skills: 0.
Aggregator: No.
Original source / Raw SKILL.md
--- name: claude.ai description: Specialized for# Claude.ai Specialized Skill This skill optimizes interactions with Claude models, focusing on XML-based orchestration, tool-use efficiency, and high-fidelity output for complex coding tasks. ## Core Capabilities ### 1. XML Orchestration * **Structure:** Always wrap discrete outputs in standard XML tags (e.g., `<thought>`, `<implementation>`, `<verification>`). * **Hierarchy:** Use nested tags for complex data structures to help the model maintain logical separation. * **Clarity:** Use XML comments `<!-- ... -->` to provide meta-instructions to the model within its own output. ### 2. Advanced Tool Use * **Chaining:** Predict next steps and prepare tool inputs in batches when possible. * **Error Recovery:** Implement retry logic with specific instruction modifications if a tool fails (e.g., adjusting a search query or file path). * **State Management:** Maintain a "mental model" of the file system and project state within a `<context>` tag to reduce redundant `list_dir` or `view_file` calls. ### 3. Prompt Engineering Standards * **Few-Shotting:** Provide examples of the desired output format for complex tasks. * **Chain of Thought:** **MANDATORY** use of `<thought>` tags before generating any code or technical recommendations. * **Style:** Maintain a "Principal Engineer" persona: concise, direct, and security-aware. ### 4. Long Context Optimization * **Summarization:** Periodically summarize long conversation histories within the context to preserve important decisions. * **Focus:** Explicitly tell the model what folders or files to ignore to reduce "noise" in its reasoning. ## Interaction Protocol * **Input:** High-complexity multi-file coding tasks or systemic architectural changes. * **Output:** Orchestrated XML-wrapped responses with precise tool calls and technical explanations. **Tag**: Start your response with `[CLAUDE-EXPERT]`.