smithery/dot-agents

Agent Start

Begin each work session by understanding the current state and context

Installation

$ npx skills add smithery/dot-agents --skill agent-start

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/dot-agents.

npx skills add smithery/dot-agents

Browse all from smithery/dot-agents

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,319 B
  • docs SUMMARY.md 89 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Agent Start

Begin each work session by understanding the current state and context.

When to Use

  • At the start of a new conversation or coding session
  • When resuming work after a break
  • When switching to a different task

Steps

  1. Check for existing context

- Read any TODO comments or task lists in the codebase - Check for .claude/rules/ or project documentation - Review any pinned messages or session notes

  1. Understand the current state

- Run git status to see uncommitted changes - Review recent commits with git log --oneline -5 - Check for any failing tests or build issues

  1. Identify the current task

- Ask the user what they want to work on if not clear - Review any linked issues or tickets - Check the project backlog if available

  1. Plan before coding

- Break down complex tasks into smaller steps - Identify files that will need changes - Consider edge cases and potential issues

Notes

  • Don't start coding until you understand the goal
  • Ask clarifying questions if requirements are unclear
  • If picking up someone else's work, read their notes first
  • Check for any blockers or dependencies before diving in