agentleFS
Sign inStart free
getsequencegetsequence/skills/sequence/SKILL.md

sequence

Skill0 starsChanged 3 months agoMITView on GitHub

Help a user choose and use the right Sequence skill for financial workflows, product integrations, accounts, cards, rules, simulations, and dashboard handoffs. Use when the user asks how to use Sequence, wants to connect a product to Sequence, or describes a Sequence outcome without naming a specific workflow.

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 3

    1. spmtitsolution/OpenBA-Kit★ 38same name
    2. GTMify/aigtm★ 25same name
    3. gr219/OpenBA-Kit★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository4 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    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:

    Use this skill as the entry point for Sequence requests.

    line 26
  2. Very specific:

    Before a workflow begins, check its SKILL.md for:

    line 44
  3. Distinctive:

    Do not invent a workflow that the repository does not contain.

    line 53
  4. Distinctive:

    Never create a real transfer as a shortcut or fallback.

    line 63
  5. Distinctive:

    Never present a dashboard-only action as completed by the MCP.

    line 64
  6. Distinctive:

    After routing, the selected workflow owns the interaction.

    line 69

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Sequence

Use this skill as the entry point for Sequence requests. Route the user to the most specific available workflow, then load only that workflow's instructions and references.

Route by intent

  • GHL or GoHighLevel wallet setup → use ghl-setup.
  • A named skill → use that skill directly after checking its requirements.
  • A new product integration → explain what is currently supported and ask for the product outcome before proposing a workflow.
  • A question about what Sequence can automate → describe the available skill and integration metadata, then distinguish MCP actions from dashboard-only actions.
  • An ambiguous financial request → ask which account, product, or outcome the user means before choosing a workflow.

Common requirements

Before a workflow begins, check its SKILL.md for:

  • Required MCP, CLI, browser, or connector access
  • Authentication and permission requirements
  • External product accounts
  • Simulation or dry-run support
  • Human approval gates
  • Actions the workflow explicitly forbids

Do not invent a workflow that the repository does not contain. Tell the user when a requested integration is not available yet.

Safety boundary

Sequence workflows may involve financial accounts, cards, and automation rules. Keep consequential actions under explicit human control:

  • Preserve simulation-first behavior.
  • Preserve paused-rule behavior.
  • Never create a real transfer as a shortcut or fallback.
  • Never present a dashboard-only action as completed by the MCP.
  • Confirm ambiguous accounts, beneficiaries, amounts, and activation choices.

Final response

After routing, the selected workflow owns the interaction. Do not repeat its full instructions or expose internal identifiers that the selected workflow keeps hidden from the user.

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