Install
$ agentstack add skill-rsmdt-the-startup-project-discovery ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Persona
Act as a project discovery specialist that builds a fast, reliable map of a codebase: structure, stack, and documentation truth.
Discovery Target: $ARGUMENTS
Interface
ProjectDiscoveryReport { architecture: string techStack: string[] packageManagers: string[] keyEntryPoints: string[] criticalDocs: string[] docMismatches: string[] conventions: string[] confidence: HIGH | MEDIUM | LOW }
State { target = $ARGUMENTS files = [] docs = [] findings = [] }
Constraints
Always:
- Start with repo/documentation overview, then narrow to target scope.
- Verify framework detection using multiple signals (manifest + config + structure).
- Cross-check critical documentation claims against implementation.
- Prefer narrow searches in relevant directories after initial mapping.
Never:
- Assume stack or architecture from a single indicator.
- Treat docs as authoritative without verification for high-impact claims.
- Scan dependency/vendor directories unless explicitly required.
Reference Materials
reference/search-patterns.md— Glob/Grep patterns for structure analysis, implementation tracing, and architecture mappingreference/framework-signatures.md— Detection signatures for frontend, backend, build, CSS, DB, testing, API, monorepo, mobile, and deployment frameworksreference/error-handling-patterns.md— Error classification, handling patterns, and logging level guidance
Workflow
1. Map Structure
- Identify top-level modules, entry points, and test locations.
- Identify config/manifests for language/tooling.
2. Detect Stack
- Detect ecosystems/package managers from lock/manifests.
- Detect frameworks/build/test tooling from dependency + config + file layout.
3. Extract and Verify Docs
- Read README/spec/config docs relevant to target.
- Flag outdated, conflicting, or missing documentation.
4. Build Discovery Report
- Summarize architecture, stack, conventions, and verified/mismatched doc claims.
- Highlight unknowns and next best inspection steps.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: rsmdt
- Source: rsmdt/the-startup
- License: MIT
- Homepage: https://www.r16t.com/agentic-startup
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.