TechTideOhio Core Repo Reconnaissance
Use the agent to map an unfamiliar repository before implementation by finding entrypoints, commands, ownership boundaries, risks, and tests.
Verified Surface
- Provider lane: core
- Native surface: SKILL.md skill packages
- Harness export: core
- Import mode: techtide-synthesis
- Source evidence: load
references/source-evidence.mdbefore promoting third-party material.
Workflow
- Read package manifests, root guidance, tests, CI, and likely entrypoints first.
- Identify framework, runtime, data stores, deployment path, and build artifacts.
- Find the smallest files that govern the requested behavior.
- Record unknowns that require live verification instead of guessing.
- Return a compact implementation map with risk notes.
Output Contract
Return:
- provider lane and native surface
- source evidence used
- promotion decision or operating recommendation
- security and privacy notes
- verification still required
Guardrails
- Keep third-party source bodies out of public artifacts unless direct import has clean license, attribution, and manual review.
- Do not use star counts, popularity, screenshots, or social posts as the sole evidence for promotion.
- Do not install or execute unreviewed external scripts as part of source research.
- Quarantine missing licenses, unclear ownership, vague prompt packs, duplicate skill packs, and unsupported native-surface claims.
- Preserve Alex Cinovoj / TechTide ownership for TechTide-authored synthesis while citing third-party sources as references.