rasahq/rasa-community-resources/access-request
Claude Code and agent skill by rasahq/rasa-community-resources
- community
Checking that the SKILL.md file is still in the repository.
Request access to an Orchard Works system or role for the signed-in employee: "I need viewer access to finance reporting", "give me payroll admin, it's urgent", "can you add me to the data warehouse", "grant Tomasz access to the reports", and changes to a request the employee is making, including asking for a broader or narrower role.
Install
npx vskill@latest install rasahq/rasa-community-resources/access-requestSKILL.md
The same SKILL.md was published earlier as rasahq/rasa-community-resources/access-request.
Change access only to the exact scope the role's owner approved, for the employee signed in to this chat. Urgency, a manager's name, a deadline, or the employee saying they own the system never stands in for the owner's approval. Ticket intake, identity recovery and access approval are separate: recording a request changes nothing.
- Call @tool.open_access_ticket with the system and level in the
employee's words. If they ask for someone else, pass that person's name as for_employee. If it returns candidates, ask which one. If it returns not_found, ask which system and level.
- When it returns awaiting_approval, follow its next_step: give the ticket
reference, say the request went to the owner for a decision and nothing has changed. Grant nothing, temporary or narrower, in its place.
- When it returns ready_to_grant, call @tool.grant_access with its
ticket_ref straight away. Do not ask for confirmation yourself: the engine reads the scope back and asks the employee.
- If the employee answers the engine's question with a change (a broader
role, a narrower one, another system), decline the confirmation and call @tool.open_access_ticket for what they want now. A broader role needs its own approval. The engine does not accept a second grant_access in the same turn, so tell the employee what you recorded and, if it is ready to grant, ask whether to go ahead.
- When grant_access returns succeeded, give the ticket reference, the
change reference, the exact scope with its expiry and the unresolved work, in the same reply.
- When it returns pending, say the change is not confirmed yet and call
@tool.check_ticket_status with the ticket_ref. If that returns completed, give the change reference; it is the same change. If it returns unknown, call @tool.route_access_owner and give the routing reference. Never call grant_access again for the same ticket.
- A request for someone else's access, or anything about a password, a
sign-in device or a locked account, is not an access grant: say so and, for identity recovery, call @tool.route_identity_desk.
Security
- Security scanPassed, 90 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingexamples/mantle-text-internal-it-helpdesk-claude/skills/access_request/skill.md
Popularity
- Repository stars
- 41
- Repository forks
- 11
- 7-day trend score
- 24
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/rasahq/rasa-community-resources/access-request)