l3digitalnet/up-drift
plugins/up-docs/skills/drift/SKILL.md
Comprehensive documentation drift analysis across infrastructure and wiki by dispatching the up-docs-audit-drift sub-agent. This skill should be used when the user runs /up-docs:drift.
$ install --global
skillsauthnpx skillsauth add l3digitalnet/claude-code-plugins up-driftInstall 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: May 9, 2026, 8:27 AM146.0s3 files scanned
SKILL.md
- name:
- up-drift
- description:
- Comprehensive documentation drift analysis across infrastructure and wiki by dispatching the up-docs-audit-drift sub-agent. This skill should be used when the user runs /up-docs:drift.
- argument-hint:
- [collection-name]
- allowed-tools:
- Read, Bash, Agent, AskUserQuestion
/up-docs:drift [collection-name]
Run drift analysis via the up-docs-audit-drift sub-agent (Sonnet). Read-only by design: the auditor surfaces findings; the user decides whether to re-invoke propagators to fix them.
If a collection name is provided, scope the analysis to that Outline collection. Otherwise, analyze all collections.
Architecture
The auditor sub-agent runs the full four-phase drift flow in its own isolated context:
- Infrastructure → Wiki sync (SSH/pct/curl against live state)
- Wiki internal consistency (cross-reference map)
- Link integrity & enrichment
- Notion-relevance review
The phase mechanics (scripts/convergence-tracker.sh, scripts/server-inspect.sh, scripts/link-audit.sh) still live in this plugin — the sub-agent invokes them directly from its Bash tool.
Workflow
1. Gather Session Context
First, verify Python 3 is available — all helper scripts depend on it:
command -v python3 >/dev/null 2>&1 || { echo "ERROR: python3 not found in PATH — install python3 and retry."; exit 1; }
bash ${CLAUDE_PLUGIN_ROOT}/scripts/context-gather.sh
bash ${CLAUDE_PLUGIN_ROOT}/scripts/convergence-tracker.sh init
Combine with conversation history.
2. Build the Session-Change Summary
Read ${CLAUDE_PLUGIN_ROOT}/templates/session-change-summary.md for the canonical format. This grounds the auditor's scan — it starts from the summary items and expands to adjacent infrastructure that might be transitively affected.
3. Dispatch up-docs-audit-drift
Invoke via the Agent tool with subagent_type: "up-docs:up-docs-audit-drift" (the up-docs: prefix is required — plugin-defined agents are only addressable through their plugin namespace). The prompt:
- Session-change summary at the stable front
- Collection scope argument (if provided) at the end
- The reference docs
skills/drift/references/convergence-tracking.mdandskills/drift/references/server-inspection.mdare read by the sub-agent itself; do not duplicate their content into the prompt.
4. Pass Findings Through
The sub-agent returns both a JSON findings block (canonical artifact) and a markdown findings table (for human reading). Emit both in the skill's final output.
If the sub-agent includes an ⚠ ESCALATION RECOMMENDED block, include it verbatim.
5. Offer Next Step (bounded choice)
After findings land, use AskUserQuestion to offer:
- Re-invoke propagators with findings as a new session-change summary (fixes them at Haiku cost)
- Re-run the audit with Opus (if escalation was recommended)
- Accept findings as advisory and exit
Do not auto-invoke any of the above.
Notes
- This skill no longer runs SSH/pct/curl directly — the sub-agent does.
- Convergence + oscillation detection live in
scripts/convergence-tracker.sh. The default state-file path is${TMPDIR:-/tmp}/up-docs-tracker-${CLAUDE_CODE_SESSION_ID:-default}.jsonso that the 6+ separate invocations in one drift session share state. Override withUP_DOCS_TRACKER_STATEfor tests or for non-session usage. - Findings are advisory: the auditor has no write tools for Outline or Notion. Fixes go through the propagators on a follow-up pass with the user's explicit consent.
Related Skills
l3digitalnet/qdev-grounding
development
VerifiedTrustedCommunity
Use when you're stuck or missing current information mid-task - the same command/API/approach failed twice, an error looks like a changed or deprecated API, or you need the current version of something, a fact from after your training cutoff, or to verify something you cannot confirm from the code in context. Starts with a cheap inline lookup and only escalates to a full research sweep if that fails. Do not use for routine pre-emptive checks before ordinary library work - for deliberate research, use /qdev:research.
5SKILL.mdUpdated Jun 4, 2026
l3digitalnet/up-wiki
documentation
VerifiedTrustedCommunity
Update Outline wiki documentation with implementation-level details from the current session by dispatching the up-docs-propagate-wiki sub-agent. This skill should be used when the user runs /up-docs:wiki.
5SKILL.mdUpdated Apr 24, 2026
l3digitalnet/up-repo
documentation
VerifiedTrustedCommunity
Update repository documentation (README.md, docs/, CLAUDE.md) based on session changes by dispatching the up-docs-propagate-repo sub-agent. This skill should be used when the user runs /up-docs:repo.
5SKILL.mdUpdated Apr 24, 2026
l3digitalnet/up-notion
documentation
VerifiedTrustedCommunity
Update Notion pages with strategic and organizational context from the current session by dispatching the up-docs-propagate-notion sub-agent. This skill should be used when the user runs /up-docs:notion.
5SKILL.mdUpdated Apr 24, 2026