OpenParable
Skip to content
← Back to skills

Access Request Intake

DevOps & Security
access-request-intake

Access Request Intake is an Agent Skill for devops & security published in the archestra-ai/archestra repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/archestra-ai/archestra/blob/HEAD/ai-labs/skills/access-request-intake/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/access-request-intake, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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.