/access-request-intake
Collect a complete system-access request from the user and file it via the IT service desk. Use when someone asks to request, grant, or set up system/application access for an employee.
$ npx -y skills add archestra-ai/archestra --skill access-request-intake --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/access-request-intake
Context preview
The summary Claude sees to decide when to auto-load this skill.
Collect a complete system-access request from the user and file it via the IT service desk. Use when someone asks to request, grant, or set up system/application access for an employee.
SKILL.md
access-request-intake.SKILL.mdname: access-request-intake
description: Collect a complete system-access request from the user and file it via the IT service desk. Use when someone asks to request, grant, or set up system/application access for an employee.
Access request intake
File system-access requests through the Acme IT service desk's `create_access_request` tool. The ticket is only valid when every field is present and correct, so gather all of them before submitting.
Required fields
Collect all five:
- `employee_email` — the person who needs access
- `system` — the system or application
- `access_level` — one of `read-only`, `read-write`, `admin`
- `justification` — the business reason
- `manager_email` — the approving manager
Protocol
1. From the user's request, fill in whatever fields you already have. 2. If any required field is missing or ambiguous, ask the user for it. Do not guess, and do not file the request until you have all five. 3. If the user later changes or corrects a field, use the latest value they gave. 4. Before filing, check the access policy for the requested system and level, and apply every rule it states that bears on the grant, not just the first one. Grant a level the policy allows for this request; if the requested level cannot be granted as asked, follow what the policy says to do instead. 5. Once every field is settled and the level is policy-compliant, call `create_access_request` once with the complete set. 6. Report the returned `ticket_id`.
Read more
name: access-request-intake description: Collect a complete system-access request from the user and file it via the IT service desk. Use when someone asks to request, grant, or set up system/application access for an employee.
Access request intake
File system-access requests through the Acme IT service desk's `create_access_request` tool. The ticket is only valid when every field is present and correct, so gather all of them before submitting.
Required fields
Collect all five:
- `employee_email` — the person who needs access
- `system` — the system or application
- `access_level` — one of `read-only`, `read-write`, `admin`
- `justification` — the business reason
- `manager_email` — the approving manager
Protocol
1. From the user's request, fill in whatever fields you already have. 2. If any required field is missing or ambiguous, ask the user for it. Do not guess, and do not file the request until you have all five. 3. If the user later changes or corrects a field, use the latest value they gave. 4. Before filing, check the access policy for the requested system and level, and apply every rule it states that bears on the grant, not just the first one. Grant a level the policy allows for this request; if the requested level cannot be granted as asked, follow what the policy says to do instead. 5. Once every field is settled and the level is policy-compliant, call `create_access_request` once with the complete set. 6. Report the returned `ticket_id`.
Enterprise AI Platform with guardrails, MCP registry, gateway & orchestrator
Repo: archestra-ai/archestra
Other skills on archestra.
- /archestra-dev-backend-tests
Use when writing or modifying Archestra backend unit tests (platform/backend/src/**/*.test.ts) — mocking modules, stubbing globals, database fixtures, vitest projects/isolation, or test performance.
Open skill - /archestra-dev-backend
Use when adding or changing Archestra backend routes, models, services, API request/response schemas, endpoint permissions, or OpenAPI/codegen for the generated API client.
Open skill - /archestra-dev-bench-analysis
Map-reduce a finished archestra-bench run into a Tier-1/Tier-2 improvement report using Claude subagents (same analysis as the Rust analyzer, no API key).
Open skill - /archestra-dev-e2e
Use when writing, debugging, or running Archestra Playwright e2e tests, API/UI fixtures, WireMock-backed tests, local/CI e2e setup, or test selectors.
Open skill - /archestra-dev-frontend
Use when modifying Archestra frontend Next.js/React code, UI components, forms, TanStack Query hooks, generated API client usage, frontend copy, or documentation links.
Open skill - /archestra-dev-interactions-migrations
Use BEFORE writing or running any Drizzle migration that touches the `interactions` table (or any other very large, write-hot table). The interactions table is the platform's biggest, append-heavy table — every LLM proxy call writes a row — so a careless migration can take a
Open skill

