codyswanngt/lisa-wiki-status
plugins/lisa-wiki-agy/skills/lisa-wiki-status/SKILL.md
Report Lisa wiki source freshness across enabled ingestion connectors. Reads wiki config, log, source notes, and state cursors, then renders a concise read-only freshness table with skipped/blocker reasons and exact next actions. Use when maintainers ask whether the wiki sources are fresh, stale, skipped, blocked, or need targeted ingest.
$ install --global
skillsauthnpx skillsauth add codyswanngt/lisa lisa-wiki-statusInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 6, 2026, 3:55 AM38.5s1 file scanned
SKILL.md
- name:
- lisa-wiki-status
- description:
- Report Lisa wiki source freshness across enabled ingestion connectors. Reads wiki config, log, source notes, and state cursors, then renders a concise read-only freshness table with skipped/blocker reasons and exact next actions. Use when maintainers ask whether the wiki sources are fresh, stale, skipped, blocked, or need targeted ingest.
- allowed-tools:
- ["Bash", "Read"]
lisa-wiki-status
Render the Lisa wiki source freshness report without changing the repository.
Scope
This skill answers a narrower question than lisa-wiki-doctor or lisa-wiki-lint: whether each enabled, non-external-write ingestion connector has current source evidence and what the operator should do next.
Read these repository files as the source of truth:
wiki/lisa-wiki.config.jsonfor enabled connectors and wiki root.wiki/log.mdfor latest ingest, skip, and blocker notes.wiki/sources/**for reader-safe source notes.wiki/state/**for connector state cursors and source-note references.
Workflow
-
Resolve the wiki root from
wiki/lisa-wiki.config.json, unless--wikior--configis passed. -
Run the bundled deterministic renderer:
node plugins/lisa-wiki/scripts/wiki-status.mjs $ARGUMENTSIf running from the source plugin tree before distribution, use
plugins/src/wiki/scripts/wiki-status.mjs. -
Report the rendered connector table. Preserve connector verdicts exactly:
fresh,stale,never_ingested,skipped, orblocked. -
Include the evidence paths, last observed date, skip/blocker reason when present, and exact next action for each non-fresh connector.
-
Mention
lisa-wiki-lintonly as a separate integrity follow-up. Do not conflate freshness with broken links, stale claims, or structure linting.
Rules
- Read-only. Do not ingest, edit wiki pages, edit config, advance state, branch, commit, push, open PRs, or run repair flows.
- Do not ask for confirmation before rendering. This status command has no write side effects.
- Do not use global Codex memory or non-project memory as fresh wiki evidence. Only project-scoped source notes, state, and log entries count.
- If the wiki/config is missing, surface the renderer output or error directly and stop.
- If a connector is skipped because project-scoped memory is unavailable, preserve that reason and treat accepting the expected skip as a valid next action.
Related
lisa-wiki-ingest refreshes sources, lisa-wiki-lint checks wiki integrity, and lisa-wiki-doctor verifies setup/readiness.
Related Skills
codyswanngt/lisa-setup-workstation
development
VerifiedTrustedCommunity
Prepare a machine — a fresh laptop or a throwaway container — to run coding agents, before any repository exists. Detects which of Lisa's supported agents (Claude Code, Codex, Cursor, OpenCode, Antigravity, Copilot) are already installed, asks which credential manager the machine uses (Bitwarden, 1Password, Doppler, Vault, AWS, or none), and installs only what is missing, each by its vendor's own preferred method. Idempotent, headless by default, and emits a Dockerfile for a spin-up/spin-down environment. Run it on a new machine, in a container, or before cloning anything.
3SKILL.mdUpdated Aug 30, 2026
codyswanngt/lisa-setup-remote-env
tools
VerifiedTrustedCommunity
Provision and verify a remote execution environment for a host project — Codex Cloud today, other remote surfaces as they are added. Generates a repository-owned setup script that installs the declared toolchain, materializes secrets through lisa-secrets-access, and runs the project's own hook. Provisions by API where one exists, by driving the vendor console where one does not, and by emitting exact config otherwise — then proves the result with the same read-back regardless of which tier did the work. Use before dispatching any work with executionEnv.
3SKILL.mdUpdated Aug 30, 2026
codyswanngt/lisa-setup-local-env
tools
VerifiedTrustedCommunity
Bring a developer's machine in line with the toolchain the project declares. Reports every tool in remoteEnv.tools that is missing, outdated, or unpinned for this platform, and installs the missing ones into ~/.local/bin from the same pinned, checksummed entries the remote surfaces use — but only when asked. Same manifest, same pins, same installers as lisa-setup-remote-env; what differs is consent and that the pin is a floor rather than an equality. Run it on a fresh checkout, after a manifest change, or when a tool fails at the moment of use.
3SKILL.mdUpdated Aug 30, 2026
codyswanngt/lisa-remote-dispatch
tools
VerifiedTrustedCommunity
Route one unit of work to a remote execution surface. Reads the executionEnv parameter (local by default, codex-cloud or claude-web today), verifies the environment is provisioned and bound to this repository, submits a thin skill invocation, records the task identifier to .lisa/remote-dispatch.json, and exits without polling. Routing only — the remote runs the identical skill from the identical repository. Composable and inline: other skills invoke it via the Skill tool rather than users calling it directly.
3SKILL.mdUpdated Aug 30, 2026