agentsclimarketplace

Llm wiki claim anchors

Skill po4yka/llm-wiki-skills/skills/llm-wiki-claim-anchors

Portable Agent Skills for building, operating, evaluating, and governing LLM-Wiki knowledge systems.

Install
npx -y skills add po4yka/llm-wiki-skills --skill llm-wiki-claim-anchors

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Insert deterministic claim and source anchor IDs after evidence has been inspected. Use when the user wants stable claim IDs, source anchor IDs, support-label formatting, anchor validation, or reproducible claim references; route missing-evidence investigation to llm-wiki-provenance.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.0 KB, as published. Nobody here has run it

LLM-Wiki Claim Anchors

Goal

Add stable, auditable claim and source anchors to important wiki pages.

When to use

  • The user wants stable claim IDs or source anchor IDs added to a wiki page or folder.
  • A high-impact recommendation or synthesis page needs auditable provenance before it is trusted or merged.
  • The user asks to validate existing claim/source anchors or check anchor formatting.
  • llm-wiki-provenance has flagged unsupported, ambiguous, or conflicting claims that need anchors or a gap report.

Inputs

  • Target wiki pages or folders.
  • Raw sources or source pages.
  • Desired mode: report-only or patch.
  • Existing provenance conventions if present.

Procedure

1. Read the convention

Use references/docs/provenance/claim-anchors.md when available.

Default format:

- Claim text. ^claim-YYYYMMDD-001
  - Support: extracted
  - Source: `raw/sources/example.md` ^src-YYYYMMDD-001

2. Select claims

Prioritize:

  • high-impact recommendations;
  • current-state claims;
  • claims used in synthesis;
  • claims marked verified/reviewed;
  • claims found by llm-wiki-provenance.

Re-verify current-state claims (pricing, versions, release status, provider support) against fresh sources before anchoring them as extracted rather than inferred.

3. Classify support

Use:

extracted | inferred | ambiguous | synthesis | unsupported | conflicting

Do not upgrade unsupported claims to inferred just to make the page look complete.

4. Add anchors

In patch mode:

  • preserve wording unless the user asks for edits;
  • add claim anchors near the claim;
  • add source anchors near supporting source references;
  • avoid changing human-owned synthesis except to add explicit provenance notes when approved.

5. Validate

Run or recommend:

node scripts/validate-claim-anchors.mjs <wiki-or-file-path>

6. Report gaps

Create or update a provenance report for unsupported, ambiguous or conflicting claims.

Output

## Claim anchor summary

## Pages inspected

## Anchors added or proposed

## Unsupported claims

## Ambiguous or conflicting claims

## Validation result

## Review required

Safety gates

  • Do not fabricate source anchors.
  • Do not edit the meaning of a claim while adding anchors.
  • Do not mark claims verified.
  • Do not expose sensitive source excerpts unnecessarily.
  • Do not add anchors to human-owned sections without approval.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.