agentleFS
zedarvateszedarvates/frugal-skills/skills/webhooks/SKILL.md

webhooks

Skill1 starsChanged 30 days agoMITView on GitHub

Instructions for the upstream workflow: Minimal HTTP endpoint that exposes the router to no-code workflows — a POST route that takes a prompt and a task type and returns the routing decision as JSON, on a configurable port. Use to let an external workflow system (n8n and similar) call the router without importing Python. Boundary: the listener binds all interfaces and performs no authentication, so it must stay on a trusted local network and is not a public entry point. Not for the routing decision itself — use auto-router; not for a general HTTP surface — see the module registration pattern in code-rules.

15 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use data-pipelines, incident-response and 1 more.

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.
  • YepAPISkill

    data-pipelines

    ETL patterns, cron scheduling, queue-based processing, and batch jobs with Inngest/BullMQ.

    Also in 3 projects that use this

  • AnthropicSkill

    incident-response

    Run an incident response workflow — triage, communicate, and write postmortem. Trigger with "we have an incident", "production is down", an alert that needs severity assessment, a status update mid-incident, or when writing a blameless postmortem after resolution.

    Also in 3 projects that use this

  • OpenAISkill

    observability

    Vercel Observability expert guidance — Drains (logs, traces, speed insights, web analytics), Web Analytics, Speed Insights, runtime logs, custom events, OpenTelemetry integration, and monitoring dashboards. Use when instrumenting, debugging, or optimizing application performance and user experience on Vercel.

    Also in 3 projects that use this

The file

Files
SKILL.md

webhooks — expose the router to no-code workflows

Package scope and prerequisites

This catalog ships instructions, not the executable runtime. Python modules, scripts, local services and optional tools named below must be installed separately from the upstream project. Check their availability before running commands; if they are missing, explain the prerequisite instead of claiming execution or results. The host agent may use model tokens while following these instructions.

Purpose

A single endpoint so a workflow tool can ask for a routing decision.

python -m skills.webhooks.n8n_endpoint --port 8769
POST /auto_route   {"prompt": "...", "task_type": "..."}

Declared boundary

  • Binds 0.0.0.0 by default and has no authentication. Do not expose it beyond a trusted local network; prefer an explicit loopback binding when only the local machine needs it.
  • It is a thin adapter: all logic stays in auto_router.

When NOT to use

  • You are inside Python already — call auto_router directly.
  • You need a public or authenticated API — this is not one.

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.