Open-source Skills for OpenClaw Agents

opensource-skill-to-github

@songhonglei

Quickly open-source a local skill to GitHub (primary) and optionally clawhub.com. Workflow: slug pre-check, fork to opensourceskills, strip internal info, normalize SKILL.md, generate LICENSE/README, init git, push to GitHub with configurable token source, and optionally publish to clawhub. Use when the user says "open-source this skill", "把这个 skill 开源", "发到 github", "publish skill publicly", or "把本地 skill 发开源". Hard rules: never modify the original skill in place, never auto-add force/yes flags, never write tokens to git/remote/memory, and ask the user at decision points.

standard-readme

@tenequm

Writes or audits README files following the Standard Readme specification (github.com/RichardLitt/standard-readme). Use whenever the user asks to create, write, rewrite, improve, audit, or fix a README, or asks about README quality or structure - even if they never mention "standard readme" explicitly.

Grok Geo

@xuboboo

Diagnose a brand's visibility, recommendations, citations, competitor presence, factual accuracy, and content gaps in AI-assisted web search. Use for GEO aud...

better-readme

@thomaszhou22

Use when the user asks to create, improve, fix, or audit a README.md file, score their README, document an open source project, or set up new project docs. Provides 8-dimension 0-100 quality scoring, 5-type template matrix (Library, CLI, App, Skill, Data), and pre-publish checklist. Do NOT use for API docs, wikis, inline code comments, or general technical writing.

Questlog

@antreasantoniou

Maintain an explicit Markdown commitments ledger with a local cockpit for NOW, next actions, deadlines, waiting items, workstream states and inbox capture.

propagate

@antreasantoniou

Propose a canonical home, concrete consumers, and any justified runtime home for a reusable tool, library, skill, document, or workflow. Use after building a reusable capability or when asked where it should live; execution requires approval of exact targets and actions.

Back to the Chronicle

@antreasantoniou

Reconstruct missing project history safely

doppel-gang

@antreasantoniou

Review author-written applications, essays, bios, proposals, and important correspondence through explicitly synthetic, contrasting review lenses while preserving the author's voice and final editorial authority. Use for substantive critique and author-led revision, not impersonation or automatic submission.

Threadseer

@antreasantoniou

Turn conversations into grounded decisions

Butler

@antreasantoniou

Track per-project Claude usage estimates and local GPU budgets, preview admission, atomically reserve capacity, and reconcile actual usage with a local dashboard.

ML Run Provenance

@antreasantoniou

Design or audit self-describing ML run metadata attached at initialization, including intent, code and data identity, resume lineage, and evidence limits. Use when wiring a tracker, introducing a run naming pattern, or investigating why a run exists.

ML Research Skeptical Audit

@antreasantoniou

Challenge ML claims with code and falsification

Cross-Agent Sync

@antreasantoniou

Sync Claude and Codex project progress

Beautiful PDF

@antreasantoniou

Design and visually review print-ready PDFs

Bitwarden Lease

@antreasantoniou

One secure Bitwarden unlock per 24 hours

Grade-A Pipeline

@antreasantoniou

Run a test-sandwiched multi-agent build pipeline

agent-orchestra

@antreasantoniou

Design and compose multi-agent graphs for correctness, coverage, or creativity. Use when a task benefits from isolated proposals, explicit arbitration, adversarial verification, committees, recursive review, cross-modal checks, or saturation loops. Applies across agent runtimes; the included JavaScript workflow is one adapter.

GCP Keyless

@antreasantoniou

Use GCP without recurring browser OAuth

Argus

@antreasantoniou

Preserve durable context across every Archivum

Archivum

@antreasantoniou

Durable memory for projects and research

Agent Collaboration Control

@antreasantoniou

Govern and actively monitor collaborative agent work

Local UIs

@antreasantoniou

Find and open locally running web interfaces

Mailbutler

@antreasantoniou

Narrative-aware, approval-gated inbox triage

Heimdall

@antreasantoniou

Evidence-backed browser and API test plans

plus-ultra

@antreasantoniou

Run a Byzantine 2+1 plan before consequential work and a fresh, plan-blind reality check afterward. Use when the user asks for Plus Ultra, maximum rigor, independent proposals, enforced verification, or help responding to a Plus Ultra hook gate. Claude Code can enforce the loop through the included hook adapter; on Codex and other hosts it is a convention unless separately wired and verified.

Doppel

@antreasantoniou

Build your digital-twin writing voice

Visual QA

@antreasantoniou

Run an evidence-driven UI review committee

Nexus

@antreasantoniou

Map repositories into focused context packs

Chronicle

@antreasantoniou

Operational history, evidence, and intent

Context7

@wei840222

Retrieve current, source-backed documentation for libraries, frameworks, SDKs, APIs, developer tools, open-source projects, and GitHub projects. Use for vers...

A OpenClaw SKILL.md - Use when the user mentions Jira issues (e.g., "PROJ-123"), asks about tickets, wants to create/view/update issues, check sprint status, or manage their Jira workflow. Triggers on keywords like "jira", "issue", "ticket", "sprint", "backlog", or issue key patterns.