You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CRITICAL: Never provide level of effort time estimates(e.g., hours, days, weeks) for tasks. Focus solely on breaking down the work into clear, actionable steps without estimating how long they will take.
187
-
188
162
<skills_system priority="1">
189
163
190
164
## Available Skills
@@ -194,7 +168,8 @@ CRITICAL: Never provide level of effort time estimates(e.g., hours, days, weeks)
194
168
When users ask you to perform tasks, check if any of the available skills below can help complete the task more effectively. Skills provide specialized capabilities and domain knowledge.
195
169
196
170
How to use skills:
197
-
- Invoke: Bash("openskills read <skill-name>")
171
+
- Invoke: `npx openskills read <skill-name>` (run in your shell)
172
+
- For multiple: `npx openskills read skill-one,skill-two`
198
173
- The skill content will load with detailed instructions on how to complete the task
199
174
- Base directory provided in output for resolving bundled resources (references/, scripts/, assets/)
<description>Expert guidance for creating, writing, and refining Claude Code Skills. Use when working with SKILL.md files, authoring new skills, improving existing skills, or understanding skill structure and best practices.</description>
185
+
<name>analyzing-codebase</name>
186
+
<description>Semantic search, structure extraction, and call graph analysis for codebases using vector embeddings and tree-sitter. Use when working with code search, understanding code structure, or analyzing function call relationships.</description>
218
187
<location>project</location>
219
188
</skill>
220
189
221
190
<skill>
222
-
<name>planning-with-files</name>
223
-
<description>Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output.</description>
191
+
<name>chatting-ai</name>
192
+
<description>Interact with local AI assistants for conversational dialogue, automatically managing multi-turn conversation state. Use when you need to analyze code, refactor and optimize, write new features, debug issues, or seek technical consultation. Supports multiple input methods (direct input, files, pipes).</description>
<description>Creates code docs (with smart references and text charts) and task docs for development tracking. Use for architecture docs, flow diagrams, implementation planning, or when users mention code documentation, task docs, ASCII diagrams, smart references, or code flow visualization.</description>
0 commit comments