Aiprox Workflows

Create and run multi-agent AI workflows on AIProx. Chain agents into scheduled pipelines. Pay per execution in sats.

Security Scan

The skill's requirements and runtime instructions are coherent with a pay-per-run multi-agent workflow service; the single requested environment variable (AIPROX_SPEND_TOKEN) aligns with the claimed billing model, but you should be aware of financial risk from autonomous runs and the external service dependencies.

Purpose & Capability

The name/description (multi-agent workflow engine with per-run payments) matches the manifest and SKILL.md: it requires a spend token and documents workflow creation, running, scheduling, templates, and agent capabilities. The listed capabilities (search, scraping, sentiment, email, market data, token-analysis, code-audit, etc.) are consistent with a pipeline/orchestration product that delegates work to specialized agents.

Instruction Scope

SKILL.md contains explicit instructions for creating/running/listing/deleting workflows, scheduling, and cost reporting. It instructs the operator to place AIPROX_SPEND_TOKEN in the MCP server config and to use npx/aiprox-workflows-mcp for the MCP adapter. It does not instruct the agent to read unrelated files or arbitrary environment variables, nor to exfiltrate data to unexpected endpoints beyond email/webhook outputs described in the doc.

Install Mechanism

This is an instruction-only skill (no install spec or code shipped). The docs reference an npm package and an MCP adapter command (npx aiprox-workflows-mcp / npm install aiprox-workflows) but provide no automated installer in the manifest — this is consistent but means installing the adapter is a manual step the user must perform from external registries.

Credentials

Only AIPROX_SPEND_TOKEN is required, which is proportionate to a billed workflow service. This token is a financial credential (spend token) and should be treated as highly sensitive; the skill doesn't request unrelated tokens or system credentials.

Persistence & Privilege

always:false (not force-installed). The platform-default ability for the agent to invoke the skill autonomously remains enabled — combined with a spend token this creates a real financial risk (the agent could trigger paid runs). The manifest does not request other privileged system access or modify other skills' config.

Assessment

This skill is coherent with its stated purpose, but before installing consider: (1) Treat AIPROX_SPEND_TOKEN as a sensitive spend-only credential; ask whether the token can be scoped/limited and whether revocation is easy. (2) Confirm whether the agent will run workflows autonomously by default and what user consent/confirmation is required before each paid run — if you want to avoid unexpected charges, disable autonomous invocation or require explicit approval. (3) Verify the external domains mentioned (aiprox.dev, lightningprox.com) and the npm package (aiprox-workflows) before installing any adapter. (4) Start by creating/running a single test workflow and monitor run_history and sats_spent; set strict budget caps if the service supports them. (5) If you need stronger guarantees, ask the provider how emails/webhooks are sent/stored and whether sensitive data processed in workflows is retained or accessible to third parties.

AIProx Workflows is a multi-agent pipeline engine. Chain AI agents into named workflows, schedule them to run on a cron, and get results delivered by email or webhook. Pay per execution in sats — no subscriptions, no monthly fees.

When to Use

• Building automated pipelines that chain multiple AI agents
• Scheduling recurring tasks (daily news digest, competitive intel, market signals)
• Running one-off multi-step pipelines on demand
• Any workflow where one agent's output feeds into the next

MCP Tools

create_workflow

Create a named pipeline with ordered agent steps.

Create a workflow "daily-crypto-brief" that searches Bitcoin news, analyzes sentiment, and emails a summary @daily

Step chaining: use $step1.result, $step2.result, etc. to pass outputs forward.

Available capabilities:

Capability	What it does
web-search	Real-time web search via search-bot
sentiment-analysis	Sentiment and tone analysis via sentiment-bot
scraping	Web scraping and article extraction via data-spider
data-analysis	Data processing and text analysis via doc-miner
translation	Multilingual translation via polyglot
vision	Image/screenshot analysis via vision-bot
code-execution	Code audit and security review via code-auditor
email	Send email notifications via email-bot
market-data	Prediction market signals via market-oracle
token-analysis	Solana token safety and rug detection via isitarug

run_workflow

Trigger any workflow by its ID.

Run workflow wf_abc123

list_workflows

Show all workflows for the current spend token.

List my workflows

get_run_history

Show past execution results, sats spent, and step-by-step output.

Show run history for wf_abc123

delete_workflow

Delete a workflow (cancels scheduled runs).

run_template

Run a pre-built template by name in one shot.

Run the polymarket-signals template and email me at [e-mail]

Pre-Built Templates

Template name	Pipeline	Cost
news-digest	search-bot → sentiment-bot → email-bot	~150 sats/run
token-scanner	data-spider → isitarug → email-bot	~120 sats/run
competitive-intel	search-bot → doc-miner → sentiment-bot → email-bot	~200 sats/run
multilingual-content	data-spider → doc-miner → polyglot	~180 sats/run
site-audit	vision-bot → code-auditor → doc-miner	~220 sats/run
polymarket-signals	market-oracle → sentiment-bot → email-bot	~160 sats/run

Authentication

Set AIPROX_SPEND_TOKEN in your MCP server config. Get a spend token at lightningprox.com.

{
  "mcpServers": {
    "aiprox-workflows": {
      "command": "npx",
      "args": ["aiprox-workflows-mcp"],
      "env": {
        "AIPROX_SPEND_TOKEN": "lnpx_your_token_here"
      }
    }
  }
}

Scheduling

Shorthand	When
@hourly	Every hour
@daily	Every day at midnight
@weekly	Every Sunday
0 9 * * 1-5	9am Monday–Friday

Pricing

50–220 sats per workflow execution depending on agents used. No monthly plan. Deducted from your Lightning spend token balance.

Behavior Guidelines

When a user asks to automate something:

1. Identify which capabilities are needed (search → analyze → notify is the common pattern)
2. Suggest a template if one matches, otherwise offer to create a custom workflow
3. Confirm the schedule and email/webhook if they want recurring runs
4. After creating, offer to run it immediately

Cost transparency:

• Mention estimated sats cost before creating/running
• Report sats_spent after each run

Check templates first: If the task matches a template, use run_template — it's faster and pre-configured.

Links

• Dashboard: aiprox.dev/workflows
• Templates: aiprox.dev/templates
• Registry: aiprox.dev/registry.html
• npm SDK: npm install aiprox-workflows
• MCP server: npx aiprox-workflows-mcp