AccessOwl Skills for Claude

Claude can work with the AccessOwl API from its general knowledge, but skills make it fast and consistent. A skill teaches Claude exactly how to handle one AccessOwl task, from which endpoints to call to how to present the answer and when to ask for confirmation. The ClaudeTag for AccessOwl plugin bundles one skill per task, carefully curated by the AccessOwl team for accuracy. You fork its public GitHub repository into your organization, connect the fork to Claude as a plugin source, and everyone in the channel gets the same behavior. Read-only questions are answered in one message, Claude asks for one confirmation before anything is created, and requests always follow your approval policies.

The skills

Skill	What you can say
`request-access`	”Request a HubSpot Marketing seat for Tom.”
`request-revocation`	”Tom no longer needs his HubSpot seat, revoke it.”
`grant-access`	”Maria’s Mixpanel access is provisioned, mark the request granted.”
`list-access`	”What does Maria have access to?”
`mirror-access`	”Give Tom the same access as Lisa.”
`access-report`	”Everyone in Marketing without HubSpot.”
`userlist-import-preflight`	”Validate this CSV against our Notion app before I import it.”
`vendor-update`	”We finished the vendor review for Slack, record today’s date.”
`view-policies`	”Which policy covers Salesforce?”
`discovered-apps`	”Which apps has AccessOwl discovered?”

See Manage access with Claude Tag for full conversation examples.

Install the plugin

You need the Claude Tag connection to AccessOwl set up first. Then, as a Claude organization admin:

Fork the AccessOwl skills repository

Fork the AccessOwl skills repository (github.com/AccessOwl/claude-skills-for-customer) into a private repository in your organization’s GitHub account.

Claude only accepts private or internal repositories as organization plugin sources, so the public AccessOwl repository can’t be connected directly. Your fork is what Claude syncs from.

Connect the fork to Claude

In claude.ai, go to Organization settings > Plugins and add your fork as a plugin source via Sync from GitHub. If prompted, install the Claude GitHub App on the fork. Leave Sync automatically on so plugin updates in your fork reach your workspace on their own; new threads pick them up automatically.

Attach the plugin

Open the Access bundle that holds your AccessOwl API credential, select + in its Plugins section, and add ClaudeTag for AccessOwl from the marketplace.

Adding the plugin to an Access bundle

Add the recommended instructions

In the custom instructions for your workspace or the access channel, paste:

For anything about access, applications, users, or policies, always use
the skills from the ClaudeTag for AccessOwl plugin. Do not answer
AccessOwl questions without them.

This keeps Claude on the skills instead of improvising.

Staying up to date

Claude syncs from your fork, so new skill versions published by AccessOwl reach you once your fork catches up with the upstream repository. Two ways to do that:

Select Sync fork on your fork’s GitHub page whenever AccessOwl announces a new version. One click, done.
The repository ships a sync-upstream GitHub Actions workflow that pulls upstream changes into your fork on a daily schedule. Enable Actions on your fork once and updates flow through without any clicks.

The plugin also works in Claude Code, where no fork is needed. Add the public repository directly with /plugin marketplace add AccessOwl/claude-skills-for-customer and the skills are available in your terminal.

General

Quickstart for...

Guides

Integrations

AccessOwl Skills for Claude

The skills

Install the plugin

Staying up to date

​The skills

​Install the plugin

​Staying up to date

The skills

Install the plugin

Staying up to date