Read the file and its scope
AGENTS.md, CLAUDE.md and SKILL.md are commonly used as human-readable instructions for agent workflows, but the meaning of each depends on the tool that consumes it. Start by locating the file in the project and reading its headings, paths and referenced files. Treat a statement such as “always run tests” as a requirement to check in that workflow, not proof that tests ran.
For Cursor, the current Rules documentation explains project instructions and scope. For Claude Code, consult its settings documentation. Agent products evolve; a Markdown viewer cannot tell you which instruction file a specific version loaded or in what precedence order.
Review for human clarity
Ask three questions: What files or tasks does this rule apply to? What action does it require? How would someone notice that it was followed? Broken links, ambiguous path globs and outdated commands are easier to spot when you read the file as a document with its surrounding folder.
The Agent Review Pack provides a plan and checklist for a similar review habit. Aero Markdown can display local instruction files, but it is not an agent runner, policy checker or validator. Its Mac app is not publicly available yet. For plans produced by agents, use the plan review guide.