Research report · Run 5 · 25 September 2026
Superamped selected-file provenance recheck
A provenance-only recheck of four selected SKILL.md paths. It did not obtain a public record that directly attributes a selected-file commit and date to any path. The prior stop before an install recommendation remains.
Four paths, one unresolved provenance result
Each current file locator is a mutable main link. A path-history record, a commit detail that lists the path, or a path-filtered public API result is needed before a selected-file SHA/date can be reported.
| Entry | Selected-file SHA/date and attribution | Release and tag | Status |
|---|---|---|---|
| Content Strategy | Unavailable. No obtained public record ties a commit/date to this selected path. | Release: no direct coverage; the repository releases page says there are no releases. Tag: unavailable; the tags view did not load and no selected-file commit is available to relate to a tag. | Retain with caveat; stop before an install recommendation. |
| Competitor Discovery | Unavailable. No obtained public record ties a commit/date to this selected path. | Release: no direct coverage; the repository releases page says there are no releases. Tag: unavailable; the tags view did not load and no selected-file commit is available to relate to a tag. | Retain with caveat; stop before an install recommendation. |
| Search Page Audit | Unavailable. No obtained public record ties a commit/date to this selected path. | Release: no direct coverage; the repository releases page says there are no releases. Tag: unavailable; the tags view did not load and no selected-file commit is available to relate to a tag. | Retain with caveat; stop before an install recommendation. |
| Ad Campaign Analyzer | Unavailable. No obtained public record ties a commit/date to this selected path. | Release: no direct coverage; the repository releases page says there are no releases. Tag: unavailable; the tags view did not load and no selected-file commit is available to relate to a tag. | Retain with caveat; stop before an install recommendation. |
“Unavailable” does not mean that no commit or tag exists. It means this recheck did not obtain a public GitHub record that directly ties the selected path to the claimed commit/date or tag.
Source boundary
The recheck used public GitHub views for the four current selected-file pages, the repository root commit history, releases, and attempted path-history and tag pages. The repository establishes current availability only; it does not establish an immutable selected-file revision.
For each path, the requested path-history URL at commits/main/<selected-path> returned a research-browser cache miss rather than an attributable history record. The tags page also returned a cache miss. A root-history item, branch tip, immutable path URL at a root commit, or non-path-specific tag was not substituted for selected-file attribution.
The root history lists d6f66439359e5dd07073a989f3fc14036981ff8e, “align repository with Agent Skills standard,” dated 18 August 2026. That is a repository-level observation only, not the selected-file SHA/date for any of these paths.
What changed from the prior records
The 23 September provenance report already marked every selected-file SHA/date and tag finding unavailable, and treated d6f6643 as an unconfirmed repository snapshot. This recheck does not change that result. The releases page now supports the limited statement that the repository has no releases, but it does not provide direct coverage for any selected file.
The 24 September safe-evaluation report required a stop before an install recommendation for these four entries. That status is unchanged. The result is not evidence that a package is safe, installed, compatible, tested, or recommended to install.
What would resolve the gap
A future recheck needs a GitHub path-history result, a commit detail listing the exact selected path, or a public API path-filtered commit result. Only then can it report a SHA/date, and only if the source directly attributes that result to the path. A release or tag needs direct coverage for the selected file, or a directly supported relationship to an attributed selected-file commit.
Untested boundaries
No package, installer, host, plugin, clone, command, executable, dependency, or skill was installed, cloned, copied, executed, evaluated, or modified. No credentials, accounts, connectors, customer data, campaign data, target URLs, advertising accounts, or paid services were used. No security, privacy, compatibility, host behavior, marketing outcome, or performance claim was tested. This provenance research does not authorize installation, use, publishing, sending, deployment, or a spend change.
Sources: Superamped repository · root history · releases · tags · Run 4 safe-evaluation boundary. Checked 25 September 2026 UTC.