markdowntown-atlas-scan

Atlas Simulator scan flow and next-step guidance for markdowntown. Use when working on folder scanning, tool detection, cwd handling, results panels, or scan-to-workbench CTAs.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 4, 2026⬇️1downloads

When & Why to Use This Skill

The markdowntown-atlas-scan skill is a specialized developer utility designed to streamline the Atlas Simulator workflow. It provides comprehensive guidance for folder scanning, tool detection, and environment configuration, ensuring that developers can efficiently transition from initial directory analysis to an active workbench session with full context preservation.

Use Cases

  • Case 1: Automating local folder scans to detect tool compatibility and validate current working directory (CWD) handling for ancestor-scanning tools.
  • Case 2: Troubleshooting simulation results by analyzing scan metadata and identifying missing or incorrectly loaded files within the Atlas environment.
  • Case 3: Optimizing the user journey from scan results to the Workbench using context-aware 'Next Steps' and primary Call-to-Action (CTA) routing.
  • Case 4: Implementing guardrails for local-only file scanning to ensure data privacy and handling permission or truncation errors with clear, actionable feedback.
namemarkdowntown-atlas-scan
descriptionAtlas Simulator scan flow and next-step guidance for markdowntown. Use when working on folder scanning, tool detection, cwd handling, results panels, or scan-to-workbench CTAs.

markdowntown-atlas-scan

Core workflow

  1. Confirm entry points to /atlas/simulator and the primary scan action.
  2. Validate tool detection and cwd behavior for ancestor-scanning tools.
  3. Ensure results highlight missing/loaded files and scan metadata.
  4. Keep the Next steps panel prominent and action-oriented.
  5. Route users into Workbench with scan context intact.

Guardrails

  • Scans are local-only; do not upload file contents.
  • Handle permission errors, empty scans, and truncated scans with clear copy.
  • Prefer one primary CTA per results state.

References

  • docs/atlas/simulator.md
  • docs/atlas/scan-next-steps.md
  • docs/architecture/atlas-simulator-flow.md
  • docs/ui/scan-flow.md
  • codex/skills/markdowntown-atlas-scan/references/atlas-docs.md
  • codex/skills/markdowntown-atlas-scan/references/atlas-source.md