More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    One Source of Truth for Project Documentation

    1

    Stop guessing after two failed fixes: one register of canonical docs per project, an evidence ladder, and a drift check at every version bump.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    One Source of Truth for Project Documentation

    One Source of Truth for Project Documentation

    Example session with this skill installed

    Our dashboard uses Harbor Charts, a fictional charting library, pinned at 3.2. After bumping to 3.3, tooltips stopped appearing on bar charts. Two developers already tried rewiring the tooltip handler and checking for a renamed option, and both attempts failed. Tell us what to do next, and set up the register so this does not repeat.

    • Read your context and instructions
    • Compiled the one source

    TWO STRIKES REACHED — Rewiring the handler and checking for a renamed option are two distinct hypotheses, both tested, both failed. Guessing stops here, per the rule.

    REGISTER ROW BUILT — Component: Harbor Charts, as imported. Canonical reference: the maintainer's API reference, tooltips section, pinned version recorded as 3.2 (now 3.3 after the bump), last verified: today. Notes column started with the setup gotcha found during install: tooltips default off unless the chart container has an explicit height.

    EVIDENCE LADDER APPLIED — The changelog for 3.3 (tier 2) states: from 3.3, tooltips require the chart to be wrapped in a tooltip provider component, new in this version. The tier 1 reference for 3.3 confirms the provider and its required prop. No tutorial or memory claim was used to settle it.

    FIX — Wrap each bar chart in the tooltip provider, one line per chart, then re-run the dashboard's chart tests. Row updated: pinned 3.3, verified today, note added: "tooltips require the provider wrapper from 3.3 onward." Next bump: the drift check runs in the same change as the version bump, changelog skimmed before merging, so the next person opens one row instead of repeating two failed guesses.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Every project accumulates confident guesses about how its libraries behave, left unchecked since the last person looked. This skill installs one habit and one artifact. The habit is mechanical: two failed fix attempts, then the canonical documentation — it fires regardless of how sure you feel about attempt three. The artifact is a doc register, one row per component, recording the canonical reference by publisher, title, and section, the pinned version the project actually runs, and the date someone last verified the two match. The skill also gives an evidence ladder ranking five source tiers from pinned-version official reference down to memory, a protocol for adding a dependency that makes its register row part of installation, a version-drift check to run at every bump, and a rubric scoring register health across coverage, version accuracy, freshness, evidence quality, and real use. A worked example follows a fictional form-library upgrade where the changelog answers in minutes what two guesses could not, and the quality gate requires every fix to trace to the top evidence tiers or be recorded as a finding.

    • It cannot verify a reference it cannot see; if the documentation is behind access you do not have, the register records the gap as a finding.
    • When the official reference itself is wrong or silent, the skill falls back to a recorded test, not a stronger claim.
    • A register only helps if the team updates it; the skill includes a four-column fallback for teams that will not maintain a full table.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 3 days ago

    Permissions

    No special permissions declared or detected

    Listed3 days ago

    What's inside

    Frequently Asked Questions

    Record it as a finding in the register row: contract unverifiable. If the dependency is load-bearing, raise it before merging, because that is a team risk decision, not one installer's afternoon.

    No. It records where the contract lives, which version it applies to, and when it was last checked. The two-strike rule is what forces the reading; a register nobody opens is decoration.

    Yes: four columns only — component, reference, version, date — and the rule that the person touching a dependency updates its row in the same change.

    New in Technical Documentation