Loading…
Build or update a canonical EPISTEMIC-MAP.md sorting a project's knowledge into four states: validated Facts, open Questions, undocumented Assumptions, and inferred Risks. Purpose-built for prototype-to-production handoff, where a signed contract means a new engineering team must take over before the original builder's tacit knowledge walks out the door. Spawns subagents across docs and the codebase to find what's proven, what's asked, what's silently assumed, and what nobody has noticed, then runs a dedicated synthesis pass for systemic risks no single source states. Use whenever a user mentions "epistemic map", "knowledge map", "EPISTEMIC-MAP.md", "known unknowns", "unknown unknowns", "what do we actually know vs assume", "map our assumptions", "handoff risk map", "prototype handoff", or "onboarding a team onto a prototype". Always prefer this skill over ad-hoc knowledge-gap documentation.
epistemic-mapper is an agent skill entry in ChatHome Skills, sourced from GitHub Skill Search and scored 58/100. # Epistemic Mapper Extract a project's knowledge state from its documentation and its code, then sort every observation into one of four quadrants and write the. As an agent skill, it packages a reusable instruction set that AI coding agents such as Codex and Claude Code can load to perform this task without hand-written glue code. ChatHome Skills discovered this entry through its daily ingest of official registries and GitHub discovery queries, and re-verifies repository facts, freshness signals, and install metadata on every run. The quality score weighs official-registry presence, a working install command, license clarity, GitHub star trajectory, and repository freshness — the full formula is on the Sources page. The install command above is ready to copy. Review the last-pushed date and repository status before adding epistemic-mapper to a production agent workflow; the snapshot facts below are point-in-time values from the most recent ingest.
codex skill install Mr-Nobody-Anonymous/All-skillsReview the upstream source before running this command.
Scan coverage: Install metadata and the indexed document body.
Automated signals from install metadata and a bounded skill body — not a full code security audit and not a recursive source or dependency review.
# Epistemic Mapper Extract a project's knowledge state from its documentation and its code, then sort every observation into one of four quadrants and write the result into a canon