agentsclimarketplace

Super automation

Skill arpitexplores/super-automation

Portable Markdown skill for AI vibe coding with automation: SaaS workflows, API integrations, triggers, permissions, retries, monitoring, and GitHub automation.

Install
npx -y skills add arpitexplores/super-automation

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Workflow and app automations across SaaS tools, APIs, and integrations.

SKILL.md

1.6 KB, 327 tokens by cl100k_base, as published. Nobody here has run it

Super Automation

Overview

Design reliable automations with clear triggers, data flow, and monitoring.

User Intent Examples

  • "Need help with GitHub Automation for my product/site."
  • "Create a plan for Workflow Automation."
  • "Not sure where to start, need a quick assessment."

Workflow

  1. Define the goal, trigger, and success criteria.
  2. Map required systems and permissions.
  3. Design workflow steps and error handling.
  4. Implement integrations and test with sample data.
  5. Add monitoring, alerts, and audit logs.
  6. Document ownership and maintenance steps.

Minimal Intake Questions

  • Primary goal or outcome
  • Scope (pages, systems, teams, or timeframe)
  • Constraints (tools, budget, timeline)

Output Format

  • Workflow diagram and trigger spec
  • Integration and permissions checklist
  • Error handling and retry strategy
  • Test results and validation steps
  • Monitoring and maintenance plan

Routing Map (Modules)

  • GitHub Automation -> references/modules/github-automation.md
  • Workflow Automation -> references/modules/workflow-automation.md

Bundled References

  • references/modules/
  • scripts/
  • assets/
  • agents/

Compatibility Notes

  • If any module references slash commands or tool-specific paths, translate them into plain-language steps.
  • Keep outputs platform-agnostic unless the user specifies a specific tool, stack, or agent.

Guardrails

  • Do not store secrets in plain text.
  • Use idempotent actions where possible.
  • Log failures with enough context to debug.

What ships with it: 12 files

2018.4 KB alongside SKILL.md

agents/

examples/

Gives 0 of the 12 instructions most automation workflows skills give in 327 tokens

Counted across 745 of the 1,008 authors here whose files we hold, read 2026-08-07

  • Write conventional commit messagesin 36 of 745, across 35 files
  • Delete branches after mergein 30 of 745, across 21 files
  • Make atomic commitsin 25 of 745, across 15 files
  • Write minimal code to pass testsin 22 of 745, across 10 files
  • Re-snapshot after navigation or DOM changesin 21 of 745, across 13 files
  • Use try-catch for error handlingin 20 of 745, across 8 files
  • Run tests before committingin 20 of 745, across 12 files
  • Write tests before implementationin 20 of 745, across 8 files
  • Configure branch protection rulesin 19 of 745, across 5 files
  • Explain the why in commit messagesin 19 of 745, across 9 files
  • Refactor code while tests remain greenin 19 of 745, across 6 files
  • Interact with elements using refsin 19 of 745, across 11 files

Said here and by no other author read

  • Define the goal, trigger, and success criteria
  • Map required systems and permissions
  • Design workflow steps and error handling
  • Implement integrations and test with sample data
  • Add monitoring, alerts, and audit logs
  • Document ownership and maintenance steps

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 327,069. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.