Showing 47851–47880 of 53870 skills
Use to publish an APPROVED, drafted content item via the CMS adapter (WordPress or git-static) - "publish the draft", /organic-os:publish. Refuses unapproved items.
shalintripathi/organic-os
Use when the user wants to remove a site from organic-os, deregister a site, uninstall, "reset organic-os", "remove my site", "start over", or runs /organic-os:reset. Guided teardown that shows what exists and, per user choice, deregisters the site from the local registry - it never deletes the brain repo or revokes credentials on the user's behalf.
shalintripathi/organic-os
Use when the user installs organic-os, says "set up organic-os", "onboard my site", "connect my website", "add another website", "switch site", "organic-os status", or runs /organic-os:setup or /organic-os:sites. Reads the enable-time install form first (anything filled there is never re-asked), audits the site URL and proposes a pre-filled profile before asking, scaffolds the per-site brain repo, runs the connector wizard with live verification, records credentials one at a time, registers routines for the chosen runtime, ends with a tested postflight scorecard, and manages the multi-site registry (add / update / switch / status).
shalintripathi/organic-os
Use when the user first opens organic-os, says "get started", "start organic-os", "what do I do first", "guide me through this", or runs /organic-os:start. The branded front door - health-checks the environment, then routes to first-run quick setup or, for a returning user, a compact status view and menu. Always ends by naming the three commands used most.
shalintripathi/organic-os
Consult on what a vendor technology has historically been caught up in, what to detect as a result, and what to do about it once found. Answers three questions from a corpus of 1,142 threat advisory records joined to MITRE ATT&CK and D3FEND. One, scoping -- "I run this technology, what should I worry about" -- which works even when the corpus has never heard of the product. Two, rule design -- "here are the patterns or techniques I am considering, what does the corpus say". Three, coverage -- "what should I build that I have not got", ranked by gap against what the caller already implements. Answers cover the management, control and data planes, not only the plane the ranking favours. Use whenever someone names a firewall, VPN, EDR, cloud platform, OT device or any product they run and asks what to worry about, what to detect, what use cases to build, or where coverage is thin.
gocortexio/skills
Author Cortex XSIAM Data Model Rules in Cortex Query Language (XQL). Turns a raw vendor log sample into a production-ready rule with a MAPPED-header comment block.
gocortexio/skills
Build PPT / PowerPoint / 演示文稿 / slide decks end-to-end via a .pptwork/<deck>/ filesystem contract. Use when the user wants to plan, author, screenshot, or export a slide deck. Provides Node scripts for deck CRUD, headless screenshot, and editable PPTX export. Covers clarification, story planning, single-page authoring (via the ppt-html-authoring skill), visual QC, and export troubleshooting.
JunfengRan/PPTWork
Author a single PPT slide as a self-contained slide.html + design.md, given one outline entry. Use when the user asks to design, draft, or rewrite an individual slide page (KPI page, agenda, cover, two-column comparison, chart slide, etc.). Single-page only; does not plan across pages, does not screenshot, does not export. Works alongside the `ppt` skill or standalone.
JunfengRan/PPTWork
Use when orchestrating multiple coding agent CLIs (Claude Code, Codex, OpenCode, Grok CLI, Antigravity). Discovery, comparison, structured prompting, and multi-agent handoff patterns. Portable free pack — no host-specific secrets.
frankxai/awesome-hermes-agent-skills
Use when a Hermes session is about to edit a linter config or a TypeScript file. Warns on console.log and blocks weakening an existing formatter config. Does not install the ECC marketplace.
frankxai/awesome-hermes-agent-skills
Use when starting any complex task (3+ steps) or before declaring work complete. Enforces todo/task state to match reality — merge updates + read verification. Prevents false completion.
frankxai/awesome-hermes-agent-skills
Work with Master Canvas AI video handoff packages. Use when a user provides a Master Canvas ZIP or project_manifest.json and wants Hermes to inspect assets, preserve scene and shot order, prepare ComfyUI/LTX 2.3 jobs, or hand off prompts to Kling, Veo, or another video generation operator. Also use when a user wants Hermes to autonomously create, update, and package a Master Canvas pre-production project from a brief, scenes, shots, prompts, references, and local assets.
wassermanproductions/master-canvas-hermes-plugin
Answer questions about a project's analytics with figures from the analytics datamarts. Use when asked for a figure, why a figure changed, how campaigns or flows performed, or for a summary of a period. Russian triggers: "сколько выручки", "почему упала выручка", "итоги рассылки", "как сработал сценарий", "сводка за месяц". English triggers: "how much revenue", "why did revenue drop", "how did the campaign perform", "summary for last month". Don't use when: the request is to build or change a flow, a mailing or a filter — those have their own skills; the user needs a list of customers rather than a figure.
mindbox-cloud/agent-skills
Creates and edits emails for the Mindbox email editor from a text description. Use when the user asks to create or change an email, describes an email template, or says 'сделай рассылку' / 'make a campaign'. The technical layout is handed over for preview and saving through the companion skill email-ops.
mindbox-cloud/agent-skills
Operational actions for Mindbox emails — preview, reading and saving the visual template, saved templates (an email by one, changing, creating, copying), reading/editing campaign metadata and recipients (a segment or a filter), finding gallery assets via MCP, uploading images from the user's machine through the MCP App panel, PNG preview. Use together with the email skill when images, a preview, a check or a write to Mindbox are needed.
mindbox-cloud/agent-skills
Build or edit a CDP filter from a natural-language request. Use for audience or object selections and changes to existing filter JSON. Russian triggers: "собери фильтр", "построй фильтр", "сделай выборку", "нужен сегмент", "выбери клиентов, которые...", "фильтр по товарам", "добавь условие в фильтр". English triggers: "build a filter", "make a segment", "select customers who...", "filter products", "edit this filter", "add a filter condition". Returns a platform-confirmed filter and a link when available; does not save a segment. Don't use when: the filter only needs explaining and not changing — that is filter-explain; the question is how many or how much, which is a counting task, not a filter.
mindbox-cloud/agent-skills
Explain existing CDP filter JSON in plain language, including conditions and values that could not be read. Use when asked what a filter or segment selects. Does not change it. Russian triggers: "объясни фильтр", "что делает этот фильтр", "кого выбирает эта выборка", "разбери фильтр", "объясни условия сегмента". English triggers: "explain this filter", "what does this segment select", "who matches this filter", "explain these filter conditions". Don't use when: the filter has to be built or changed — that is filter-build; the question is how many or how much, which is a counting task, not an explanation.
mindbox-cloud/agent-skills
Build a correct draft marketing scenario (flow) from a plain-language request: read the flows reference, resolve the entities the design needs to real ids, create and fill the blocks, wire the outputs, verify every block by reading it back, and hand over a link. Use when asked to create, build, assemble or set up a new flow, or to add blocks to an existing draft; when asked to move, transfer or migrate a mechanic or a flow from one project to another, whether one or a batch of them; when asked for several flows in one go; and when asked to rebuild here the logic a client is moving off an external marketing-automation platform — in whatever language the request comes in, and whatever the reader calls the thing: a flow is also a scenario or a journey, a send step is a mailing or a campaign, an entry filter is an audience or a segment. Don't use when: the flow already exists and only needs describing or checking — this skill builds, it does not report; the request is to launch, stop or delete something, which stays a human decision.
mindbox-cloud/agent-skills
Explain in plain language why a Mindbox promotion did not apply to an order, why its benefit came out zero or why the discount is smaller than expected: one reason and who to go to. Use when a cashier, a salesperson, a store manager or first-line support asks why a promotion did not work, or sends the explanation link from the admin panel (https://<project>.mindbox.ru/processing-orders/debugger?calculationId=...&promotionId=...) or a promotion link (https://<project>.mindbox.ru/promotions/<number>) together with an order number. Russian triggers: "почему не применилась акция", "не сработала скидка", "клиент жалуется на акцию", "промокод не сработал", "почему не списались баллы", "whypromo". English triggers: "why didn't the promotion apply", "the discount didn't work", "promo code didn't work", "why were no points redeemed". Don't use when: a technical breakdown with codes and stages is needed — ask for it separately; promotion settings, the promotion tree or the change history are asked for — the explanation does not contain them.
mindbox-cloud/agent-skills
Quick and accessible AI reviewer for Agent Skills — for non-specialists. Checks structure, workflow, references, and links. Produces a clear report without technical jargon. Summary from Exhausted Vitaly. Use when user says "quick review", "basic skill check", "review my skill", "review for product owner", "light review", "quick check", "check my skill", "evaluate skill quality", "what's wrong with my skill", "review this skill". Don't use when: user asks for a deep/nightmare review (use skill-review-nightmare), user asks to create a new skill, to review code, user asks to review a prompt that is not a skill.
mindbox-cloud/agent-skills
Use when auditing, pruning, or cleaning up an agent's entire existing rule set in one bulk pass across every rule source at once (all CLAUDE.md files, all memory entries, AGENTS.md, ADRs, COORDINATION). This is whole-corpus hygiene; NOT for adding, editing, or fixing an individual rule (just edit that file directly).
bwdurst/rule-curator
Use when creating or reviewing a shipd.ai Olympus quest submission — picking a candidate GitHub repo, designing a challenge task hard enough for the ≤50% pass-rate bar, writing the test patch, solution patch, test.sh, or Dockerfile, or when a platform check fails (naming collisions, Dockerfile warnings, description request_changes, test fairness).
mashhoorahdal/shipd-olympus-skill
Naturaliza texto en español generado por IA aplicando 11 técnicas lingüísticas y detectando marcas técnicas/tipográficas (caracteres invisibles, watermarking, tipografía atípica) para mejorar la calidad editorial y naturalidad comunicativa. Produce el texto reescrito y un informe con diagnóstico cuantitativo.
dorelysm/naturalizacion-texto-es
Distill an already-built or near-launch product into one incisive brand kernel — the "reveal" already hiding in its name, story, or the product itself — then build the name, voice, visual identity, and a developer-ready handoff kit around it. This is LATE-STAGE branding: use it when there is a real, thought-through product that is about to launch, or already live but not explained in a way people grasp in an instant. Use whenever the user wants to name or rename a product, find a tagline or slogan, create a brand identity / brand kit / style guide / design system, design a logo, wordmark, palette, or type system, mock up a homepage for a launch, or hand brand assets to a coding agent (Claude Code, Codex, Cursor). Trigger even when the user only says their product needs to "land" or "feel like" something, or that they can't explain it simply yet. Do NOT use for half-baked, pre-product ideas with nothing to excavate — this skill extracts a kernel that already exists; it does not invent one from a blank canvas.
DTM-repo/skills
Write, review, discover, lint, format, and validate BIRD 2/3 routing-daemon projects with the @birdcc toolchain. Use for bird.conf, bird2.conf, bird3.conf, bird6.conf, .bird/.bird2/.bird3 files, bird.config.json, birdcc.config.json, include graphs, BIRD filters and protocols, birdcc init/lint/fmt/lsp, or bird -p checks. Treat BIRD 1 as legacy and verify it with the actual BIRD 1 binary. Route editor and CLI installation to birdcc-installer, GitHub Actions to birdcc-cicd, runtime incidents to bird-troubleshooting, and implementation archaeology to bird-source-explorer.
bird-chinese-community/BIRD.skills
Trace BIRD routing-daemon behavior through the actual C source tree. Use for implementation questions, suspected upstream bugs, parser/keyword origins, filter instructions, protocol state machines, route attributes, birdc commands, stack traces, or BIRD 2 versus BIRD 3 source comparisons. Prefer a local checkout or exact upstream tag/commit and cite concrete files, functions, and revisions. Route config linting to bird-agent and active incidents to bird-troubleshooting.
bird-chinese-community/BIRD.skills
Diagnose active BIRD daemon incidents across config, runtime, environment, sockets, logs, source, and tooling. Use when BIRD fails to start or reload, crashes, loses sessions/routes, behaves differently after lint passes, or when birdcc and bird -p disagree. Collect read-only evidence first, protect routing secrets, and route isolated config edits to bird-agent or pure implementation research to bird-source-explorer.
bird-chinese-community/BIRD.skills
Build or review GitHub Actions workflows for BIRD 2/3 projects using bird-chinese-community/setup-birdcc and @birdcc/cli. Use for pull-request lint/format/parse checks, BIRD2/BIRD3 matrices, BIRD_BIN, changed config files, pnpm/Turbo caching, submodule configs, action pinning, or .github/workflows changes. Route local config work to bird-agent and local editor/CLI installation to birdcc-installer.
bird-chinese-community/BIRD.skills
Install or migrate BIRD 2/3 editor support and @birdcc/cli. Use for the BIRD2 LSP VS Code extension, the separate TextMate syntax extension or extension pack, VS Code forks, BIRD.nvim, BIRD.vim, manual Neovim LSP wiring, JetBrains TextMate bundles, birdcc CLI installation, offline VSIX setup, or migrations from BIRD2.nvim/BIRD2.vim. Route config diagnostics to bird-agent and GitHub Actions to birdcc-cicd.
bird-chinese-community/BIRD.skills
<One-line description of when to use this skill. Keep it under 160 characters.>
bird-chinese-community/BIRD.skills