agentleFS
Sign inStart free
extra-orgextra-org/extra/.claude/skills/sidecar-auth-context/SKILL.md

sidecar-auth-context

Skill119 starsChanged 5 months agoMITView on GitHub

Working on resolver plugins, the fixed access plugin contract, mapping resolver outputs into ExecutionContext, or protected-node filtering. Primary task is tasks/0006-sidecar-auth-context.md.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Do not edit this file directly.

    line 10
  2. Very specific:

    Use this when working on resolver plugins, the fixed access plugin contract, mapping resolver outputs into ExecutionContext, or …

    line 18
  3. Very specific:

    Call resolver plugin methods declared in top-level resolvers.

    line 42
  4. Very specific:

    If any node has protected: true, require plugins/access.py with AccessResolver.can_access(ctx, node_id) -> bool.

    line 43
  5. Very specific:

    Keep plugin instances shared where appropriate.

    line 45

≈ “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
<!-- This file is generated by tools/skills. Do not edit this file directly. Edit .ai/skills/sidecar-auth-context.md and run `make generate-ai`. -->

Skill: Plugin Context & Access

When to use this skill

Use this when working on resolver plugins, the fixed access plugin contract, mapping resolver outputs into ExecutionContext, or protected-node filtering. Primary task: tasks/0006-sidecar-auth-context.md.

Files to read first

  • AGENTS.md
  • docs/SIDECAR_CONTEXT_AUTH.md
  • docs/ARCHITECTURE.md
  • docs/PROMPT_RENDERING.md

Architecture rules

  • The runtime contains no customer-specific auth/business logic.
  • Resolver plugins fill prompt variables before a node runs.
  • Tool plugins are separate and run during LLM execution.
  • Protected nodes are hidden from routers unless the access plugin allows them.
  • Access failures fail closed.
  • Secrets are redacted in traces.

Implementation rules

  • Implement plugin integration in src/agentplatform/context.
  • Build ctx from request headers and request data.
  • Call resolver plugin methods declared in top-level resolvers.
  • If any node has protected: true, require plugins/access.py with AccessResolver.can_access(ctx, node_id) -> bool.
  • Keep plugin instances shared where appropriate; keep request data on ExecutionContext.

Validation checklist

  • No customer-specific logic in the runtime.
  • Resolver outputs are request-scoped.
  • Protected nodes are filtered before routing.
  • Deny/error cases fail closed and are traced.
  • Secrets redacted in traces.
  • Tests use fake plugins covering allow/deny/error.
  • make check passes.

Common mistakes to avoid

  • Implementing auth/tenant/business rules inside the engine.
  • Failing open when access plugin raises.
  • Exposing resolver plugins to the LLM as tools.
  • Logging raw tokens/secrets in the trace.

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