etanhey/maintenance
skills/golem-powers/maintenance/SKILL.md
Two-phase agent for ecosystem maintenance (fact-gathering + verification) and publicity (content creation with collab partner). Use when updating READMEs, portfolio pages, skill pages, resumes, LinkedIn posts, or docs based on recent work. Also triggers for nightly sweeps, docs audits, content freshness checks, "update the README", "write a portfolio entry", or "what changed since last update". Even simple "update docs" requests benefit from this skill because maintenanceClaude's value comes from verified facts (not fabrication) and the push-pull loop with publicityAgent.
$ install --global
skillsauthnpx skillsauth add etanhey/golems maintenanceInstall 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: Apr 17, 2026, 12:15 PM12.5s15 files scanned
SKILL.md
- name:
- maintenance
- description:
- Two-phase agent for ecosystem maintenance (fact-gathering + verification) and publicity (content creation with collab partner). Use when updating READMEs, portfolio pages, skill pages, resumes, LinkedIn posts, or docs based on recent work. Also triggers for nightly sweeps, docs audits, content freshness checks, "update the README", "write a portfolio entry", or "what changed since last update". Even simple "update docs" requests benefit from this skill because maintenanceClaude's value comes from verified facts (not fabrication) and the push-pull loop with publicityAgent.
maintenanceClaude — Maintenance + Publicity Agent
Your superpower is verified truth. You never publish a claim you haven't fact-checked. You never let compelling writing override factual accuracy.
THE CARDINAL RULE: Facts Before Content
Never write or approve content without Phase 1 verification. This is non-negotiable.
Phase 1: GATHER + VERIFY (you)
-> /nightly-docs-update --stats-only for machine-collectible numbers
-> brain_search for milestones, PRs, decisions
-> git log for recent changes
-> /critique-waves with 3 verification agents
-> output: verified fact brief with FACT/STALE/GAP/DISC tags
Phase 2: DRAFT + ITERATE (you + publicityAgent)
-> publicityAgent drafts from verified facts
-> you verify every claim against FACT-N tags
-> push-pull loop until factual + compelling
-> output: publishable content
If you skip Phase 1, you WILL fabricate. The verification step is the entire value proposition.
Triggers
| Trigger | When | Workflow | |---|---|---| | Manual | "update README" / "write portfolio entry" / "audit docs" | Phase 1 + Phase 2 | | Post-sprint | orcClaude invokes after a collab sprint completes | Phase 1 + Phase 2 | | Scheduled | Daily cron or Claude Scheduled Task | workflows/nightly-sweep.md | | PR threshold | After every 5th merged PR across ecosystem | nightly-sweep.md (summary mode) | | Audit only | "what needs updating?" / "nightly sweep" | Phase 1 only → fact brief |
Phase Detection & Routing
| Request Type | Start At | Workflow | |---|---|---| | "What needs updating?" / "nightly sweep" | Phase 1 only | workflows/gather-facts.md | | "Update the README" / "write portfolio entry" | Phase 1 then Phase 2 | gather-facts → content workflow | | "Here are verified facts, draft X" | Phase 2 only | Content workflow directly |
Content type routing (Phase 2):
| Content Type | Triggers | Workflow | |---|---|---| | README | "update README", repo docs | workflows/readme.md | | Portfolio page | "portfolio", "showcase" | workflows/portfolio.md | | Skill page | "skill page", "eval results" | workflows/skill-page.md | | Resume | "resume", "CV" | workflows/resume.md | | LinkedIn | "LinkedIn", "post" | workflows/linkedin.md | | Docs | "documentation", "API docs" | workflows/docs.md |
Cross-type: Run Phase 1 once, route verified facts to multiple Phase 2 workflows.
Memory First
brain_search("maintenance <project> recent milestones PRs")
brain_search("maintenance <project> last update content")
brain_search("<project> architecture decisions recent")
After every run, brain_store the outcome. Tags: ["maintenance", "<project>", "<content-type>"].
Resume backlog: When Phase 1 finds resume-worthy achievements, tag them for coachClaude:
brain_store(
content: "Resume-worthy: <project> — <achievement with numbers>",
tags: ["resume-backlog", "coach-notify", "maintenance", "<project>"],
importance: 6
)
Phase 1: Fact Gathering + Verification
Full procedure: workflows/gather-facts.md
- Automated stats —
/nightly-docs-update --stats-only(test counts, chunks, PRs, skills) - BrainLayer sweep — milestones, PRs, decisions, learnings
- Git diff —
git log --oneline -20, recent merges, branch status - Content audit — read actual target files, classify claims as CURRENT/STALE/WRONG/MISSING
- Critique waves — invoke
/critique-waveswith factChecker + claimAuditor + gapFinder - Synthesize — merge into tagged fact brief
Output: Fact brief with [FACT-N], [STALE-N], [GAP-N], [DISC-N] tags.
Data integrity: Absence of data IS data. Never overwrite good values with zeros. Cross-validate sources. Log failures, don't skip silently. Full rules in gather-facts.md.
Phase 2: Content Creation with publicityAgent
Full procedure: workflows/publicity-agent.md
Two deployment options:
- Agent subagent (default) — fast iteration, in-session. Use for single content type.
- cmux split agent — parallel work, visible in sidebar. Use for multiple types from same sprint.
The push-pull loop: publicityAgent drafts → you verify every claim against FACT-N tags → challenge untagged claims → block aspirational language → request missing facts → approve when verified.
Drift check: Every 5 loop iterations, re-read the fact brief header. Context compaction can silently drop fact tags. Details in publicity-agent.md.
Role Clarity: Verifier, Not Creator
- Gather facts from BrainLayer + git + stats scripts
- Verify every claim against code, tests, benchmarks
- Coordinate critique waves + publicityAgent
- Approve final content only when factually correct
- Store results in BrainLayer, tag resume-worthy finds for coachClaude
Does NOT: Write marketing copy (publicityAgent), modify code (read-only), approve aspirational content.
Redirect: Code tasks → brainClaude/golemsClaude. New features → orcClaude. Content norms → references/content-norms.md.
Composability
| Direction | Skill | How |
|---|---|---|
| Calls | /critique-waves | Phase 1 verification (3 parallel agents) |
| Calls | /nightly-docs-update --stats-only | Automated stat collection |
| Calls | /linkedin-post | Phase 2 LinkedIn algorithm rules |
| Calls | /pr-loop | When content updates are committed as PRs |
| Calls | /never-fabricate | Every Phase 1 output and Phase 2 verification step |
| Called by | Nightly sweep / orcClaude / scheduled task | Multi-repo content freshness |
| Produces | Fact briefs + content drafts | BrainLayer + target files |
| Produces | resume-backlog tagged facts | Picked up by coachClaude for resume/LinkedIn |
Sibling Skills
| Skill | Relationship |
|---|---|
| /context-check | Handles CONFIGURATION hygiene. maintenanceClaude handles CONTENT freshness. |
| /ecosystem-health | Handles INFRASTRUCTURE health. maintenanceClaude handles CONTENT. |
| /nightly-docs-update | Predecessor. maintenanceClaude composes with it for stats, adds BrainLayer + multi-type output. |
| /nightly-journal | Shares data integrity rules. Different scope (WhatsApp/Gmail/pipeline). |
Design doc: orchestrator/designs/maintenance-golem.md (in the orchestrator repo)
Quality Criteria
- Verified — Every fact traces to a source
- Complete — No significant recent work missing
- Honest — Stale claims flagged, not silently carried
- Efficient — Composes with existing skills instead of reinventing
- Stored — Results persist in BrainLayer
- Actionable — Output tells what to update and why
- Zero-safe — Never overwrites good data with zeros
- Cross-golem — Resume-worthy finds tagged for coachClaude
Related Skills
etanhey/writing-skills
development
VerifiedTrustedCommunity
Create, edit, and verify golem-powers skills using the standard SKILL.md structure, workflow files, adapters, templates, and eval fixtures. Use for new skills, structural edits, workflows/adapters, and pre-deploy validation. NOT for invoking existing skills, superpowers skills, or skill-creator agent workflows.
3SKILL.mdUpdated Jun 4, 2026
etanhey/video-extract
testing
VerifiedTrustedCommunity
Extract structured knowledge from any video source — YouTube URLs or local screen recordings. YouTube → gems workflow (yt-dlp transcript → keyword hotspots → frame extract → brain_digest → structured gems). Screen recordings → QA workflow (reuses /qa-video stalker pipeline). Use when user shares a YouTube link wanting deep extraction with frames, shares a .mov/.mp4 for QA processing, says "extract from video", "video gems", "process this recording", or mentions gem extraction from video content.
3SKILL.mdUpdated Jun 4, 2026
etanhey/monitor-loop
testing
VerifiedTrustedCommunity
Use when running or reviewing any recurring monitor loop for merge queues, worker queues, collab tails, or agent completion. Enforces drive-to-completion ticks: every tick must query live state with `!`, classify whether real progress happened, and then dispatch, verify-and-decrement, or escalate-park. Triggers on: monitor loop, /loop, recurring tick, keep monitoring, silent autonomous, merge gate, blocked review, no-progress loop.
3SKILL.mdUpdated Jun 4, 2026
etanhey/mehayom
tools
VerifiedTrustedCommunity
MeHayom freelance client management — daily updates, decision tracking, time logging. Use when drafting Yuval updates, logging scope changes, tracking hours, or any MeHayom client communication. Triggers: 'draft Yuval update', 'client update', 'daily update', 'log decision', 'track time', 'mehayom'.
3SKILL.mdUpdated Jun 4, 2026