Decision topic

Connect tools or automate recurring work

Choose between MCP/API building, SaaS workspace actions, recurring reports, and scheduled agent workflows.

Last meaningful review July 21, 2026

Start here

You need an agent workflow to connect systems or run repeatedly, while keeping credentials, approvals, and failure handling explicit.

This topic coversMCP servers · API integrations · workspace actions · scheduled reports · recurring workflows

Not this topicunapproved high-risk actions · credential sharing · enterprise ETL as a side effect

Choose your scene

Pick the closest situation, not the perfect one.

Each scene hides the noisy marketplace ranking behind one practical recommendation, one optional alternative, and one fallback when a public skill is not the right intervention.

I need to build an MCP server or API integration.

I want the agent to connect an external service through tools or MCP.

Decision moment

Choose developer integration workflows, not no-code reporting.

Not this

If you only need a business report, use recurring report.

Recommended skillSource

mcp-builder

It is the clearest official workflow for building MCP servers.

Use when: Use it for new MCP tools over external APIs.
Avoid when: Avoid it for ordinary document or content automation.
Signal: Official Anthropic skill source; SkillsMP indexed candidate.

Recommended skillSource

mcp-integration

It is useful when integrating with ChatGPT app or OpenAI skill surfaces.

Use when: Use it when the host platform is OpenAI-oriented.
Avoid when: Avoid it for Anthropic-only plugin packaging.
Signal: OpenAI curated source contains app/MCP adjacent guidance.

Build

Project integration spec

Write a small integration spec before coding.

Use when: Use it for production integrations.
Avoid when: Do not let a skill invent API contracts.
Signal: Auth, rate limits, and deployment are service-specific.

I need actions inside Lark, Google Workspace, Notion, Slack, or similar tools.

I want the agent to read, write, summarize, or update records in a workplace app.

Decision moment

Choose app-specific skills only when the target system is known.

Not this

If the task is just drafting text, use writing content.

Recommended skillSource

lark-doc / lark-sheets / lark-minutes

The high install counts indicate strong supply for Lark/Feishu app-specific actions.

Use when: Use it when your work system is Lark/Feishu.
Avoid when: Avoid it outside that ecosystem.
Signal: skills.sh all-time: Lark skills frequently exceed 400,000 installs in open.feishu.cn source.

Recommended skillSource

google-workspace skills

It is the right family when the target is Gmail, Slides, Meet, or related Google tools.

Use when: Use it for Google Workspace operations.
Avoid when: Avoid it for generic automation without Google credentials.
Signal: skills.sh all-time: Google Workspace CLI skills are marked official and include Slides, Gmail, Meet, Forms.

No skill

Permission and auth check

Confirm OAuth, scopes, and human approval before actions.

Use when: Use it for customer or internal systems.
Avoid when: Do not perform irreversible actions without review.
Signal: Workspace actions require account permissions.

I need a recurring report across tools or sites.

I want data collected repeatedly and sent as a dashboard, brief, or notification.

Decision moment

Choose reporting plus scheduling, not a one-time research skill.

Not this

If there is only one source app, use that app-specific skill.

Recommended skillSource

firecrawl-dashboard-reporting

It directly maps to recurring dashboard/report style outputs from web sources.

Use when: Use it for repeatable public web or dashboard reports.
Avoid when: Avoid it for private SaaS data without connectors.
Signal: skills.sh all-time: 29,267 installs; official Firecrawl workflow source.

Recommended skillSource

business-pulse

It fits small-business multi-connector briefs.

Use when: Use it when its documented connectors match your tools.
Avoid when: Avoid it for arbitrary ETL.
Signal: SkillsMP indexed source from Anthropic knowledge-work plugins.

Build

Workflow automation job

Build or configure workflow infrastructure when reliability matters.

Use when: Use it for production recurring reports.
Avoid when: Do not hide missing monitoring behind a skill recommendation.
Signal: Scheduling, retries, secrets, and alerting are operational features.

I already have an agent workflow and need it to run on a schedule.

The workflow exists; I need cron, state, logs, retries, and alerts.

Decision moment

Choose scheduling/ops instead of re-designing the business workflow.

Not this

If the workflow itself is undefined, define it first.

Recommended skillSource

agents-sdk

It is a high-install agent runtime/scheduling-adjacent source.

Use when: Use it when your runtime supports it and you need agent job structure.
Avoid when: Avoid it for simple one-off tasks.
Signal: skills.sh all-time: 185,000 installs.

Recommended skillSource

cloudflare-deploy

It is relevant when scheduled work is deployed on Cloudflare infrastructure.

Use when: Use it for Cloudflare Workers deployment flows.
Avoid when: Avoid it outside Cloudflare.
Signal: OpenAI curated skill source.

Build

Scheduler wrapper

Add logs, retries, state, and alerting around the workflow.

Use when: Use it for any unattended run.
Avoid when: Do not allow irreversible scheduled actions without approvals.
Signal: Durable scheduling is infrastructure, not just instructions.

Why this topic exists

skills.sh shows high-install Lark/Feishu, Azure, Google Workspace, MCP, and Firecrawl workflow skills; SkillsMP also indexes many connector and MCP variants.

skills.sh: open.feishu.cn and larksuite/cli skills appear heavily in the all-time leaderboard.
skills.sh: mcp-builder from Anthropic has strong source presence via official repository.
SkillsMP positions MCP/API integration as a dense but noisy category.

Still unsure?

Describe the job in your own words.

Request a topic or scene ↗