agentleFS
Sign inStart free
drafthqdrafthq/draft/skills/integrations/SKILL.md

integrations

Skill40 starsChanged 4 months agoMITView on GitHub

Canonical integrations parent command. Handles external system exports and syncs. Routes intent to jira-preview or jira-create based on context.

15 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use payments.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • OpenAISkill

    payments

    Stripe payments integration guidance — native Vercel Marketplace setup, checkout sessions, webhook handling, subscription billing, and the Stripe SDK. Use when implementing payments, subscriptions, or processing transactions.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 15 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the user explicitly invokes a specialist mode, route directly:

    line 23
  2. Distinctive:

    If no explicit mode is specified, infer the intent from the user's prompt:

    line 30
  3. Very specific:

    If the user runs a bare /draft:integrations without clear intent, present a small integrations menu with a recommended default path:

    line 39
  4. Distinctive:

    Do not automatically launch a specialist workflow without explicit or clear inferred intent.

    line 49

“Common” is measured: kept by at least 6 in 10 of the 15 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Integrations Workflows

/draft:integrations is the canonical integrations parent command.

It handles connectors and exports to external systems like Jira.

Specialist integration workflows remain available as named modes:

  • /draft:jira preview (or /draft:integrations jira-preview)
  • /draft:jira create (or /draft:integrations jira-create)

Step 1: Parse Intent and Route

Examine the user's input and route to the correct integrations workflow.

Explicit Named Modes

If the user explicitly invokes a specialist mode, route directly:

  • /draft:integrations jira-preview → follow /draft:jira preview
  • /draft:integrations jira-create → follow /draft:jira create

Intent Routing

If no explicit mode is specified, infer the intent from the user's prompt:

IntentActionRoute
"Export to Jira", "Preview Jira issues", "Show me what you'll create in Jira"Jira Preview/draft:jira preview
"Create Jira issues", "Sync to Jira", "Make tickets"Jira Create/draft:jira create

Step 2: Bare Parent Command Fallback

If the user runs a bare /draft:integrations without clear intent, present a small integrations menu with a recommended default path:

Draft Integrations Menu:
1. /draft:integrations jira-preview (Generate Jira export file for review)
2. /draft:integrations jira-create (Create Jira issues from export)

What integration action do you want to perform?

Do not automatically launch a specialist workflow without explicit or clear inferred intent.

Compatibility Note

The legacy specialist commands remain supported during the migration period, but /draft:integrations is the canonical parent for integration tasks.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free