access-control

Enforce Telegram allowlists, Bearer token authentication, and device pairing for Julia's gateway.

Updated Feb 21, 2026
One-click install
npx skills add https://github.com/abzhaw/juliaz_agents --skill access-control-abzhaw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: access-control
Source: https://github.com/abzhaw/juliaz_agents/tree/main/.agent/skills/access-control
Command: npx skills add https://github.com/abzhaw/juliaz_agents --skill access-control-abzhaw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides robust access control for Julia's communication channels, preventing unauthorized messages and ensuring that only trusted chat IDs and authenticated clients can interact with the gateway.

Core Features & Use Cases

  • Telegram allowlist enforcement for chat IDs to block unknown users from the bridge
  • API Bearer Token authentication to protect REST endpoints
  • OpenClaw pairing security and device-based access control for paired clients
  • Bridge-origin verification to limit requests to trusted origins

Quick Start

Configure the allowlist and API secret in your environment, then enable the access-control patterns in your deployment to secure messaging endpoints.

Frequently Asked Questions about access-control

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I restrict Telegram bot access to authorized chat IDs only?

You can restrict Telegram bot access by enforcing a chat ID allowlist to block unknown users from interacting with the gateway. This ensures only trusted chat IDs are permitted to send messages through the bridge.

What is the best way to secure REST API endpoints with Bearer token authentication?

Securing REST API endpoints involves validating API secrets at runtime to protect REST endpoints using Bearer token authentication. This ensures only authenticated clients with valid tokens can access the gateway.

How does device pairing work for multi-user gateway deployments?

Device pairing for multi-user deployments implements a workflow where only paired clients receive access control permissions. This secures OpenClaw devices by verifying paired clients before allowing gateway interaction.

Can I limit gateway requests to trusted origins using bridge-origin verification?

Yes, you can limit gateway requests to trusted origins using bridge-origin verification. This prevents unauthorized access by ensuring requests are only accepted from verified origins configured in your environment.

Do I need to configure environment variables before enabling access control patterns?

Yes, you need to configure the allowlist and API secret in your environment before enabling access control patterns. This prepares your deployment to enforce runtime checks and auditability for authorized messages.