all publishers

agents-store

@agents-store source repo

740 published skills · page 3 of 8

  1. ▌
    Project Scaffold · agents-store bundle
    Use when the user asks to "create a new Flask project", "scaffold a Flask app", "start a Flask project", "Flask project structure", "Flask project layout", "init Flask project", "Flask with SQLAlchemy and migrations from scratch", or needs the initial layout, application factory, config, .env and .gitignore for a new Flask 3 application.
    0 repo stars
  2. ▌
    N8n Error Handling · agents-store bundle
    Wire n8n error handling so failures are loud, structured, and recoverable. Use when building any webhook/API workflow, a scheduled or unattended workflow, or any path where a silent failure would drop user-visible work — and whenever the user mentions error handling, onError, continueErrorOutput, error branches/outputs, retries, retryOnFail, Respond to Webhook status codes, 4xx/5xx, Error Trigger, or "my workflow fails silently". Covers per-node error outputs and wiring, retry/self-healing, error-trigger workflows, and 4xx/5xx response shapes.
    0 repo stars
  3. ▌
    Memory System 2 · agents-store bundle
    Guide for OpenClaw's memory system — MEMORY.md curation, daily logs, memory flush, and vector search. Use this skill whenever the user asks about how the agent remembers things between sessions, wants to configure memory management, needs to understand daily logs versus long-term memory, or is setting up memory curation processes. Also applies to questions about vector search, memory security in groups, or "how does the agent remember".
    0 repo stars
  4. ▌
    AI Chat Agents · agents-store bundle
    Build durable AI chat agents on Trigger.dev with chat.agent, sessions and the useTriggerChatTransport React transport (requires server 4.5.0 or newer and AI SDK 5+). Use when the user asks about "chat.agent", "trigger.dev chat agent", "AI chat on trigger.dev", "useTriggerChatTransport", "trigger.dev sessions", "start_agent_chat", "human in the loop chat", or migrating a streamText route to Trigger.dev.
    0 repo stars
  5. ▌
    Release · agents-store
    Release vercel-plugin — run gates, bump version, generate artifacts, commit, and push. Use when asked to "release", "ship", "bump and push", or "cut a release".
    0 repo stars
  6. ▌
    Vercel Firewall · agents-store
    Vercel Firewall expert guidance — automatic DDoS mitigation, the Vercel WAF (custom rules, IP blocking, managed rulesets, rate limiting), Attack Mode, system bypass, bot management, and the `vercel firewall` CLI. Use when configuring platform-level security, responding to attacks, or staging firewall rules.
    0 repo stars
  7. ▌
    Vercel Services · agents-store bundle
    Configure and troubleshoot Vercel Services for multiple frontends and backends in one project. Use when composing a polyglot or multi-service application on one Vercel deployment; defining the `services` key, service-targeted rewrites, or service bindings in `vercel.json`; or running all services with `vercel dev`.
    0 repo stars
  8. ▌
    Bootstrap Boot 2 · agents-store bundle
    Guide for BOOTSTRAP.md (first-run setup ritual) and BOOT.md (gateway restart checklist) in OpenClaw. Use this skill whenever the user is setting up a new agent for the first time, configuring onboarding flows, creating first-run discovery processes, or defining what should happen on gateway restart. Even questions like "what should happen when the agent starts for the first time", "how do I initialize a fresh agent", or "what runs on reboot" need this skill.
    0 repo stars
  9. ▌
    Create 2 · agents-store bundle
    Use this skill when the user asks to "create a new template", "scaffold a Level 1 template", "create project-{stack}", "make a new stack template", "fork project-template", "create a demo template", "set up a new project from template", or wants to create any new project template at Level 1, 1.5, or 2 from the universal base or a stack template.
    0 repo stars
  10. ▌
    Examples 47 · agents-store bundle
    This skill should be used when the user asks for a "full example", "sample audit", "example session audit", "what does the report look like", "show me a sample report", "example of the session doctor output", "what does a rejected token look like in the audit", or wants to see a complete rendered session audit before running one.
    0 repo stars
  11. ▌
    Agents Playground · agents-store bundle
    Use this skill when the user wants to test or debug a Microsoft Teams bot locally on Teams SDK 2.1 — Microsoft 365 Agents Playground (`agentsplayground`), accepting unauthenticated local requests (`dangerouslyAllowUnauthenticatedRequests`), the "No credentials configured … all incoming requests will be rejected" warning, mock activities, logs, replacing the deprecated DevTools. Triggers on "Agents Playground", "test Teams bot locally", "No credentials configured", "dangerouslyAllowUnauthenticatedRequests", "Teams DevTools replacement".
    0 repo stars
  12. ▌
    Catalog Import 2 · agents-store bundle
    Full catalog import with categories and products from JSON. Use when importing a complete catalog, migrating from another platform, or bulk-loading products.
    0 repo stars
  13. ▌
    Scheduled Tasks 2 · agents-store bundle
    Schedule Trigger.dev tasks with cron — declarative schedules defined on schedules.task, imperative per-user schedules created through the SDK or API, timezones, spreading windows, retries and idempotency of scheduled runs, testing, and why a schedule did not fire. Use when the user asks to "schedule a trigger.dev task", "run a task on a cron", "create a schedule", "dynamic or per-user schedules", "schedules:attach", "attach a schedule to production", "my schedule did not run", or "my cron runs a few minutes late".
    0 repo stars
  14. ▌
    Agents Md 2 · agents-store bundle
    Guide for creating and customizing AGENTS.md — the operating rules, procedures, and behavioral guardrails for an OpenClaw agent. Use this skill whenever the user is working on agent behavior, operating procedures, session startup sequences, memory management policies, group chat rules, safety red lines, tool usage priorities, or standing order references. Even if they just say "the agent should do X differently" or "add a rule for Y", this skill applies because operational rules belong in AGENTS.md. Also use when deciding what belongs in AGENTS.md versus SOUL.md — this skill clarifies the boundary.
    0 repo stars
  15. ▌
    Examples 44 · agents-store bundle
    MCP tool call patterns, multi-channel marketing workflow examples, and scenario references. Use when you need reference implementations for Sendpulse operations.
    0 repo stars
  16. ▌
    Cdn Caching · agents-store
    Debug Vercel CDN caching — cache hit rate, stale content, revalidation behavior, ISR + PPR, per-request cache reasons (cacheReason) and PPR state (ppr_state), and costs.
    0 repo stars
  17. ▌
    Build Agents · agents-store
    Default guidance for building AI agents. Use for generic requests to build, create, scaffold, design, architect, or implement an AI agent, agent app, tool-calling agent, durable agent, multi-agent system, or scheduled agent.
    0 repo stars
  18. ▌
    N8n Self Hosting · agents-store bundle
    Deploy a production self-hosted n8n end-to-end to a fresh Linux VM over SSH, using Docker Compose behind a Caddy reverse proxy with automatic HTTPS. Use whenever the user wants to self-host, install, provision, or deploy n8n on their own server/VPS (Hetzner, DigitalOcean, AWS EC2, bare metal) — single/regular mode or queue mode with workers — or to update, back up, restore, or harden such an instance, or make Python Code nodes run on it (task runners). For SELF-HOSTED n8n (Docker), not n8n Cloud and not building workflows. The skill makes the agent ask single-vs-queue first, collect domain/SSH/timezone inputs, generate fresh secrets on the box, and bring the stack up with TLS. Trigger on "deploy n8n", "self-host n8n", "n8n docker compose", "n8n queue mode / workers", "n8n reverse proxy / SSL", "back up / update my n8n", "Python runner unavailable" / "n8nio/runners sidecar", or "we don't want to give every user the OAuth client secret" / "enable Sign in with Google" (credential overwrites).
    0 repo stars
  19. ▌
    Identity Md 2 · agents-store bundle
    Guide for creating IDENTITY.md — the agent's name, creature type, vibe, emoji, and avatar in OpenClaw. Use this skill whenever the user is naming their agent, choosing an emoji or avatar, setting up the agent's visual identity, or asking how agent identity works. Even simple questions like "what should I name my agent", "how do I set the bot emoji", or "change the agent's avatar" need this skill.
    0 repo stars
  20. ▌
    Audit 2 · agents-store bundle
    Audits the current Claude Code session in one command — working directory, loaded CLAUDE.md and rules, skills, subagent types, plugins, hooks, MCP servers (connected, failed, waiting for auth), env variable names by source, the model and effort of the main session and of every subagent with the flag or setting that produced them, and the developer's mistakes with concrete fixes. Use when the user asks to audit, debug or check their Claude Code session, or asks what they are doing wrong.
    0 repo stars
  21. ▌
    Examples 45 · agents-store bundle
    This skill should be used when the user asks "how do I onboard/offboard someone in Vaultwarden", "show a Vaultwarden CI pipeline example", "back up and upgrade Vaultwarden", or wants an end-to-end walkthrough combining the admin panel, client API and bw CLI.
    0 repo stars
  22. ▌
    Runtime Cache · agents-store
    Vercel Runtime Cache API guidance — ephemeral per-region key-value cache with tag-based invalidation. Shared across Functions, Routing Middleware, and Builds. Use when implementing caching strategies beyond framework-level caching.
    0 repo stars
  23. ▌
    Heartbeat Md 2 · agents-store bundle
    Guide for OpenClaw heartbeats — the periodic background turn that surfaces anything needing attention. Current releases keep heartbeat instructions in the heartbeat monitor's scratch (a database row, managed with `openclaw automations scratch`) and the cadence in `agents.defaults.heartbeat`; the HEARTBEAT.md workspace file is retired and never read at runtime, but older workspaces still carry one. Use this skill whenever the user needs background monitoring, periodic checks, standing orders integration, quiet hours configuration, a leftover HEARTBEAT.md, or wants to understand heartbeat mechanics and token costs. Even questions like "how do I make the agent check something periodically", "set up monitoring", or "reduce heartbeat token costs" need this skill.
    0 repo stars
  24. ▌
    Sync 3 · agents-store
    Use this skill when the user says "sync from parent", "pull template changes", "merge parent template", "update from project-template", "my project is out of sync", "get latest template changes", "sync template", or needs to propagate improvements from a parent template (Level 0 or Level 1) down to a child project.
    0 repo stars
  25. ▌
    Custom Metrics · agents-store
    Emit and query Vercel Custom Metrics. Use when instrumenting application or business measurements in Vercel Functions, using metric() from @vercel/functions, choosing metric names and attributes, or querying emitted values with vc metrics.
    0 repo stars
  26. ▌
    Microfrontends · agents-store bundle
    Guide for building, configuring, and deploying microfrontends on Vercel. Use this skill when the user mentions microfrontends, multi-zones, splitting an app across teams, independent deployments, cross-app routing, incremental migration, composing multiple frontends under one domain, microfrontends.json, @vercel/microfrontends, the microfrontends local proxy, or path-based routing between Vercel projects. Also use when the user asks about shared layouts across projects, navigation between microfrontends, fallback environments, asset prefixes, or feature flag controlled routing.
    0 repo stars
  27. ▌
    Vercel Connect · agents-store
    Vercel Connect expert guidance for securely obtaining scoped credentials for third-party services on behalf of apps or users. Use when wiring up provider API access, OAuth, API-key services, MCP servers, triggers, framework adapters, or eve agent connections.
    0 repo stars
  28. ▌
    Eve · agents-store bundle
    eve framework guidance for durable AI agents and agent-powered applications. Use when creating, editing, or debugging an eve project, when the user explicitly asks for eve, or when the build-agents skill has selected eve as the default framework. Covers eve's filesystem-first runtime, durable sessions, tools, skills, connections, channels, sandboxes, subagents, schedules, evals, frontend clients, and Agent Runs observability. Do not use for incidental agent mentions, generic agent-building prompts, or established non-eve stacks unless the user asks for comparison or migration.
    0 repo stars
  29. ▌
    Auth 2 · agents-store
    Authentication integration guidance — Clerk (native Vercel Marketplace), Descope, and Auth0 setup for Next.js applications, plus Sign in with Vercel, Vercel Passport, and Vercel KMS. Covers proxy.ts auth patterns, sign-in/sign-up flows, and Marketplace provisioning. Use when implementing user authentication or protecting deployments.
    0 repo stars
  30. ▌
    MCP A2a · agents-store bundle
    Use this skill when the user is combining the Model Context Protocol or Agent2Agent with a Microsoft Teams bot on Teams SDK 2.1 — using a remote MCP server's tools in the agent, exposing the Teams bot as an MCP server (`find_user`, `notify`, `ask`, `request_approval`) with `@modelcontextprotocol/sdk`, bot-to-bot hand-off over A2A with `@a2a-js/sdk`. Triggers on "Teams MCP", "MCP server Teams", "expose Teams as MCP", "MCP client Teams bot", "A2A Teams", "human in the loop Teams".
    0 repo stars
  31. ▌
    AI Sdk · agents-store bundle
    Vercel AI SDK expert guidance. Use when building AI-powered features — chat interfaces, text generation, structured output, tool calling, agents, MCP integration, streaming, embeddings, reranking, image generation, or working with any LLM provider.
    0 repo stars
  32. ▌
    Queues · agents-store
    Vercel Queues guidance — durable topics with at-least-once delivery, independent consumer groups, retries, delays, and idempotency keys via @vercel/queue (JS) or vercel-queue (Python). Use when deferring background work, buffering traffic, fanning out events, or choosing between Queues and Workflows.
    0 repo stars
  33. ▌
    Domains · agents-store
    Search, register, connect, transfer, and renew domain names on Vercel using the CLI or Domains Registrar API. Use for domain availability and pricing, custom domains, DNS records, nameservers, ownership verification, and domain orders.
    0 repo stars
  34. ▌
    Webhooks 2 · agents-store bundle
    Use NocoDB webhooks from the business side — which events exist, how to set one up in the UI, what the receiving system gets (payload), conditions, the Button trigger, and testing. Use when: - "trigger something when a record changes" - "send NocoDB data to n8n / another system" - "set up a webhook in NocoDB" - "what does the NocoDB webhook payload look like" - "fire a webhook from a button" - "webhook only when status becomes ..." - "list the webhooks on a table"
    0 repo stars
  35. ▌
    Flags Sdk · agents-store bundle
    Set up and use feature flags and A/B tests with the Flags SDK (`flags` npm package) and Vercel Flags. Use when installing or configuring the SDK, adding a new or existing flag, wiring `vercelAdapter` (OIDC or SDK keys), declaring flags with `flag()`, using the `vercel flags` CLI (create, inspect, list, enable, disable, set, update, split, rollout, rules, segments, use-targeting, evaluations, versions, open, archive, unarchive, rm, sdk-keys, override, prepare), setting up providers/adapters (Vercel, Statsig, LaunchDarkly, PostHog, GrowthBook, Global Config, OpenFeature, Split, Flagsmith, Reflag, Optimizely, or custom), precompute, `identify`/`dedupe`, Flags Explorer/Toolbar, Next.js or SvelteKit, or encrypting flag values. Triggers: feature flags, feature gates, A/B testing, experimentation, gradual rollout, traffic split, targeting rules, flag overrides, precompute, Flags Explorer, Vercel Flags, vercel flags CLI, `flags/next`, `flags/sveltekit`, `flags/react`, `@flags-sdk/*`.
    0 repo stars
  36. ▌
    Tools Md 2 · agents-store bundle
    Guide for the local tool notes of an OpenClaw agent — environment-specific tool notes, search priorities, device names, and local infrastructure details. On current releases these live in the `## Tools` section of AGENTS.md (the standalone TOOLS.md file is retired); older workspaces still carry TOOLS.md. Use this skill whenever the user is configuring which tools their agent should prefer, adding environment notes, documenting search tool priority orders, or setting up device/API references. Even questions like "which search tool should my agent use first", "how do I tell the agent about my devices", or "add tool notes" need this skill.
    0 repo stars
  37. ▌
    Setup 25 · agents-store bundle
    This skill should be used when the user asks to "connect to Vaultwarden", "point bw at my Vaultwarden server", "check Vaultwarden is reachable", "get a Vaultwarden API token", "call the Vaultwarden REST API", "manage org members via the API", or "sync users from LDAP into Vaultwarden".
    0 repo stars
  38. ▌
    Chat Sdk 2 · agents-store bundle
    Vercel Chat SDK expert guidance. Use when building multi-platform chat bots — Slack, Telegram, Microsoft Teams, Discord, Google Chat, GitHub, Linear — with a single codebase. Covers the Chat class, adapters, threads, messages, cards, modals, streaming, state management, and webhook setup.
    0 repo stars
  39. ▌
    Env Vars 2 · agents-store
    Vercel environment variable expert guidance. Use when working with .env files, vercel env commands, OIDC tokens, or managing environment-specific configuration.
    0 repo stars
  40. ▌
    Bootstrap 2 · agents-store
    Project bootstrapping orchestrator for repos that depend on Vercel-linked resources (databases, auth, and managed integrations). Use when setting up or repairing a repository so linking, environment provisioning, env pulls, and first-run db/dev commands happen in the correct safe order.
    0 repo stars
  41. ▌
    Next Forge 2 · agents-store bundle
    next-forge
    0 repo stars
  42. ▌
    Marketplace 2 · agents-store
    Vercel Marketplace expert guidance — discovering, installing, and building integrations, auto-provisioned environment variables, unified billing, and the vercel integration CLI. Use when consuming third-party services, building custom integrations, or managing marketplace resources on Vercel.
    0 repo stars
  43. ▌
    Vercel Sandbox 2 · agents-store bundle
    Vercel Sandbox guidance — ephemeral Firecracker microVMs for running untrusted code safely. Supports AI agents, code generation, and experimentation. Use when executing user-generated or AI-generated code in isolation.
    0 repo stars
  44. ▌
    Vercel Storage 2 · agents-store
    Vercel storage expert guidance — Blob, Edge Config, and Marketplace storage (Neon Postgres, Upstash Redis). Use when choosing, configuring, or using data storage with Vercel applications.
    0 repo stars
  45. ▌
    Knowledge Update 2 · agents-store
    Corrects outdated LLM knowledge about the Vercel platform and introduces new products. Injected at session start.
    0 repo stars
  46. ▌
    Workflow 2 · agents-store bundle
    Creates durable, resumable workflows using Vercel's Workflow DevKit. Use when building workflows that need to survive restarts, pause for external events, retry on failure, or coordinate multi-step operations over time. Triggers on mentions of "workflow", "durable functions", "resumable", "workflow devkit", "queue", "event", "push", "subscribe", or step-based orchestration.
    0 repo stars
  47. ▌
    Vercel CLI 2 · agents-store bundle
    Deploy, manage, and develop projects on Vercel from the command line
    0 repo stars
  48. ▌
    Chat Sdk · agents-store bundle
    Vercel Chat SDK expert guidance. Use when building multi-platform chat bots — Slack, Telegram, Microsoft Teams, Discord, Google Chat, GitHub, Linear — with a single codebase. Covers the Chat class, adapters, threads, messages, cards, modals, streaming, state management, and webhook setup.
    0 repo stars
  49. ▌
    Env Vars · agents-store
    Vercel environment variable expert guidance. Use when working with .env files, vercel env commands, OIDC tokens, or managing environment-specific configuration.
    0 repo stars
  50. ▌
    Bootstrap · agents-store
    Project bootstrapping orchestrator for repos that depend on Vercel-linked resources (databases, auth, and managed integrations). Use when setting up or repairing a repository so linking, environment provisioning, env pulls, and first-run db/dev commands happen in the correct safe order.
    0 repo stars
  51. ▌
    Next Forge · agents-store bundle
    next-forge
    0 repo stars
  52. ▌
    Marketplace · agents-store
    Vercel Marketplace expert guidance — discovering, installing, and building integrations, auto-provisioned environment variables, unified billing, and the vercel integration CLI. Use when consuming third-party services, building custom integrations, or managing marketplace resources on Vercel.
    0 repo stars
  53. ▌
    Vercel Sandbox · agents-store bundle
    Vercel Sandbox guidance — ephemeral Firecracker microVMs for running untrusted code safely. Supports AI agents, code generation, and experimentation. Use when executing user-generated or AI-generated code in isolation.
    0 repo stars
  54. ▌
    Vercel Storage · agents-store
    Vercel storage expert guidance — Blob, Edge Config, and Marketplace storage (Neon Postgres, Upstash Redis). Use when choosing, configuring, or using data storage with Vercel applications.
    0 repo stars
  55. ▌
    Knowledge Update · agents-store
    Corrects outdated LLM knowledge about the Vercel platform and introduces new products. Injected at session start.
    0 repo stars
  56. ▌
    Examples 2 · agents-store bundle
    Tool call patterns, end-to-end workflow examples, and scenario references. This skill should be used when the user needs reference implementations, complete examples, or tool call patterns.
    0 repo stars
  57. ▌
    Setup 2 · agents-store
    This skill should be used when the user asks how to "connect to the Dify API", "authenticate with Dify", "get a Dify API key", "what is the Dify base URL", "blocking vs streaming in Dify", "the Dify user field", "send files to a Dify app", or needs the app metadata endpoints (/info, /parameters, /meta, /site). Foundation for every other Dify API call.
    0 repo stars
  58. ▌
    Setup 3 · agents-store
    Use when the user asks to "verify Flask project setup", "check Flask structure", "is my Flask app set up correctly", "validate Flask project", or needs to confirm that a Flask project follows recommended patterns and has correct file structure.
    0 repo stars
  59. ▌
    Examples 3 · agents-store bundle
    Tool call patterns, end-to-end workflow examples, and scenario references. This skill should be used when the user needs reference implementations, complete examples, or tool call patterns.
    0 repo stars
  60. ▌
    Setup 4 · agents-store
    This skill should be used when the user wants to "connect to Taiga", "log into Taiga", "authenticate with Taiga", "get a Taiga auth token", "set up Taiga access", or before running any Taiga REST API call. Establishes the auth token and the global request conventions (headers, pagination, version locking, the resolver).
    0 repo stars
  61. ▌
    Setup 5 · agents-store
    Use this skill when the user is preparing a development environment for Microsoft Teams app development — installing the Teams Developer CLI, verifying Node version, confirming a Teams sideloading-enabled tenant, or troubleshooting "command not found" / "teams CLI not installed" / "no Microsoft 365 dev tenant" errors before any other Teams work begins.
    0 repo stars
  62. ▌
    Setup 6 · agents-store
    This skill should be used when the user asks to "install grammY", "create a Telegram bot", "set up my first bot", "verify grammY installation", "get a bot token", "BotFather", or needs to bootstrap a brand-new grammY project from zero to a running echo bot.
    0 repo stars
  63. ▌
    Setup 7 · agents-store
    Verify Next.js project environment and readiness. This skill should be used when the user asks to "verify Next.js setup", "check Next.js project", "is my Next.js app configured correctly", "test Next.js environment", or needs to confirm their project is ready for development.
    0 repo stars
  64. ▌
    Setup 8 · agents-store
    Verify NocoDB connection for schema-development work — both transports (MCP + CLI/API). Use when: - "check NocoDB dev setup" - "verify NocoDB API access" - "is the nc CLI working?" - "can I modify schema?" - "test NocoDB MCP connection"
    0 repo stars
  65. ▌
    Setup 9 · agents-store
    Verify NocoDB connection and MCP setup. Use when: - "check my NocoDB connection" - "verify MCP is working" - "test NocoDB setup" - "is NocoDB connected?" - "troubleshoot NocoDB access"
    0 repo stars
  66. ▌
    Setup 10 · agents-store
    This skill should be used when the user asks to "set up restic backups on a server", "install restic", "prepare a Linux server for backups", "check what arch/init system my server uses", or needs to recon a server (architecture, OS, init system, timezone, free disk) and install the correct latest restic binary before configuring backups.
    0 repo stars
  67. ▌
    Examples 4 · agents-store
    Complete SEO recipes and implementation examples for Next.js App Router. This skill should be used when the user asks for "SEO example", "blog SEO setup", "e-commerce SEO", "landing page SEO", "SaaS SEO", "full SEO implementation", "SEO recipe", "SEO template", or needs a complete, copy-paste ready SEO implementation for a specific page type.
    0 repo stars
  68. ▌
    Examples 5 · agents-store bundle
    This skill should be used when the user asks for a "full Dify example", "end-to-end Dify integration", "how do I build a chatbot with Dify", "complete workflow example", "Dify RAG example", or wants a working, copy-paste walkthrough that strings multiple Dify API calls together.
    0 repo stars
  69. ▌
    Examples 6 · agents-store bundle
    End-to-end scenario walkthroughs for updating self-hosted Dify. Use when the user asks for "dify update example", "how to update dify", "show me an update walkthrough", "dify upgrade guide", "step-by-step dify update", or needs a complete example of the update process.
    0 repo stars
  70. ▌
    Setup 11 · agents-store
    This skill should be used when verifying Dokploy MCP connection, CLI installation, and API access. Use when user says "set up dokploy", "verify dokploy connection", "check dokploy", "test dokploy access", or enables the dokploy-dev plugin for the first time.
    0 repo stars
  71. ▌
    Examples 7 · agents-store bundle
    Application design scenarios and reference implementations. This skill should be used when the user needs complete application examples, tool call patterns, or end-to-end workflow references.
    0 repo stars
  72. ▌
    Setup 12 · agents-store
    This skill should be used when the user wants to "connect to Outline", "authenticate with Outline", "set up Outline access", "use my Outline API key", or before running any Outline REST API call. Establishes the API key + base URL from the environment and the global request conventions (RPC POST style, Bearer header, response envelope, limit/offset pagination, sorting, rate limits, policies).
    0 repo stars
  73. ▌
    Examples 8 · agents-store bundle
    MCP tool call patterns, end-to-end workflow examples, code templates, and scenario references. Use when you need reference implementations for Teleshop operations.
    0 repo stars
  74. ▌
    Setup 13 · agents-store bundle
    Set up Trigger.dev in a project, connect to a self-hosted instance, verify MCP connection, authenticate the CLI, or configure dev/staging/production environments. Use when the user asks to "set up trigger.dev", "init trigger project", "connect to self-hosted trigger", "verify trigger connection", "install trigger.dev", or "configure trigger environments".
    0 repo stars
  75. ▌
    Setup 14 · agents-store
    This skill should be used when the user asks to "set up Chatwoot API", "get a Chatwoot access token", "configure CHATWOOT_API_KEY", "install the Chatwoot CLI", "connect to Chatwoot", "verify Chatwoot is working", or needs to obtain credentials and confirm REST API / CLI access to a Chatwoot account (cloud or self-hosted).
    0 repo stars
  76. ▌
    Examples 9 · agents-store bundle
    Tool call patterns, end-to-end workflow examples, and scenario references. This skill should be used when the user needs reference implementations, complete examples, or tool call patterns.
    0 repo stars
  77. ▌
    Setup 15 · agents-store
    This skill should be used when the user asks "what is macstack.json", "set up macstack", "check macstack setup", "verify macstack.json", "explain the macstack standard", or before any other macstack-dev skill runs in a project for the first time. Explains the standard, locates the schema and category registry, and verifies tooling.
    0 repo stars
  78. ▌
    Examples 10 · agents-store bundle
    Tool call patterns, end-to-end workflow examples, and scenario references for Plane Agile workflows. Use when needing reference implementations, complete examples, or tool call patterns.
    0 repo stars
  79. ▌
    Examples 11 · agents-store bundle
    MCP tool call patterns, multi-channel marketing workflow examples, and scenario references. Use when you need reference implementations for Sendpulse operations.
    0 repo stars
  80. ▌
    Examples 12 · agents-store bundle
    This skill should be used when the user wants a worked end-to-end Taiga example or walkthrough — "show me a full Taiga workflow", "example of setting up a project in Taiga", "how do I run sprint planning via the API", "end-to-end bug triage example", or wants to see several Taiga API calls chained together for a real scenario.
    0 repo stars
  81. ▌
    Examples 13 · agents-store bundle
    Use this skill when the user wants a worked, end-to-end scenario for a Microsoft Teams app — a full walkthrough for an echo bot, an AI quote agent, an Adaptive Card form, a message-extension search command, or an SSO + Microsoft Graph bot. Triggers on "Teams bot example", "full example Teams", "end-to-end Teams scenario", "echo bot example", "Teams SSO example".
    0 repo stars
  82. ▌
    Setup 16 · agents-store
    This skill should be used when the user wants to "connect to Jira", "connect to Confluence", "authenticate with Atlassian", "set up Jira/Confluence access", "use my Atlassian API token", or before running any Jira or Confluence REST API call. Establishes Atlassian Cloud Basic auth (email + API token) and the global conventions both APIs share (base paths, headers, Jira startAt/maxResults vs Confluence cursor pagination, ADF/storage body formats, accountId).
    0 repo stars
  83. ▌
    Examples 14 · agents-store bundle
    This skill should be used when the user asks "show me a complete grammY example", "give me a full grammY bot file", "example of a Telegram bot with menu", "complete echo bot in grammY", "example session counter", "example webhook bot Cloudflare Workers", "example conversation form bot", or wants end-to-end scenario walkthroughs rather than isolated snippets.
    0 repo stars
  84. ▌
    Setup 17 · agents-store
    This skill should be used when the user asks to "install Infisical CLI", "set up Infisical CLI", "log in to Infisical", "authenticate Infisical CLI", "verify Infisical is working", "is Infisical CLI working", "point Infisical at self-hosted", or needs to get the Infisical CLI installed, authenticated, and confirmed operational.
    0 repo stars
  85. ▌
    Examples 15 · agents-store bundle
    This skill should be used when looking for complete workflow examples, step-by-step setup guides, architecture diagrams, or command references. Relevant for queries like "how do I set up multi-bank", "show me an example of the budget alert flow", "walk me through generating a report", or "show first-time setup guide". Use this skill whenever the user asks "how do I...", wants a walkthrough, needs a step-by-step guide, or is setting up the plugin for the first time.
    0 repo stars
  86. ▌
    Examples 16 · agents-store bundle
    Next.js development scenario walkthroughs and code patterns. This skill should be used when the user asks for "Next.js examples", "Next.js project walkthrough", "how to build a dashboard in Next.js", "Next.js e-commerce example", "Next.js code patterns", or needs end-to-end implementation guidance for common Next.js application types.
    0 repo stars
  87. ▌
    Examples 17 · agents-store bundle
    End-to-end NocoDB schema-development walkthroughs. Use when: - "show me a schema example" - "how do I build a CRM in NocoDB?" - "e-commerce schema example" - "schema design walkthrough" - "NocoDB dev scenarios"
    0 repo stars
  88. ▌
    Examples 18 · agents-store bundle
    NocoDB workflow examples, scenario walkthroughs, and practical patterns. Use when: - "show me a NocoDB example" - "workflow examples" - "scenario walkthroughs" - "how do I use NocoDB for..." - "NocoDB use case"
    0 repo stars
  89. ▌
    Examples 19 · agents-store bundle
    This skill should be used when the user asks for a "restic backup example", "end-to-end restic R2 walkthrough", "Docker server backup tutorial", "restic disaster recovery example", "how would this work on my server", or wants a complete scenario walkthrough.
    0 repo stars
  90. ▌
    Setup 18 · agents-store
    This skill should be used when the user asks to "verify DataForSEO connection", "check DataForSEO MCP", "test DataForSEO setup", "is DataForSEO working", or needs to confirm that the DataForSEO MCP integration is operational.
    0 repo stars
  91. ▌
    Examples 20 · agents-store bundle
    This skill should be used when learning how to deploy apps, provision databases, set up Docker Compose stacks, or debug a failed deployment on Dokploy. Provides end-to-end workflow walkthroughs. Triggers: "dokploy example", "how to deploy on dokploy", "dokploy tutorial", "dokploy walkthrough", "show me how to use dokploy", "dokploy debug example".
    0 repo stars
  92. ▌
    Setup 19 · agents-store
    This skill should be used when the user wants to "connect to Mattermost", "log into Mattermost", "authenticate with Mattermost", "get a Mattermost token", "set up Mattermost access", or before running any Mattermost REST API call. Establishes the session token (read from the login Token response header) and the global request conventions (base path, headers, pagination, rate limits).
    0 repo stars
  93. ▌
    Workflows 2 · agents-store
    List, execute, and inspect NocoDB Workflows (the platform's built-in automation engine) via Meta API v3. Use when: - "list NocoDB workflows" - "execute a workflow" - "view workflow execution" - "trigger workflow on demand" - "fetch execution results"
    0 repo stars
  94. ▌
    Examples 21 · agents-store bundle
    This skill should be used when the user wants a worked end-to-end Outline example or walkthrough — "show me a full Outline workflow", "example of building a knowledge base in Outline", "how do I publish and share a doc via the API", "document lifecycle example", "onboard users to Outline", or wants to see several Outline API calls chained together for a real scenario.
    0 repo stars
  95. ▌
    Setup 20 · agents-store
    This skill should be used when the user asks to "install PayloadCMS", "create a Payload project", "set up Payload v3", "scaffold Payload app", "initialize Payload with Next.js", "pick a Payload database adapter", "configure payload.config.ts", or needs to bootstrap a fresh Payload project from zero to a running admin panel.
    0 repo stars
  96. ▌
    Setup 21 · agents-store
    Use when the user asks to "verify SQLAlchemy setup", "check database connection", "is SQLAlchemy configured correctly", "test database setup", or needs to confirm that SQLAlchemy is properly initialized in their Python project.
    0 repo stars
  97. ▌
    Examples 22 · agents-store bundle
    Trigger.dev code examples, end-to-end workflow templates, MCP tool usage patterns, and scenario walkthroughs. Use when the user asks for "trigger.dev examples", "task templates", "MCP tool patterns", "trigger.dev workflow examples", or needs reference implementations.
    0 repo stars
  98. ▌
    Setup 22 · agents-store bundle
    This skill should be used when the user asks to "verify web search setup", "check search services", "test firecrawl connection", "test exa connection", "is jina working", "check perplexity MCP", or needs to confirm which web search and scraping services are operational.
    0 repo stars
  99. ▌
    Examples 23 · agents-store bundle
    This skill should be used when the user wants a worked, end-to-end Chatwoot example — "show me a full Chatwoot integration", "seed a conversation via the API", "build a Chatwoot bot example", "bulk import contacts", or "triage Chatwoot from the terminal" — combining setup, the REST API, the CLI, and webhooks into a complete scenario.
    0 repo stars
  100. ▌
    Troubleshoot 2 · agents-store
    This skill should be used when a Dify API call fails or behaves unexpectedly — "Dify 401 / 404 / 429 error", "Dify conversation not found", "Dify blocking timeout", "Dify rate limit", "why is my Dify conversation empty", "Dify user mismatch", or "Dify file upload not working". Error codes, limits, and common pitfalls.
    0 repo stars