agentsclimarketplace

Llm wiki github action

Skill po4yka/llm-wiki-skills/skills/llm-wiki-github-action

Configure GitHub Actions for LLM-Wiki maintenance. Use when the user wants scheduled wiki lint reports, PR-based documentation updates, Agent Skills validation, provenance checks, or safe repo-docs maintenance without direct writes to main.From its SKILL.md

Install
npx -y skills add po4yka/llm-wiki-skills --skill llm-wiki-github-action

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 file declares

Copied from the file, not written here

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

4.7 KB, 892 tokens by cl100k_base, as published. Nobody here has run it

LLM-Wiki GitHub Action

Goal

Create safe GitHub Actions workflows for LLM-Wiki validation and maintenance.

When to use

  • The user wants a scheduled wiki-lint or wiki-health report published as a workflow artifact.
  • The user wants PR-based automation for generated docs or maintenance changes and wants to avoid direct pushes to main.
  • The user needs Agent Skills frontmatter validation (or other repo-specific validation scripts) wired into CI.
  • The user wants to add or enable one of the starter evals, ingestion, publish, or security workflows.
  • The user is deciding what GitHub Actions permissions or triggers a wiki-maintenance job should have.

Starter templates

Use these local templates when available in a full repository checkout. In a single-skill install, recreate the same workflow shapes from this list:

  • llm-wiki-evals.github-actions.yml for retrieval, grounding, promptfoo and wiki-health checks.
  • llm-wiki-ingestion.github-actions.yml for source manifests, ingestion fidelity, parser security and retrieval smoke checks.
  • llm-wiki-publish.github-actions.yml for export profile validation, redaction/security checks, artifacts and optional Pages publish.
  • llm-wiki-security.github-actions.yml for secrets, dependency, OSV, Semgrep, red-team and export-policy checks.

The starter workflow schedules are commented out by default. Enable cron only after workflow_dispatch has run successfully and the repository owner accepts the recurring cost and external calls.

Inputs

  • Repository path.
  • Desired automation: validation, lint, scheduled report, maintenance PR, skill validation.
  • Permission constraints.
  • Whether Actions should write files, open PRs, or only upload reports.

Procedure

1. Choose automation mode

ModeUse when
report-onlyEarly adoption or sensitive repos.
artifact reportReports should not change the repo.
PR-based updateGenerated output needs human review.
validationValidate schemas, links, skills and frontmatter.

Default to report-only or PR-based updates. Avoid direct pushes to main.

2. Define triggers

Start with manual and pull request triggers. Add a schedule only after the first manual run succeeds. Keep copied starter schedule: blocks commented until that happens.

on:
  pull_request:
  workflow_dispatch:

3. Set permissions narrowly

Use the least privilege required by the chosen mode. Read-only jobs should not request write permissions. PR-creation jobs should be clearly separated from validation jobs.

4. Add validation jobs

Possible jobs:

  • Agent Skills frontmatter validation for every skills/*/SKILL.md;
  • repository-specific validation scripts when the target repo already defines them;
  • frontmatter schema validation;
  • broken link scan;
  • wiki-lint report generation;
  • stale page report;
  • provenance gap report.

5. Add PR workflow only when safe

For PR-based updates:

  • create a branch;
  • commit reports or generated docs;
  • open PR with clear summary;
  • request review from owners;
  • never merge automatically.

6. Copy starter workflows deliberately

When the user asks for ready-made workflow files, copy only the relevant starters:

NeedStarter
evals and red-teamllm-wiki-evals.github-actions.yml
ingestion pipeline checksllm-wiki-ingestion.github-actions.yml
publish/export pipelinellm-wiki-publish.github-actions.yml
security scansllm-wiki-security.github-actions.yml

Rename each copied file to .github/workflows/<purpose>.yml, replace placeholder commands, and keep permissions minimal. Re-verify that the pinned action versions and commands in a copied starter are still current for the target repository's toolchain before enabling its trigger.

Output

## GitHub Actions plan

## Workflow files created or proposed

## Permissions

## Triggers

## Safety model

## Manual verification steps

Safety gates

  • Do not grant broad write permissions without justification.
  • Do not configure direct pushes to main for generated knowledge.
  • Do not run external model calls on private content without explicit approval.
  • Do not hide generated changes outside pull-request review.

What ships with it: 4 files

12.4 KB alongside SKILL.md

Gives 0 of the 12 instructions most docs writing skills give in 892 tokens

Counted across 1,637 of the 3,044 authors here whose files we hold, read 2026-08-07

  • Announce the skill at startin 54 of 1637, across 26 files
  • Convert legacy doc files before editingin 45 of 1637, across 7 files
  • Predict questions readers might askin 42 of 1637, across 4 files
  • Generate clarifying questions for initial contextin 42 of 1637, across 3 files
  • Create document scaffold with placeholder textin 42 of 1637, across 3 files
  • Brainstorm content options for each sectionin 42 of 1637, across 3 files
  • Test the document with a fresh context-less instancein 42 of 1637, across 3 files
  • Include exact file paths in every taskin 42 of 1637, across 15 files
  • Ask interview questions one at a timein 42 of 1637, across 27 files
  • Apply surgical edits during refinementin 41 of 1637, across 2 files
  • Offer structured workflow or freeformin 40 of 1637, across 1 file
  • Ask for document meta-contextin 40 of 1637, across 2 files

Said here and by no other author read

  • default to report-only or PR-based updates
  • avoid direct pushes to main
  • start with manual and pull request triggers
  • add a schedule only after the first manual run succeeds
  • use the least privilege required
  • separate PR-creation jobs from validation jobs

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,834. 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.