digitizers

@digitizers source repo

17 skills
0 followers
5 hours ago last updated

▌
Cloudways MCP · digitizers bundle
Operational guide for managing Cloudways servers and applications, across one or several Cloudways accounts, via the official Cloudways MCP server (Cloudways' hosted MCP / Remote MCP, per their support docs). Use whenever the user mentions Cloudways, a Cloudways server or app, server monitoring, app monitoring, bandwidth, disk usage, PHP/MySQL/traffic analytics, Varnish cache, app cloning, backups/restore on Cloudways, Git deployments on Cloudways, SSL/Let's Encrypt on Cloudways, malware scans / Security Suite, staging sync, team members, AgencyOS client billing, or running an audit/onboarding on a Cloudways-hosted client site. Any write operation (start/stop/restart server, backup, restore, update CNAME, purge cache, change service state, git pull, SSL install/revoke, IP whitelist update, staging sync, team/billing changes, delete server/app) requires explicit confirmation of target server/app and intended action before execution.

0
installs
▌
Deepclaw Openclaw · digitizers bundle
OpenClaw observability plugin for DeepClaw — streams real-time LLM usage, token, cache, reasoning, and cost telemetry into DeepClaw.

0
installs
▌
Hostinger MCP · digitizers bundle
Operational guide for managing Hostinger infrastructure — VPS, websites/hosting, domains, DNS, email marketing (Reach), and billing — via the official Hostinger MCP server (npm hostinger-api-mcp), across one or several Hostinger accounts. Use whenever the user mentions Hostinger, hPanel, a Hostinger VPS, a Hostinger-hosted site, Hostinger domains/DNS, domain purchase/transfer/lock, Hostinger email/Reach contacts, or Hostinger billing/subscriptions. Any write operation (create/update/delete/recreate a VPS, change firewall/DNS, purchase a domain or VPS, change a subscription or payment method, deploy/import a site) requires explicit confirmation of the target resource and intended action — and the cost, for money-spending operations — before execution.

0
installs
▌
Meta Ads MCP · digitizers bundle
Production-grade operational guide for creating, managing, optimizing, and documenting Meta (Facebook/Instagram) ad campaigns via the Facebook Ads MCP. Use whenever the user mentions Facebook ads, Instagram ads, Meta campaign planning, ad budgets/spend, ad audiences (incl. Custom Audiences), retargeting, ad performance, Pixel/CAPI tracking, creative briefs, naming conventions, campaign documentation, or safe MCP-based campaign operations.

0
installs
▌
Siteagent Elementor Studio · digitizers bundle
Helps with WordPress + Elementor work via the elementor-mcp MCP server — building new pages, editing existing ones, inspecting site state, or exploring what's possible. Auto-detects Elementor Pro (native Form, Theme Builder, Loop Grid, Popups, Dynamic Tags, Sticky/Motion vs free-tier workarounds) AND the page engine (classic vs Elementor 4 atomic/V4 — atomic uses add-flexbox/add-atomic-* tools since classic writes don't persist on a V4 page). Detects ACF + Crocoblock/JetEngine for dynamic-data binding (Tier-0; bind ACF via Pro dynamic tags, place Jet widgets via add-widget with runtime-verified types). On atomic (V4) sites, authors the Elementor 4 design system — Global Classes, Variables (design tokens), and per-element Interactions — and recovers from the fork's schema-in-error and governance responses. Asks what the user wants before acting. Use when the user references the Elementor MCP, invokes `/siteagent-elementor-studio`, or runs `mcp__elementor__elementor-mcp-*` tools. Also covers initial install of

0
installs
▌
Sumit MCP · digitizers bundle
Operate SUMIT (formerly OfficeGuy) Israeli billing from an agent — read invoices, debt, and catalog items; issue invoices/receipts/quotes (חשבונית/קבלה/חשבון עסקה); and charge with a layered, confirm-first safety model. Use when the task mentions SUMIT, OfficeGuy, חשבונית, קבלה, invoicing, billing, retainers, or Israeli accounting documents.

0
installs
▌
Wordpress API Pro · digitizers bundle
Production-grade WordPress REST API integration for managing posts, pages, media, WooCommerce products, Elementor content, SEO meta, ACF, and JetEngine fields. Use when you need to retrieve, draft, create, or update WordPress content programmatically on sites where the user has provided explicit credentials. For any operation that writes to a live site, get explicit user approval for the target site, post/product IDs, and final action before executing. Prefer drafts first. Run batch operations in dry-run mode first; use --execute only after review. Remote URL media downloads and local file reads are restricted by safety boundaries. Also includes a no-auth Tier-1 site audit (PageSpeed, SSL, security headers, CMS/PHP fingerprint, SEO basics) for cold pre-sale checks, and authenticated plugin/SEO-stack discovery.

0
installs
▌
Magnific Studio · digitizers bundle
Magnific Studio — generate AI images and upscale via the Freepik / Magnific REST API. Use when the user wants to generate an AI image, hero visual, banner background, illustration, or texture from a text prompt, or to upscale/enhance an existing image. Triggers on "Magnific", "Freepik", "generate an image", "AI background", "AI hero visual", "text-to-image", "upscale this image". Not for branded social posts or presentations (canva-studio) and not for UI mockups (figma-studio). Reads the API key from ~/.claude/freepik.env (FREEPIK_API_KEY) so it works across all sessions.

0
installs
▌
Codex Review Loop · digitizers bundle
Drive a pull request to convergence through the Codex AI reviewer — build → local Round 0 pre-review → PR → @codex review → verify each finding against HEAD → fix the real in-scope ones with regression tests → re-trigger until Codex is clean, or until every blocking finding left is triaged into a terminal state → human reviews last. Use when a PR is open or just pushed and should be reviewed, when a branch is built and tested and a PR is about to be opened (Round 0 local pre-review), when the user mentions "codex", "@codex review", "the review loop", "ultrareview", or asks to iterate a PR to green.

0
installs
▌
Pr First Workflow · digitizers bundle
Default to a branch + pull request for every change — code, docs, config, content, and marketing copy alike — instead of committing to main. Branch → commit → local pre-review (Round 0) → push → PR → review → merge → return to main; direct-to-main only when the human explicitly says so. Use when starting any change in a git + GitHub repo, when deciding whether something can skip a PR, when the user mentions branching / PR workflow, and whenever a request implies landing a change — "commit it", "ship it", "push it", "get it into main", "publish it", "update the copy / the page / the README" — however small the edit sounds. Pairs with codex-review-loop, which pre-reviews the built branch (Round 0) and drives the opened PR to green.

0
installs
▌
Safe Prod DB Write · digitizers bundle
Safely run a one-off write, backfill, or data-mutating script against a PRODUCTION database — pull the connection, dry-run, get explicit human authorization, execute, verify, clean up. Use before any script that inserts/updates/deletes prod data (codes, backfills, one-off fixes, seed data), when the user asks to mutate production data, or when a task needs a real prod DB connection. Also use when adding a DB model/table/migration; when a hosted tool or dashboard applies a migration (Supabase `apply_migration`, Neon, PlanetScale) — see "Migrations applied by a hosted tool"; when a permission layer blocks a write you were authorized to make — see "When the harness refuses the write"; when the project keeps a dev twin of production (a Neon/Supabase branch, staging cluster), since naming the target host is step 0; or when adding a CI guard for a per-table invariant (RLS, tenant column, index). Assumes a Neon/Vercel-style setup, but the protocol generalizes.

0
installs
▌
UI Component Router · digitizers bundle
Router for sourcing UI components — picks ONE source among the shadcn/ui registry (MCP or CLI), 21st.dev magic-mcp, and Ant Design, so a component need lands on one system instead of a hand-rolled lookalike or a mixed component zoo. Read this FIRST whenever a task needs a UI component or section — a button, dialog, data table, form, pricing section, hero, navbar, dashboard widget — or when the user asks to "add a component", "build a section", "use shadcn", "find a component for", "תוסיף קומפוננטה", "תבנה סקשן", "צריך טבלה/טופס/דיאלוג", "חפש קומפוננטה". Not for designing a brand or page from scratch (that is design work, not component sourcing), not for choosing the project's framework, and not for installing/configuring the tools themselves.

0
installs
▌
Handoff · digitizers bundle
Use when the current session's work must continue in a fresh agent session — the context window is nearly full or about to be compacted, the user is ending a work session and will resume later, the work is being handed to another agent, machine, or teammate, or the user asks for a "handoff", "handoff document", "session summary to continue from", or to "prepare this for the next session". Also fires when a hook or system reminder reports high context usage and asks for a handoff. Not for writing project documentation for humans (README, docs, changelogs, reports) — only for transferring this session's state to a future agent session.

0
installs
▌
Fable Mode · digitizers bundle
Use this skill IMMEDIATELY whenever the message contains "fable-mode", "fable mode", "פייבל", or "מצב פייבל" — including as a prefix before a task (e.g. "fable-mode: review this...") — no matter what the task itself is. Also use it proactively, unprompted, in two situations: (1) the user wants a fact double-checked or verified against a live source instead of answered from memory — "double-check", "can you verify", "is this still true", "I don't trust my memory", current versions/limits/pricing/capabilities of tools, APIs, or services; (2) the task is costly if wrong — production changes, migrations, deletions, security, money, architecture commitments, debugging, or research synthesis. Enforces strict planning, verification, and calibrated claims; stays active for the rest of the conversation until "fable-mode off" / "כבה מצב פייבל". Do NOT use for casual questions, trivial edits, creative writing, or when "fable" appears only as an ordinary word (writing a fable, defining it).

0
installs
▌
Canva Studio · digitizers bundle
Operate the Canva MCP for branded design work — social posts, presentations, marketing collateral, one-pagers. Use when the user wants to create or edit a Canva design, fill a brand template, resize for another format, or export a design ("Canva", "פוסט לרשתות", "מצגת", "brand template", "עצב לי", "make a deck in Canva"). Not for AI image generation or upscaling (magnific-studio), not for UI/product mockups or design-to-code (figma-studio), and not for building slide files locally (the pptx skill).

0
installs
▌
Figma Studio · digitizers bundle
Route design work through the Figma MCP — client-site mockups, UI screens, design-to-code, code-to-design, FigJam diagrams. Use when the user wants to mock up a page or screen, implement a Figma design as code, push a page into Figma, diagram a flow, or shares a figma.com URL ("Figma", "FigJam", "mockup", "מוקאפ", "design-to-code"). Not for branded social posts or presentations (canva-studio) and not for AI image generation or upscaling (magnific-studio).

0
installs
▌
Gha Optimizer · digitizers bundle
Audit and cut GitHub Actions minutes consumption in a repo — measure real usage first, hunt REDUNDANT work before optimizing existing work (does this job need to run at all? at this frequency? only then tune it), detect double-builds against deploy platforms (Vercel/Netlify/Cloudflare Pages/Cloudways), then propose exact diffs grouped by delete/reduce-frequency/optimize. Use whenever the user's intent is to SPEND LESS on CI — reduce GitHub Actions minutes, audit CI cost or billing, ask why Actions usage is high, ask what CI work can be cut or is redundant, request a CI-efficiency review of `.github/workflows/`, or mention "gha-optimizer". Read-only by default — never edits workflows without explicit approval. The dividing line is intent, not subject matter: this skill answers "what is our CI costing us, and what can we delete?" It is the wrong skill for "make this CI work" — writing a new workflow, or fixing a red/failing/misconfigured job — where the user wants MORE working CI, not less CI.

0
installs

17 published skills