IMPLEMENTAUDIT
On this page
  1. Skills CLI path
  2. Claude Code path
  3. Codex release asset path
  4. Source checkout path
  5. First run after install
  6. Verification boundary
  7. After install
  8. Updating later
First run

Installation

This portal keeps installation early, but separates install proof from run proof.
Package extraction can be verified; host loading and audit correctness still need their own evidence.

The v0.3.3.3 URLs below are the intended final release routes, but do not establish that the correction candidate is already available. The runtime version remains 0.3.3. Until publication and readback complete, use the source route or verify the release assets before installation.

Skills CLI path

The repository is discoverable through the open skills CLI directory. Install from the current repository source with:

Skills CLIsource
$ npx --yes skills add theislampill/IMPLEMENTAUDIT.md

This route follows the repository's current source and is distinct from a checksum-verified GitHub release asset. It does not prove refresh behavior, auto-update, marketplace verification, release-byte identity, or host loading.

Claude Code path

Use Claude Code's current plugin or skill-install instructions for this repository, then verify the host shows the skill before treating it as loaded.
This docs portal does not claim marketplace behavior unless that host path was tested during a release gate.

If you are copying a release asset into a Claude Desktop-style local skill directory, use the repo helper and pass the actual session skill directory you inspected:

Claude release copyinstall
$ bash scripts/install-claude-from-release.sh \
  --url https://github.com/theislampill/IMPLEMENTAUDIT.md/releases/download/v0.3.3.3/IMPLEMENTAUDIT.skill \
  --claude-skills-dir "<path-to-claude-skills/implementaudit>"

That helper is a file-copy workaround.
It proves extraction and placement only; it does not prove Claude Desktop import, runtime loading, or marketplace installation.

Codex release asset path

Codex release copyinstall
$ bash scripts/install-codex-from-release.sh \
  --url https://github.com/theislampill/IMPLEMENTAUDIT.md/releases/download/v0.3.3.3/IMPLEMENTAUDIT.skill \
  --codex-home "$HOME/.codex" \
  --version 0.3.3

The local checksum check verifies artifact integrity when a checksum manifest is supplied.
The exact final correction candidate is a 257,998-byte IMPLEMENTAUDIT.skill with SHA-256 0e10a21600062c6f7cd440a6efb0ff3b795ce1a01067efb4005c7a176db02413. The release URL is not treated as serving those bytes until publication and independent public readback complete. These are artifact-integrity facts, not a signature, attestation, SBOM, provenance chain, or host-load proof.

For a manual Codex copy from a checkout, repeat the copy when the package changes:

Manual Codex copyunix
$ mkdir -p ~/.codex/skills/implementaudit
$ cp -R skills/implementaudit/* ~/.codex/skills/implementaudit/

On Windows PowerShell, the same shape is:

Manual Codex copypowershell
PS> New-Item -ItemType Directory -Force "$env:USERPROFILE\.codex\skills\implementaudit" | Out-Null
PS> Copy-Item -Recurse -Force .\skills\implementaudit\* "$env:USERPROFILE\.codex\skills\implementaudit\"

Source checkout path

When installing from a local checkout instead of a release tag, build and check the archive before copying it into a host directory:

Source checkout installlocal
$ bash scripts/build-release-asset.sh
$ bash scripts/write-release-checksums.sh dist/IMPLEMENTAUDIT.skill dist/CHECKSUMS.txt
$ bash scripts/write-release-checksums.sh --check dist/IMPLEMENTAUDIT.skill dist/CHECKSUMS.txt
$ bash scripts/install-codex-from-release.sh \
  --asset dist/IMPLEMENTAUDIT.skill \
  --checksum dist/CHECKSUMS.txt \
  --codex-home "$HOME/.codex" \
  --version 0.3.3

First run after install

First runsmoke
/implementaudit add tests for the login timeout bug

Look for a run folder and state file for phased work, or a bound work record for compact work, plus before/after checks and closure markers.
No commit, push, tag, release, publication, or provenance action is implied.

Verification boundary

Install evidence has levels:

  • Archive-shape validation checks package contents.
  • A checksum match verifies the asset against a manifest when one is supplied.
  • A copied skill folder can prove files were placed.
  • Only the host can prove the skill loaded.
  • Keep those claims separate when debugging.

Re-check before claiming release status:

  • The release tag exists.
  • Assets can be read.
  • CHECKSUMS.txt verifies artifact integrity when supplied; final v0.3.3.3 release-page, checksum, and fresh-download digests remain pending until the publication readback is recorded.
  • Pages is current only after deploy success.
  • Local installs do not auto-update.

After install

The practical smoke is a small repo request.
For phased work, look for a run folder and STATE.md; for compact work, look for the bound work record.
Either way, check before/after evidence and AUDIT_COMPLETE before IMPLEMENTAUDIT_RUN_COMPLETE.

Updating later

This repo does not claim passive host updating.
Reinstall or refresh the skill using the host's documented update path or the release-asset helper, then rerun a small repo request and check the visible version and closure markers.

Claude Desktop users should restart Claude Desktop after a copied skill update and verify the skill inside the host.
Session-managed skill paths can change between Claude Desktop versions; if the path differs, use the host's built-in skill management UI.