all publishers

agents-store

@agents-store source repo

740 published skills · page 2 of 8

  1. ▌
    List Apps · agents-store
    List all applications and services in a Dokploy project Arguments: <project-name-or-id>.
    0 repo stars
  2. ▌
    CLI Recipes 13 · agents-store bundle
    Ready-to-use Flask CLI commands, covering flask run options and environment variables, flask shell with the app context, flask routes, Flask-Migrate (db init, migrate, upgrade, downgrade), custom click commands registered inside an application factory, and FLASK_APP and .flaskenv setup. Use it for any question about running, inspecting or scripting a Flask app from the terminal, in any language. For the project layout use project-scaffold.
    0 repo stars
  3. ▌
    API Design 2 · agents-store bundle
    Next.js API design patterns for Route Handlers (app/api/**/route.ts): input validation, response and error shapes, streaming and SSE, webhooks, CORS, versioning, caching GET handlers, and choosing between a Route Handler and a Server Action. Not for form handling with Server Actions (form-handling) or for fetching data in Server Components (data-fetching).
    0 repo stars
  4. ▌
    Features · agents-store
    Read the release notes across a version range and report which newly added config keys and commands this fleet could adopt — per instance, with a recommendation, a risk class and a reason. Nothing is switched on. Arguments: <selector> [--from <version>].
    0 repo stars
  5. ▌
    Add Domain · agents-store
    Add a custom domain to a Dokploy application Arguments: <domain> --app <app-name-or-id> [--port <port>] [--https].
    0 repo stars
  6. ▌
    Create App · agents-store
    Create a new application in a Dokploy project Arguments: <name> --project <project> [--env <environment>] [--build <nixpacks|dockerfile|static>].
    0 repo stars
  7. ▌
    Documents 2 · agents-store bundle
    This skill should be used when the user asks to "create the macstack folder", "set up project docs", "where do user cases live", "add a screen", "add a trigger", "standardize the project documents", "repair the macstack folder", "migrate docs into macstack", mentions `macstack/`, OVERVIEW, USER-CASES, UX-UI, AUTOMATION, HANDBOOK, OPEN-QUESTIONS, DECISIONS, the client inbox or the document log — and BEFORE any other skill reads or writes anything under `macstack/`. Defines the folder standard AND the document shape: layout, path resolution, ID spaces, the pointer bindings, the bullet-label form, the language rule, the immutability guardrails, rendering and migration.
    0 repo stars
  8. ▌
    N8n Native MCP 2 · agents-store bundle
    Guide for the n8n native (instance-level) MCP server. Use when creating workflows from SDK code, editing workflows with update_workflow operations, executing or testing workflows, publishing/unpublishing, getting node type definitions, calling get_workflow_sdk_reference or get_workflow_best_practices, building first-class n8n Agents (create_agent, mutate_agent, call_agent), or working with the official n8n MCP server. Also use when asking about "native MCP", "n8n SDK", "workflow from code", "execute workflow", "Available in MCP", "instance-level MCP".
    0 repo stars
  9. ▌
    CLI Recipes 14 · agents-store bundle
    Next.js 16 command-line recipes — create-next-app, next dev and next build with Turbopack as the default (--webpack to opt out), next start, the built-in bundle analyzer, next upgrade with codemods, and linting now that next lint is removed. Use when the question is which next command, flag or package script to run. Docker packaging is docker-patterns.
    0 repo stars
  10. ▌
    Audit 3 · agents-store
    Full fleet audit in an isolated agent — one prioritised report with a ready repair line under every finding Arguments: [selector] [--focus auth|versions|memory|cron|secrets|security|shared|all].
    0 repo stars
  11. ▌
    Clone · agents-store
    Create a new instance from the reference one — isolation preflight, a genuinely free port, materialisation of compose and state, then the remaining manual steps printed rather than skipped Arguments: <new-instance> [--from <reference>] [--port auto|<n>] [--yes].
    0 repo stars
  12. ▌
    Diagram · agents-store
    Generate a specific diagram — architecture, flow, db, sequence, deps Arguments: <type> [scope] — types: architecture, flow <feature>, db, sequence <endpoint>, deps <module>.
    0 repo stars
  13. ▌
    Explain · agents-store
    Step-by-step explanation of a file, function, or module with mini-diagram if appropriate Arguments: <file-path|module-path|symbol-name>.
    0 repo stars
  14. ▌
    Onboard · agents-store
    Generate a full onboarding report — README summary, stack, folder structure, entry points, how to run locally, and 3 main diagrams (architecture, main flow, DB) Arguments: (no arguments — analyzes current project).
    0 repo stars
  15. ▌
    Analyze · agents-store
    AI-summarise a failed Dokploy deployment or a crashing container via the configured ai provider Arguments: deployment-id|app-name-or-id|compose-name-or-id.
    0 repo stars
  16. ▌
    Cleanup · agents-store
    Reclaim disk space on the Dokploy server with a guided cleanup chain Arguments: --dry-run.
    0 repo stars
  17. ▌
    Review 2 · agents-store
    Give the client the documents to read and answer — a self-contained HTML file, a published page, or both — and take their answers back Arguments: [--read | --artifact | --only <sections> | --skip <sections> | (empty = the whole package)].
    0 repo stars
  18. ▌
    Update 2 · agents-store
    Close the loop after work — bring the client documents, the spec and the generated documents up to what the code now does, move task statuses to what the audit found, journal the work and curate the changelog Arguments: [--after M11-T9 | --release M11 | --dry | (empty = every task finished since the last work entry)].
    0 repo stars
  19. ▌
    Repair · agents-store
    The only repair funnel — dispatch one catalog finding id through its eight-block plan, apply on a later turn, verify Arguments: <selector> --issue <finding-id> [--all-findings] [--yes].
    0 repo stars
  20. ▌
    Rollback · agents-store
    Roll a Dokploy application or compose stack back to a previous version Arguments: <app-name-or-id|compose-id>.
    0 repo stars
  21. ▌
    API Call · agents-store
    Build (and optionally run) an authenticated Chatwoot REST API request — picks the correct API family and auth header, reads GETs freely, and confirms before any write. Arguments: resource or action,e.g. "list open conversations in inbox 5".
    0 repo stars
  22. ▌
    Create DB · agents-store
    Create and deploy a database in a Dokploy project Arguments: <name> --project <project> --type <postgres|mysql|mariadb|mongo|redis|libsql> [--password <pass>].
    0 repo stars
  23. ▌
    Flows · agents-store
    Find main user flows (entry points → services → DB) and visualize them Arguments: (no arguments — auto-discovers flows).
    0 repo stars
  24. ▌
    Env Sync 2 · agents-store bundle
    Synchronize .env with .env.example for Dify Docker deployments, including the optional envs/ templates — detect new, removed and changed variables, add missing ones with default values, preserve existing customizations, never print secrets. Use when syncing env variables, checking for new Dify configuration variables, comparing .env.example vs .env, "env sync", "new env variables", "missing environment variables", or after pulling Dify updates.
    0 repo stars
  25. ▌
    Debug · agents-store
    Debug a failed or stuck Dokploy deployment with full decision-tree analysis Arguments: app-name-or-id|compose-id.
    0 repo stars
  26. ▌
    Plan · agents-store
    Turn requirements nobody scheduled into well-described tasks, edit tasks and milestones, and reconcile TASKS.md with the team's own tracker Arguments: [add <what> | sync | status | milestone <id> | (empty = find unplanned work)].
    0 repo stars
  27. ▌
    Auth 3 · agents-store
    Provider credential state across the fleet — classify every profile, print the logins a human must run, watch for expiry and account drift Arguments: [selector] [--provider <id>] [--status] [--print-login] [--watch].
    0 repo stars
  28. ▌
    Exec · agents-store
    Run one openclaw CLI call against selected instances through the single audited door Arguments: <selector> -- <openclaw args…> [--json] [--timeout <s>].
    0 repo stars
  29. ▌
    Logs 2 · agents-store
    Fan out gateway logs across selected instances, redacted, with per-instance headers Arguments: [selector] [--tail <n>] [--since <dur>] [--grep <re>] [--errors-only].
    0 repo stars
  30. ▌
    Review · agents-store
    Review a file, directory, or PR diff in beginner-friendly mode — structured feedback with "why" explanations Arguments: <file-path|directory|PR#>.
    0 repo stars
  31. ▌
    Deploy · agents-store
    Deploy or redeploy a Dokploy application or Docker Compose service Arguments: <app-name-or-id> [--project <project>].
    0 repo stars
  32. ▌
    Status · agents-store
    Check Dokploy application or deployment status Arguments: <app-name-or-id> [--project <project>].
    0 repo stars
  33. ▌
    Check · agents-store
    Validate the spec and the documents, report where the project stands and what to run next, or audit the implementation against the documents Arguments: [--docs | --code | --new | (empty = spec + documents + dashboard)].
    0 repo stars
  34. ▌
    Start · agents-store
    Create or repair a project's macstack/ folder and macstack.json — from nothing (a six-question interview), from an existing macstack.json, from an existing codebase, or by migrating an older layout Arguments: [project path | business request | (empty = design from scratch) | --migrate].
    0 repo stars
  35. ▌
    DB · agents-store
    Parse models, migrations, or schema and generate an ERD diagram + DB documentation Arguments: (no arguments — auto-detects models).
    0 repo stars
  36. ▌
    Update · agents-store
    Update self-hosted Dify — pre-flight (Weaviate migration gate), back up volumes with the stack down, merge a release tag into dev, sync env, pull images, verify Arguments: [tag-or-version|main] [--yes] [--weaviate-staged].
    0 repo stars
  37. ▌
    Setup 26 · agents-store bundle
    Audit an existing Flask project against the recommended patterns, covering the application factory, blueprint registration, config classes and SECRET_KEY handling, CSRF protection, dependencies and file structure. Use it when the user asks whether a Flask app is set up correctly, wants its structure or configuration reviewed, or has inherited a codebase before adding features, in any language. For starting a new project use project-scaffold.
    0 repo stars
  38. ▌
    Logs · agents-store
    Read runtime or build logs for a Dokploy application, compose stack, database, or deployment Arguments: <resource-name-or-id> [--type <app|compose|db|deployment>] [--tail <N>] [--since <1h>] [--search <term>].
    0 repo stars
  39. ▌
    Setup 27 · agents-store bundle
    Verify NocoDB connection for schema-development work — MCP and REST (curl on Meta API v3). Use when: - "check NocoDB dev setup" - "verify NocoDB API access" - "is my NocoDB token working?" - "can I modify schema?" - "test NocoDB MCP connection"
    0 repo stars
  40. ▌
    Authentication 6 · agents-store bundle
    This skill should be used when the user wants to "add authentication to Directus + Next.js", "implement Directus login in Next.js", "use NextAuth with Directus", "use Better Auth with Directus", "protect Next.js pages with Directus auth", "choose an auth approach for Directus and Next.js", "decide who owns the session", "act as the signed-in user inside a trigger.dev task", or needs to decide who owns the end-user session and the tokens across Directus and Next.js.
    0 repo stars
  41. ▌
    Layers And Boundaries · agents-store bundle
    Use when the user asks about "Flask SQLAlchemy architecture", "where to create db in Flask", "Flask app context and SQLAlchemy session", "when to commit in Flask", "Flask transaction boundary", "expire_on_commit in Flask-SQLAlchemy", "DetachedInstanceError in Flask", "Working outside of application context", "N+1 in a Jinja template", "lazy raise in Flask", "data saved in tests but lost in production", or needs the rules for where each layer of a Flask + SQLAlchemy app starts and ends.
    0 repo stars
  42. ▌
    Background Tasks 2 · agents-store bundle
    This skill should be used when the user wants to "offload work to trigger.dev from next.js", "run a background job from a server action", "trigger a task from a route handler", "delegate slow work to trigger.dev", "decide what runs in a Server Action and what in a task", "show a task's progress in next.js", "give the browser a token for a trigger.dev run", "keep task environment variables apart from next.js", "fix a TRIGGER_SECRET_KEY build error", or needs the rules where a Next.js App Router app hands work to Trigger.dev and gets the result back.
    0 repo stars
  43. ▌
    Data Access Selection · agents-store bundle
    This skill should be used when the user needs to choose how to read or write data in the Composable Stack — "NocoDB MCP or PostgreSQL MCP", "PostgREST or MCP", "which data access should I use", "how should n8n read the database", "how should a Trigger.dev task call PostgreSQL", "complex SQL or simple CRUD", "batch data operation", or is picking between the stack's data-access paths.
    0 repo stars
  44. ▌
    Directus To Nextjs 4 · agents-store bundle
    This skill should be used when the user wants to "fetch Directus data in Next.js", "display Directus content in Next.js pages", "render Directus images in Next.js", "use Directus SDK with Server Components", "create Next.js pages from Directus collections", "add TypeScript types for Directus", "cache Directus data in Next.js", "revalidate after Directus content changes", "fix 403 on Directus images", or needs the rules where Directus data meets Next.js rendering: who holds the token, what is cached, how files are served, and how types follow the schema.
    0 repo stars
  45. ▌
    Directus To Trigger 2 · agents-store bundle
    This skill should be used when the user wants to "trigger a task from a directus flow", "run a background task when a directus item is created or updated", "forward directus webhooks to trigger.dev", "process directus items asynchronously", "build a directus flow to next.js to trigger pipeline", "have a task write back to directus", "stop a directus flow and task from looping", "read and write directus from a trigger.dev task", or needs the pattern for wiring Directus Flow events through Next.js into Trigger.dev tasks and back.
    0 repo stars
  46. ▌
    Benchmark Sandbox · agents-store bundle
    Run vercel-plugin eval scenarios in Vercel Sandboxes instead of local WezTerm panels. Provisions ephemeral microVMs with Claude Code + plugin pre-installed, runs benchmark prompts, extracts hook artifacts, and produces coverage reports.
    0 repo stars
  47. ▌
    Document Rules · agents-store bundle
    Mandatory rules for generating any business document (proposal, invoice, estimate, report, presentation, contract, NDA, certificate of completion). This skill should be used at the start of every document generation request, before gathering data or running a script, to apply the first-use onboarding check, the dependency check, the data collection protocol, the output location policy, and the format defaults, and to reply in the user's language.
    0 repo stars
  48. ▌
    Postgrest API · agents-store bundle
    This skill should be used when the user wants to "use PostgREST", "make REST calls to PostgreSQL", "CRUD over HTTP on a PostgreSQL table", "upsert with on_conflict", "Prefer header options", "return=representation", "max-affected", "call a stored function over REST", "read PostgreSQL from an n8n HTTP Request node", or "read PostgreSQL from a Trigger.dev task with fetch".
    0 repo stars
  49. ▌
    Examples 51 · agents-store bundle
    End-to-end scenario walkthroughs for the Directus + Next.js + Trigger.dev stack. This skill should be used when the user asks for "directus nextjs trigger.dev examples", "how to build a blog with directus + next.js", "ai enrichment pipeline example", "scheduled data sync example", "show me a complete example with background tasks", or needs implementation references for common application types on this stack.
    0 repo stars
  50. ▌
    User Preferences 2 · agents-store bundle
    First-use onboarding, user style preferences, company profiles, and logo management for document generation. This skill should be used on the first document generation request to collect user preferences, when the user wants to change their style, or when managing company logos and branding profiles.
    0 repo stars
  51. ▌
    Template Reference 2 · agents-store bundle
    Use this skill when the user asks about "template hierarchy", "template levels", "project template conventions", "what files go in a template", "Level 0 vs Level 1", "template structure", "what belongs in the parent template", or needs reference documentation for the project template system and its 4-level hierarchy.
    0 repo stars
  52. ▌
    Chatbot Contacts Messaging 2 · agents-store bundle
    Chatbot contact management, direct messaging across channels, contact variables, tags, and notes. Use when sending messages to contacts, managing contact data, or looking up subscribers.
    0 repo stars
  53. ▌
    Deployment 7 · agents-store bundle
    This skill should be used when the user wants to "run the Directus Next.js Trigger.dev stack locally", "deploy trigger.dev tasks next to a Next.js app", "set environment variables for trigger.dev tasks", "configure content-change webhooks with trigger.dev", "revalidate the site when a task changes Directus content", "CI/CD for trigger tasks", "production checklist for directus + nextjs + trigger.dev", or needs the pipelines that connect the three services and the checks before production. For platform-specific hosting (Vercel, Dokploy, etc.), see the respective deployment plugin.
    0 repo stars
  54. ▌
    Directus To Nextjs 3 · agents-store bundle
    This skill should be used when the user wants to "fetch Directus data in Next.js", "display Directus content in Next.js pages", "render Directus images in Next.js", "use Directus SDK with Server Components", "create Next.js pages from Directus collections", "add TypeScript types for Directus", "cache Directus data in Next.js", "revalidate after Directus content changes", "fix 403 on Directus images", or needs the rules where Directus data meets Next.js rendering: who holds the token, what is cached, how files are served, and how types follow the schema.
    0 repo stars
  55. ▌
    Document Generator 2 · agents-store bundle
    Document generation process -- format selection, data collection, script invocation, and delivery. This skill should be used when generating any document (proposal, invoice, estimate, report, presentation, contract, NDA, certificate of completion), deciding which format or engine to use, or running generation scripts.
    0 repo stars
  56. ▌
    Document Templates 2 · agents-store bundle
    Document template structures and data collection checklists for each document type (proposal, invoice, estimate, report, presentation, contract, NDA, certificate of completion). This skill should be used when determining what data to collect from the user, what fields are required or optional, or how to structure a specific document type.
    0 repo stars
  57. ▌
    Postgres MCP Tools · agents-store bundle
    This skill should be used when the user wants to "run SQL through MCP", "use the PostgreSQL MCP tools", "execute_sql", "inspect a database schema over MCP", "list indexes, locks or bloated tables", "analyze query performance with MCP", "check database status", "get a query plan", "MCP Toolbox for Databases", or needs the tool reference of the 29-tool PostgreSQL MCP server for querying and administering a PostgreSQL database.
    0 repo stars
  58. ▌
    Full Feature 7 · agents-store bundle
    This skill should be used when the user wants to "build a complete feature with directus nextjs and trigger.dev", "create an end-to-end feature with background tasks", "implement a full crud feature with async processing", "build a new section of the site that uses background jobs", "add a page backed by directus with a background task", or needs a step-by-step recipe for building features that span Directus, Next.js, and Trigger.dev.
    0 repo stars
  59. ▌
    Init Project 6 · agents-store bundle
    This skill should be used when the user asks to "set up Directus + Next.js + Trigger.dev project", "initialize directus nextjs trigger.dev stack", "bootstrap the 3-service stack", "configure directus next.js and trigger.dev together", "connect trigger.dev to a directus nextjs app", "scaffold stack with background tasks", "start a new project with background jobs", or needs to set up environment variables, versions and verify connections for the Directus + Next.js + Trigger.dev stack.
    0 repo stars
  60. ▌
    Formatting Standards 2 · agents-store bundle
    Typography, font, margin, color, and layout standards for professional business documents. Use this skill when making any formatting decisions — choosing fonts, colors, margins, spacing, or layout patterns for any document type.
    0 repo stars
  61. ▌
    Audit Stack 2 · agents-store bundle
    Use when the user asks to "audit project stack", "analyze technologies", "scan dependencies", "generate stack.json", "what template level is this project", "map project to layers", or wants to discover all technologies in a codebase and get template and stack.json recommendations.
    0 repo stars
  62. ▌
    Chatbot Management 2 · agents-store bundle
    Chatbot bots, statistics, tags, campaigns, flows, and dialogs. Use when managing bots, sending chatbot campaigns, running automation flows, or viewing bot statistics.
    0 repo stars
  63. ▌
    Courses Management · agents-store bundle
    SendPulse Courses (LMS) - academies, courses, pricing plans, student groups, tags, and students. Use when listing academies or courses, enrolling or removing students, marking students as paying, deleting a student, or checking student progress.
    0 repo stars
  64. ▌
    Deployment 6 · agents-store bundle
    This skill should be used when the user wants to "set up Docker for Directus with Next.js", "run Directus locally for a Next.js app", "configure content-change webhooks", "set up revalidation when Directus content changes", "auto-update the site on content change", "production checklist for Directus + Next.js", or needs the pipeline that connects Directus edits to Next.js pages and the checks before production. For platform-specific deployment (Vercel, Dokploy, etc.), see the respective deployment plugin.
    0 repo stars
  65. ▌
    Full Feature 5 · agents-store bundle
    This skill should be used when the user wants to "build a complete feature with Directus and Next.js", "create an end-to-end page from Directus data", "implement a full CRUD feature across Directus and Next.js", "build a new section of the site", "create a page that shows Directus data", "build a dashboard with Directus content", "display Directus collection in Next.js", "add a new page with CMS data", or needs a step-by-step recipe for building features that span both Directus and Next.js.
    0 repo stars
  66. ▌
    Init Project 5 · agents-store bundle
    This skill should be used when the user asks to "set up Directus + Next.js project", "initialize Directus Next.js stack", "configure Directus with Next.js", "connect Directus to Next.js", "bootstrap Directus Next.js app", "create Next.js app with Directus", "scaffold Directus + Next.js", "start new project with Directus", "create a new Directus Next.js project", or needs to set up environment variables and verify connections for the Directus + Next.js stack.
    0 repo stars
  67. ▌
    Vercel Sandbox 3 · agents-store
    Run untrusted or AI-generated code in ephemeral Firecracker microVMs with @vercel/sandbox. Create a VM, run commands, read/write files, expose ports, snapshot and resume. Use for AI agents, code execution, builds, and isolated experimentation.
    0 repo stars
  68. ▌
    Report Generation 2 · agents-store bundle
    Use to turn research findings the user already has into a finished report in one of three formats - Executive Summary, Deep Research Report or Comparison Table - with cited sources, a Methodology section, confidence levels and gaps, or to choose the template that fits a research type or depth. Not for doing the research itself (deep-research, search-strategies) or reading pages (content-extraction).
    0 repo stars
  69. ▌
    Search Strategies 2 · agents-store bundle
    Search strategy guidelines — tool selection, fallback chains, query optimization, and parallel search orchestration. Use when choosing which search tools to use, handling tool failures, or optimizing search queries.
    0 repo stars
  70. ▌
    Full Feature 6 · agents-store bundle
    Use when the user asks to "add a new feature", "create a new page", "build CRUD for a new entity", "add a new section to the app", "implement a full feature end-to-end", or needs a step-by-step recipe for building a complete feature across Flask + SQLAlchemy layers.
    0 repo stars
  71. ▌
    Content Extraction 2 · agents-store bundle
    Content reading and extraction guidelines — reading URLs, scraping pages, crawling sites, extracting PDFs, and taking screenshots. Use when reading web content, extracting structured data from pages, or processing documents.
    0 repo stars
  72. ▌
    Authentication 5 · agents-store bundle
    This skill should be used when the user wants to "add authentication to Directus + Next.js", "implement Directus login in Next.js", "use NextAuth with Directus", "use Better Auth with Directus", "protect Next.js pages with Directus auth", "choose an auth approach for Directus and Next.js", "decide who owns the session", or needs to decide who owns the end-user session and the tokens across Directus and Next.js.
    0 repo stars
  73. ▌
    Teams Sdk Teams Dev · agents-store bundle
    Use this skill whenever the user mentions Microsoft Teams in a development context — whether they're building, integrating, configuring, debugging, or just asking questions. Covers bots, message extensions, embedded web apps, Adaptive Cards, dialogs, SSO, infrastructure, the Teams Developer CLI/SDK, and general Teams platform queries. If the word "Teams" appears, err on the side of invoking this skill.
    0 repo stars
  74. ▌
    API Reference 18 · agents-store bundle
    Manual reference (invoke /vaultwarden-dev:api-reference) for "Vaultwarden API endpoints", "Vaultwarden REST API routes", "Vaultwarden token grants", "Vaultwarden curl examples" — exact HTTP routes, payloads and auth of a Vaultwarden server.
    0 repo stars
  75. ▌
    Examples 49 · agents-store bundle
    End-to-end scenario walkthroughs for the Directus + Next.js stack. This skill should be used when the user asks for "Directus Next.js examples", "how to build a blog with Directus and Next.js", "Directus Next.js product catalog", "show me a complete example", or needs implementation references for common application types.
    0 repo stars
  76. ▌
    Secret Hygiene · agents-store bundle
    This skill should be used when a Vaultwarden or bw task could print, log or store a secret — "store BW_SESSION", "show me the password from Vaultwarden", "export the vault in plain text", "put the master password in a script" — to keep secrets out of chat, logs, git and argv.
    0 repo stars
  77. ▌
    Deep Research 2 · agents-store bundle
    Main research automation skill. 7-step algorithm for comprehensive research with 6 research types, query planning, parallel search, extraction, synthesis, and structured reporting. Use when conducting any multi-step research task.
    0 repo stars
  78. ▌
    Examples 50 · agents-store bundle
    End-to-end document generation examples, workflow walkthroughs, and complete JSON input samples for all document types (proposal, invoice, estimate, report, presentation, contract, NDA, certificate of completion). This skill should be used when the user asks for a worked example, wants to see a sample document, needs a template pattern to follow, or asks how to create a specific document step by step.
    0 repo stars
  79. ▌
    Workspace Overview 2 · agents-store bundle
    OpenClaw workspace architecture and file system overview — directory structure, file loading mechanics, character limits, scan categories (A-J), and subfolder organization patterns. Use this skill whenever the user asks about how the workspace is structured, what files get loaded automatically, character limits, what goes where, or how to organize their workspace. This is the foundational skill for workspace content — use it first when the user is new to OpenClaw or asks broad questions about workspace organization, even before more specific skills like agents-md or soul-md.
    0 repo stars
  80. ▌
    Webhook Management 3 · agents-store bundle
    Webhook CRUD, event types, testing, delivery logs, statistics, and toggle. Use when setting up webhooks for order, product, category, customer, or cart notifications or debugging webhook delivery.
    0 repo stars
  81. ▌
    React Best Practices · agents-store bundle
    React best-practices reviewer for TSX files. Triggers after editing multiple TSX components to run a condensed quality checklist covering component structure, hooks usage, accessibility, performance, and TypeScript patterns.
    0 repo stars
  82. ▌
    Admin Panel · agents-store bundle
    This skill should be used when the user asks to "use the Vaultwarden admin API", "script the /admin panel", "disable or delete a Vaultwarden user", "reset a user's 2FA", "change Vaultwarden config", or mentions ADMIN_TOKEN or the VW_ADMIN cookie.
    0 repo stars
  83. ▌
    CLI Recipes 12 · agents-store bundle
    This skill should be used when the user asks to "use bw with Vaultwarden", "get a password from Vaultwarden in a script", "create a Vaultwarden item from the CLI", "confirm org members with bw", "run bw serve", or needs Bitwarden CLI recipes for a self-hosted Vaultwarden.
    0 repo stars
  84. ▌
    Create A Backend · agents-store bundle
    Backend architecture guidance. Use when planning, building, or migrating an API or backend; choosing between Functions, Services, containers, Workflow, Queues, and Marketplace databases; or selecting a supported backend framework or runtime.
    0 repo stars
  85. ▌
    Codemap Examples 2 · agents-store
    This skill should be used when the user asks for "codemap examples", "how to use codemap", "show me what codemap can do", "codemap walkthrough", or wants to see end-to-end usage scenarios for the codemap plugin.
    0 repo stars
  86. ▌
    Using N8n MCP Skills · agents-store bundle
    Use when building, editing, validating, testing, or debugging an n8n workflow through the n8n-mcp MCP server — designing a flow, configuring a node, writing an expression or Code node, wiring credentials, or fixing one that misbehaves. The entry-point skill for the n8n-mcp-skills pack: it routes you to the right specialist skill, gives working knowledge of every n8n-mcp tool from turn one, and states the rules that keep workflows from breaking in production. Always consult it first on any n8n, workflow, node, or automation task — even a quick one-off, and even when the user names no skill — because n8n's surface drifts between versions and the specialist skills prevent silent failures.
    0 repo stars
  87. ▌
    Standing Orders 2 · agents-store bundle
    Design patterns for OpenClaw standing orders — autonomous programs that give an agent permanent operating authority for defined tasks. Use when the user wants an OpenClaw agent to run recurring or scheduled work on its own, such as periodic reports, monitoring or content scheduling, or asks for the execute-verify-report pattern or cron jobs with OpenClaw. Heartbeat tuning belongs to heartbeat-md.
    0 repo stars
  88. ▌
    Improve 2 · agents-store
    Use this skill when the user says "improve", "this should be better", "fix this in the source", "this belongs in the plugin", "this belongs in the template", "push this upstream", "improve the plugin", "improve the template", or discovers any improvement while working in a child project that should go to either a plugin or a parent template. This is the unified entry point that auto-routes to the correct system.
    0 repo stars
  89. ▌
    Wrap Up 2 · agents-store bundle
    Use this skill when the user says "wrap up", "end session", "done for today", "session review", "what should go into the template", "template improvements", "save template learnings", "review what we did for the template", "plugin improvements", "what should go into the plugin", or at the end of a work session to review what discoveries should be pushed up to parent templates or plugins.
    0 repo stars
  90. ▌
    MCP Patterns 8 · agents-store bundle
    This skill should be used when the user asks for "a Vaultwarden MCP server", "connect Claude to my Vaultwarden", "use the Bitwarden MCP server with Vaultwarden", "warden-mcp", or wants an agent to query a self-hosted vault through MCP tools instead of shell commands.
    0 repo stars
  91. ▌
    Sdk Patterns 5 · agents-store bundle
    This skill should be used when the user asks for a "Vaultwarden SDK" or "Bitwarden SDK for Vaultwarden", to "automate Vaultwarden from Python", "use python-vaultwarden", "manage Vaultwarden with Terraform", or wants a library rather than curl/bw for a self-hosted Vaultwarden.
    0 repo stars
  92. ▌
    Troubleshoot 28 · agents-store bundle
    This skill should be used when the user reports Vaultwarden errors — "Username or password is incorrect" with the right password, "404 on user-key-id", "Vaultwarden 401 or 429", "invites not arriving", "bw sync hangs" — or needs to diagnose a self-hosted Vaultwarden or bw failure.
    0 repo stars
  93. ▌
    Cost Awareness · agents-store bundle
    Use as the budget gate before the first paid DataForSEO api_request of a task, after the task skill has chosen its endpoints, and for any question about DataForSEO pricing - what a call costs, which calls are free, how to estimate or cap spend, how to check the account balance, and how to keep a bill small with bulk endpoints and explicit limit or depth.
    0 repo stars
  94. ▌
    Docker Local Dev · agents-store bundle
    Run Directus 12 locally with Docker Compose — PostgreSQL, Redis, upload and extension volumes, secrets from .env, /server/ping health check, pinned image tag, first admin, extensions on hardened images, upgrades. This skill should be used when the user asks to "run Directus locally", "Directus Docker Compose", "Directus local dev stack", "start a local Directus instance", "docker-compose.yml for Directus", or needs a throwaway Directus to develop a frontend, flows or schema against.
    0 repo stars
  95. ▌
    Session Analysis 2 · agents-store bundle
    Techniques for analyzing OpenClaw session transcripts (listed through the CLI, exported as a trajectory bundle, then queried with jq) to understand user behavior, tool effectiveness, error patterns, token costs, and active hours. Use this skill whenever the user wants to analyze how their agent is performing, what users are asking, which tools work best, what errors occur, or how to improve the workspace based on real usage data. Also applies to questions like "what do my users ask about", "is my agent working well", or "show me session stats".
    0 repo stars
  96. ▌
    Examples 48 · agents-store bundle
    Use this skill when the user asks for "examples", "how does template feedback work", "show me a walkthrough", "demo the template workflow", or needs to see end-to-end scenario walkthroughs for the project-template-dev plugin.
    0 repo stars
  97. ▌
    Feedback 3 · agents-store bundle
    Use this skill when the user says "this should be in the parent template", "fix the template", "add this to project-template", "send feedback to parent", "improve the base template", "this skill belongs in the template", "update the parent", "push this up to the template", "the template needs this", "this is missing from the template", or discovers any issue while working in a child project that should be fixed in a parent template (Level 0 or Level 1).
    0 repo stars
  98. ▌
    Validate 2 · agents-store bundle
    Use this skill when the user asks to "validate template", "check template structure", "is my template correct", "verify template conventions", "validate project template", "check template files", or needs to verify that a project template follows the Level 0/1/1.5/2 conventions and has all required files.
    0 repo stars
  99. ▌
    Examples 46 · agents-store bundle
    Tool call patterns, end-to-end research workflow examples, and scenario references for all 6 research types. Use when you need reference implementations or complete research examples.
    0 repo stars
  100. ▌
    Auth Flask Login · agents-store bundle
    Use when the user asks about "Flask-Login", "Flask login and logout", "Flask user registration", "Flask authentication", "Flask login_required", "Flask password hashing", "Flask session auth", "protect Flask routes", "Flask logout POST CSRF", "Flask login next redirect", or needs the session-based login flow for a Flask 3 application with CSRF protection.
    0 repo stars