Skip to content

Reshape README as a signpost#2

Merged
monoxgas merged 1 commit intomainfrom
nick/readme-signpost
May 4, 2026
Merged

Reshape README as a signpost#2
monoxgas merged 1 commit intomainfrom
nick/readme-signpost

Conversation

@monoxgas
Copy link
Copy Markdown
Contributor

@monoxgas monoxgas commented May 4, 2026

Summary

  • Recasts the README as a signpost rather than a destination — orients landing users toward the TUI, CLI, web catalog, and docs instead of trying to host install flows itself.
  • Adds a one-paragraph "what's a capability" with a 4-line tree so a reader has a mental model before clicking out.
  • "Looking to use one?" answers the specific question of how to get these capabilities (real names, no placeholders, no broken deep link to the org-scoped catalog page).
  • "Curious how they work, or want to build one?" affirms the value of the source tree as worked examples and points to overview / manifest / quickstart.

Test plan

  • Render the README on the PR page and confirm tree, links, and tone read well
  • Verify docs.dreadnode.io/capabilities/installing and sibling doc URLs resolve
  • Confirm dn capability install dreadnode/ai-red-teaming is the correct registry name format

🤖 Generated with Claude Code

Frames the repo as the source for dreadnode/* capabilities and routes
landing users to the right resource — TUI, CLI install, or local
checkout — with concrete examples that name a real capability rather
than placeholder slugs. Conceptual and build-it questions point at the
overview, manifest, and quickstart docs.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@monoxgas monoxgas merged commit 7577df5 into main May 4, 2026
4 checks passed
@monoxgas monoxgas deleted the nick/readme-signpost branch May 4, 2026 20:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant