How do I install the Steer skill?

Run npx skillmds@latest add amhuppert/steer 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 Steer safe to use?

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

Which AI agents work with Steer?

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 Steer free to use?

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

amhuppert (@amhuppert) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Steer by amhuppert — Agent Skill

Name: Steer
Rating: 4.666666666666667 (3 reviews)
Author: amhuppert

File contents

Steer Reflection

Reflect on the current conversation to evaluate codebase navigation effectiveness. Present findings so the user can decide what to persist via /kiro:steering-custom.

Arguments

Topic name: use the topic supplied in the user's invocation.

If no topic name provided, derive one from the conversation's primary task using kebab-case (e.g., api-client, installer-scripts, mcp-server).

Step 1: Reflect on Navigation

Analyze the full conversation history. For each question below, cite specific examples from the conversation:

Efficiency — How many tool calls were spent on navigation (file reads, searches, globs)? How many were productive vs. wasted?
Dead ends — List specific instances of searching for something and not finding it, or reading files that turned out to be irrelevant.
Missing context — What information, if available at the start, would have made navigation significantly easier? Consider:
- Key file paths discovered late
- Directory structures that weren't obvious
- Naming conventions that caused confusion
- Relationships between files that weren't documented
Improvement opportunities — What concrete changes would make this type of task easier next time?

Step 2: Synthesize Actionable Guidance

Based on the reflection, draft a concise summary of navigation guidance that could become a steering document. Present it using this structure:

Key Files

path/to/file - what it contains and when it's relevant

Navigation Tips

Concise, actionable tips for finding what you need for this type of task

Common Pitfalls

Things that look relevant but aren't
Non-obvious file locations or naming conventions

Omit any section from the template that has no meaningful content. Do not pad with generic advice.

Step 3: Present and Suggest Next Steps

Present the full reflection and synthesized guidance to the user. Then suggest:

To persist these insights as a steering document, run /kiro:steering-custom and reference the topic {topic-name}.

Do NOT write any files. The user decides what to persist and when.

---name: steerdescription: Reflect on codebase navigation effectiveness at end of conversation. Surfaces dead ends, inefficiencies, missing context. Does not write files — pair with /kiro:steering-custom to persist.---# Steer ReflectionReflect on the current conversation to evaluate codebase navigation effectiveness. Present findings so the user can decide what to persist via `/kiro:steering-custom`.## ArgumentsTopic name: use the topic supplied in the user's invocation.If no topic name provided, derive one from the conversation's primary task using kebab-case (e.g., `api-client`, `installer-scripts`, `mcp-server`).## Step 1: Reflect on NavigationAnalyze the full conversation history. For each question below, cite specific examples from the conversation:1. **Efficiency** — How many tool calls were spent on navigation (file reads, searches, globs)? How many were productive vs. wasted?2. **Dead ends** — List specific instances of searching for something and not finding it, or reading files that turned out to be irrelevant.3. **Missing context** — What information, if available at the start, would have made navigation significantly easier? Consider: - Key file paths discovered late - Directory structures that weren't obvious - Naming conventions that caused confusion - Relationships between files that weren't documented4. **Improvement opportunities** — What concrete changes would make this type of task easier next time?## Step 2: Synthesize Actionable GuidanceBased on the reflection, draft a concise summary of navigation guidance that could become a steering document. Present it using this structure:<constraints>- Maximum 40 lines- Include only actionable navigation guidance, not general observations- Use specific file paths and directory names- Scope to the feature/task — not the whole codebase</constraints><template># {Topic Title}## Key Files- `path/to/file` - what it contains and when it's relevant## Navigation Tips- Concise, actionable tips for finding what you need for this type of task## Common Pitfalls- Things that look relevant but aren't- Non-obvious file locations or naming conventions</template>Omit any section from the template that has no meaningful content. Do not pad with generic advice.## Step 3: Present and Suggest Next StepsPresent the full reflection and synthesized guidance to the user. Then suggest:> To persist these insights as a steering document, run `/kiro:steering-custom` and reference the topic **{topic-name}**.Do NOT write any files. The user decides what to persist and when.

Frequently asked questions

Steer