agentleFS
Sign inStart free
vpeetla-aivpeetla-ai/react-agent-pattern/.cursor/skills/aegis-gateway/SKILL.md

aegis-gateway

Skill2 starsChanged 4 months agoMITView on GitHub

Integrate AegisAI gateway before tool side effects (notify, publish, deploy). Use when adding Slack/Telegram/WhatsApp notify, content publish, or any irreversible external action in VAP, AegisLoop, or ai-content-factory.

  • Reads credentials
  • Commits and pushes

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If gateway URL unset → fail open with logged warning (local dev only)

    line 42
  2. Distinctive:

    Never fail open in production configs

    line 43

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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

AegisAI Gateway Integration

When required

Any side effect leaving the system:

  • Publish to LinkedIn/X/Substack
  • Send Slack/Telegram/WhatsApp messages
  • Deploy or git push to protected branches (prefer PR workflow)

Pattern

# integrations/aegis_gateway.py (existing in VAP, AegisLoop, Content Factory)
result = await gateway.request_tool(
    tool_name="notify_slack",
    payload={...},
    agent_id="...",
    run_id="...",
)
if result.requires_hitl:
    # pause until approval

Env vars

AEGISAI_API_BASE_URL=https://...
AEGISAI_API_KEY=...

Dev mode

  • If gateway URL unset → fail open with logged warning (local dev only)
  • Never fail open in production configs

Do not

  • Embed policy logic in orchestrator prompts — policy lives in AegisAI/OPA
  • Bypass gateway "temporarily" in production code paths

Reference

aegisai-enterprise-agent-platform — gateway SDK + POST /api/gateway/tool-request

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