agent-skills

Portable, project-agnostic skills for Claude Code, OpenClaw and Hermes — small, reusable developer-workflow tools that work in any repo. This repo is both a Claude Code plugin (all skills under skills/) and a plugin marketplace (digitizer-skills) that also serves operational guides for the hosting, WordPress, ads, and billing tools we run — so every device installs from one place and stays up to date from git.

Each skill is a self-contained folder with a SKILL.md (the agent reads its frontmatter description to decide when to load it) and optional REFERENCE.md / EXAMPLES.md / scripts/.

Skills

Skill	What it does
canva-studio	Operate the Canva MCP for branded design work — create from brand templates with autofill, generate freeform designs, export with approval guardrails. For social posts, presentations, and marketing collateral.
codex-review-loop	Drive a PR to convergence through the Codex AI reviewer — build → PR → @codex review → verify each finding against HEAD → fix the real ones with regression tests → re-trigger until clean → human reviews last.
fable-mode	Strict judgment/planning/verification/inference discipline — verified-vs-inferred-vs-assumed labeling, rival hypotheses before diagnosis, premise checks, confirm-before-irreversible (a criterion is a filter, not an authorization), and proportionally short answers on trivia. Triggers on "fable-mode" / "מצב פייבל" and proactively on high-stakes tasks.
figma-studio	Route design work through the Figma MCP — client-site mockups, design-to-code, FigJam diagrams — loading Figma's official /figma-use skill before editing and keeping Digitizer conventions.
gha-optimizer	Audit and cut GitHub Actions minutes — measure real usage, hunt redundant work before optimizing (does the job need to run at all? at this frequency? only then cache/tune), detect double-builds vs. deploy platforms (Vercel/Netlify/Cloudways), output exact diffs grouped by delete/reduce-frequency/optimize. Read-only until explicitly approved.
handoff	Write a handoff document so a fresh agent can continue the work — project overview + tools, policies/schemas, suggested skills, ending with current state → open issues → next steps. In the chat's primary language, secrets redacted, no duplication of existing artifacts. Ships a context-guard.sh hook that auto-nudges the handoff at ~70% context usage.
magnific-studio	Generate and upscale AI imagery via the Freepik / Magnific REST API without an MCP server. Reads FREEPIK_API_KEY from ~/.claude/freepik.env, so it works in any session.
pr-first-workflow	Default to a branch + PR for every change (code and docs); branch → commit → PR → review → merge → return to the default branch; direct-to-main only on an explicit OK. Pairs with codex-review-loop.
safe-prod-db-write	Run one-off writes/backfills against a production DB safely — pull the connection into an mktemp file, dry-run, get explicit human authorization, execute, verify counts/invariants, clean up.

The marketplace also serves operational-guide plugins from outside this repo, one per tool we run:

Plugin	Source	What it does
cloudways-mcp	Digitizers/cloudways-mcp	Cloudways hosted-MCP operational guide.
hostinger-mcp	Digitizers/hostinger-mcp	Hostinger MCP operational guide.
aura-mcp	Digitizers/aura-mcp	Aura control-plane skill — approvals, snapshots, restores.
wordpress-api-pro	Digitizers/wordpress-api-pro	WordPress REST management — posts, media, Elementor, ACF, Woo, SEO.
siteagent-elementor-studio	Digitizers/siteagent-elementor-studio	Build WordPress sites via the Elementor MCP.
meta-ads-mcp	Digitizers/meta-ads-mcp	Meta Ads MCP operational guide.
sumit-mcp	Digitizers/sumit-mcp	SUMIT (OfficeGuy) billing MCP + skill.

Install — Claude Code (recommended)

One-time per machine, inside any Claude Code session. See ONBOARDING.md for the full first-time device setup (GitHub auth, install commands, optional env vars):

/plugin marketplace add Digitizers/agent-skills
/plugin install agent-skills@digitizer-skills
/plugin install cloudways-mcp@digitizer-skills
/plugin install hostinger-mcp@digitizer-skills
/plugin install aura-mcp@digitizer-skills
/plugin install wordpress-api-pro@digitizer-skills
/plugin install siteagent-elementor-studio@digitizer-skills
/plugin install meta-ads-mcp@digitizer-skills
/plugin install sumit-mcp@digitizer-skills

Then open /plugin, find the digitizer-skills marketplace, and enable auto-update (third-party marketplaces have it off by default). From then on Claude Code refreshes the marketplace in the background and pulls new commits — edit a skill here, and every machine picks it up. Manual refresh: /plugin marketplace update digitizer-skills.

The CLI and the IDE extensions (VS Code / JetBrains) share the same ~/.claude user scope, so one install covers both.

Claude Code on the web / mobile (claude.ai/code)

Cloud sessions never run plugin installs — a session loads the skills of the repos listed as sources of its cloud environment, cloned fresh from main on session start (this repo's skills load via .claude/skills/, committed relative symlinks into skills/, so the plugin layout stays the single source of truth). Do the one-time environment setup in ONBOARDING.md §6, which lists every toolbox repo to add as a source. The tool connections (Cloudways, Hostinger, Aura, SUMIT, Elementor) ride the same clones: each tool repo commits a placeholder-only .mcp.json, and the tokens are injected as env vars in the cloud environment's configuration — ONBOARDING §7 has the variable list.

A repo-level .claude/settings.json (this repo carries one) enables the toolbox plugins for desktop sessions opened inside that repo — handy in a work repo on a machine without the user-scope install. Note that this repo's own file intentionally omits agent-skills@digitizer-skills (its skills already load from the repo itself); when copying the file into another repo, add that entry too or you'll get the tools without the workflow skills. It has no effect on cloud sessions; environment sources are the only cloud mechanism.

Install — OpenClaw / plain symlinks (fallback)

git clone https://github.com/Digitizers/agent-skills.git ~/Documents/GitHub/agent-skills
cd ~/Documents/GitHub/agent-skills && ./install.sh ~/.agents/skills

install.sh symlinks every folder under skills/ into the target (default ~/.claude/skills/). It's idempotent and safe — it replaces a stale symlink and skips any real directory of the same name. Updates arrive via git pull.

Hermes consumes the same checkout without copies by adding this repository's skills/ directory to skills.external_dirs. See the shared portability contract for runtime adapters, validation and rollback boundaries.

Migrating from the old symlink install? The skill folders moved from the repo root into skills/, so symlinks created before that point at dead paths. After installing the plugin, remove the old links so skills don't load twice: find ~/.claude/skills -maxdepth 1 -type l ! -exec test -e {} \; -delete (deletes only broken symlinks), or re-run ./install.sh if you're staying on the symlink flow.

Adding a skill

Drop a new skills/skill-name/SKILL.md folder in, keep SKILL.md under ~100 lines, give the description a clear "Use when …" trigger, and add the cloud symlink so web/mobile sessions load it too:

ln -s ../../skills/skill-name .claude/skills/skill-name

Then commit both. tools/trigger-eval/validate_spec.py fails if the symlink is missing or points at the wrong skill, so a forgotten link can't slip through. Split detail into REFERENCE.md when it grows. Machines with the plugin installed pick it up on the next marketplace refresh — no re-install.

Before opening a PR, run the exact suites used by CI:

python3 -m pip install -r tools/trigger-eval/requirements.txt
python3 tools/trigger-eval/validate_spec.py
python3 tools/portability/validate.py \
  --repo . --visibility public --require-cloud-links
python3 tools/trigger-eval/test_tools.py
python3 -m unittest discover -s tools/portability -p 'test_*.py'
python3 tools/plugin-cache-gc/test_plugin_cache_gc.py

Do not substitute bare python3 -m unittest or discovery from tools/: this repository also has a standalone regression script and tool directories are not Python packages, so generic discovery can report 0 tests while skipping them.

License

MIT.