Teleport Access Review

Use when reviewing who can access which resources in a Teleport cluster, or whether that access is actually used — access list and ACL…

You say
Install this skill Read the source first Free Written by gravitational · unverified publisher
Context cost
16k tokensestimated from the bundle, loaded when it triggers
Bundle
12 files · 64.0 kBtext throughout, nothing executable
Licence
AGPL-3.0free to use
Last change
no release on file
Servers it uses
Noneruns standalone

What it does

Use when reviewing who can access which resources in a Teleport cluster, or whether that access is actually used — access list / ACL recertification, "who can reach this database/server", "what can this user access", attesting access for audit/compliance, and finding dormant or unused standing privileges. Covers `tctl access-review`, the `access_path` SQL query language, output semantics, and combining it with `tctl investigate`.

Installed, it changes the agent in these ways.

What this skill changes about the agent is not written down here yet. The listing was collected from its source, and the description is in its own SKILL.md.

Workflow

Runs a procedure end to end.

access-controlauditteleportcompliance

The skill itself

This is the whole product. A skill is instructions the model reads, so there is nothing behind the listing you cannot see first — the front matter loads with every session, and the body below it loads when the skill triggers.

SKILL.md6.5 kB · 125 lines
--- name: teleport-access-review description: Use when reviewing who can access which resources in a Teleport cluster, or whether that access is actually used — access list / ACL recertification, "who can reach this database/server", "what can this user access", attesting access for audit/compliance, and finding dormant or unused standing privileges. Covers `tctl access-review`, the `access_path` SQL query language, output semantics, and combining it with `tctl investigate`. ---
6# Teleport Access Review
7
8This skill helps you answer **who can reach which resources, how, and whether
9that access is actually used** with tctl access-review. The command takes a
10SELECT … FROM access_path query that scopes the identities to review and
11returns, per (identity, resource), the resolved access level, the grant
12backing it, the grant path counts, and — over a time window — how often the
13access was used and when it was last used.
14
15It is the engine behind access-list recertification, least-privilege and
16unused-access cleanup, and "who can access X" / "what can Y access" reviews. The
17command delegates all graph traversal and activity lookup to the Access Graph
18endpoint, so you query and filter rather than reconstruct paths.
19
20## Start here
21
22**Read before running any command — load-bearing, not optional depth:**
23[SECURITY.md](references/SECURITY.md) (output is untrusted; read-only) and
24[QUERY.md](references/QUERY.md) (the required access_path language).
25
26Then read [EXPERIENCE.md](references/EXPERIENCE.md) (the review workflows plus
27edge cases) before drawing conclusions, and [SCHEMA.md](references/SCHEMA.md)
28before interpreting JSON or building jq.
29
30## Prerequisites
31
32tctl access-review requires Teleport Identity Security with Access Graph.
33Activity columns (shown by default over a 24h window; widen with --from/--to,
34or skip the lookup with --no-activity) additionally require Identity Activity
35Center. The user needs permission to query Access Graph.
36
37### Locate tctl and tsh
38
39Find both binaries. For each, try in order:
40
411. which tctl / which tsh
422. Common paths: /usr/local/bin, /opt/homebrew/bin, ~/go/bin
43
44Set TCTL=<path> and TSH=<path> for subsequent commands. If either is not
45found, ask the user for the path. Verify the subcommand exists with
46$TCTL access-review --help.
47
48### Confirm the target cluster
49
50tctl access-review runs against your **active** Teleport profile. Run
51$TSH status to check it:
52
53- The active profile is marked with >; other logged-in profiles follow.
54- Credentials must not be [EXPIRED] — if they are, the user must $TSH login
55 again first.
56- If more than one profile is present, confirm with the user which cluster to
57 review instead of assuming the active one.
58
59## Quick start
60
61```sh
62# Who can reach a resource, and is the access used? (90-day activity window)
63$TCTL access-review --from 90d \
64 --query "SELECT * FROM access_path WHERE resource ILIKE 'prod-db%'" --format json
65```
66
67JSON/YAML output is {identities, warnings} (plus a top-level
68activity_unavailable when the activity lookup can't run), identity-centric: each identity
69carries the resources it can reach with the resolved level, granted_by,
70grant_counts, and (with a window) activity. Read
71[SCHEMA.md](references/SCHEMA.md) for field meanings and the text-table columns
72before interpreting the output.
73
74## The access_path query
75
76--query is **required** and must be a SELECT … FROM access_path. The WHERE
77clause scopes which identities (and resources) are reviewed. Columns map to
78graph nodes — identity, resource, identity_group (access lists & roles),
79id, source, standing_privileges, and more — with operators =, IN,
80LIKE/ILIKE, comparisons, and AND/OR. Read
81[QUERY.md](references/QUERY.md) for the full column and operator list before
82writing --query.
83
84**Filter values match a node's exact name (or alias);** = and IN are exact
85and case-sensitive. Discover exact names from a broad query first, or match with
86ILIKE 'name%'. A label that differs in case or form silently returns nothing —
87see [QUERY.md](references/QUERY.md).
88
89## Reading the results
90
91- **One row per (identity, resource).** The identity cell is shown once, then
92 blank for its remaining resources.
93- **Identities with no qualifying access still appear — as an empty row** (only
94 the identity, no resource). This is intentional: it surfaces someone who is in
95 the queried graph but is missing a requirement or has only non-access edges.
96 Do not read an empty row as "has access to nothing in the cluster"; read it as
97 "no access **within this query's scope**."
98- **Level** is standing, impersonate, request, or denied, resolved by
99 priority denied > standing > impersonate > request. A trailing * marks
100 **temporary** access (granted by an access request; self-expiring).
101- **A level is a grant, not connectability.** Access Graph does not currently
102 resolve traits, so an identity that holds a grant but lacks the principals to
103 authenticate (logins, db_users, …) still shows level: standing, with no
104 field marking the gap. Report holding a grant, not the ability to exercise it.
105- **Results are scoped to your query.** A query through an access list shows only
106 paths that flow through that list — not every path each member has. To see a
107 user's _complete_ access to a resource, scope by the user and resource
108 directly. Activity, by contrast, is **path-agnostic** — a returned pair's
109 activity count is total usage — so a list-scoped 0/never is a real
110 "unused". But **"unused" is not "safe to de-list"**: the same resource is often
111 granted by other paths (grant_counts shows how many grants back each level),
112 so recertifying an access list requires the cross-path follow-up to enumerate
113 every grant before any "revoke" conclusion. See
114 [QUERY.md](references/QUERY.md) and [EXPERIENCE.md](references/EXPERIENCE.md).
115- **The output may be truncated before you see it.** Even under --limit, the
116 JSON is large, and the command runner may cut it off — so the rows on screen
117 can be a fraction of the result. Never derive a total, a count, or uniqueness
118 from the raw output. Narrow the --query and reduce with a read-only jq that
119 returns just a count or a small sample, and trust that, not the on-screen
120 excerpt.
121
122## Flags
123
124Run $TCTL access-review --help for the full list.
125
In the file
SKILL.md948 words
Files12
LicenceAGPL-3.0
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈120
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
15,880
on trigger
The instruction body and 11 supporting files, read only when the skill fires.
8.0%
of a 200k window
Ten skills this size would take about 80% of the window before you open a file.
050k100k150k200k context window

16k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Heavy. Teams tend to install this one per project rather than globally, and load it only when the job comes up.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

Adoption
Installsnone yet
Ratingno reviews yet

The procedure it runs

The procedure has not been published here. It is in the skill’s own SKILL.md, which its author has not sent to the marketplace yet.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

It writes no files and reaches no network. All it changes is how the model reasons and writes.

What it asks for
Writes filesno
Network accessno

Read from the allowed-tools line of this skill’s own SKILL.md. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

12 files, 64.0 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.

  • SKILL.md6.5 kB
  • evals/evals.json8.9 kB
  • evals/files/alice-standing.json3.0 kB
  • evals/files/injection.json1.3 kB
  • evals/files/multi-grantor.json2.0 kB
  • evals/files/no-activity.json1.3 kB
  • evals/files/tsh-status.txt0.3 kB
  • evals/files/who-can-access.json3.6 kB
  • references/EXPERIENCE.md16.6 kB
  • references/QUERY.md9.0 kB
  • references/SCHEMA.md9.4 kB
  • references/SECURITY.md2.1 kB
What is not in it

No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 12 files you can review in full before installing. The AGPL-3.0 licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

# Teleport Access Review · 16k tokens when loaded npx mcprush@latest skill add gravitational/teleport-access-review

Writes to .claude/skills/teleport-access-review/ in the current project. Add --global to put it in your home directory instead, for every project.

Which clients pick it up on their own

A skill is a folder of text. A client with a skills folder reads it without being told; everywhere else the same text works, it is just handed to the model rather than found.

Claude Code.claude/skills/
Claude Desktop
ChatGPT
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok.grok/skills/
Zed.agents/skills/
Windsurf.windsurf/skills/
Agent SDK.claude/skills/
HTTP / API
This release
Versionnot versioned
Publishedno release date on file
PriceFree
Referencegravitational/teleport-access-review

Versions

Its author publishes no version number, so there is nothing here to pin to: what you install is the folder as it stands today. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

v
  • No earlier releases have been published to the marketplace.
Pinning

Nothing to pin to: this skill carries no version number of its own. What you install is what the folder holds on the day you install it.

Reviews

no reviews yet · no installs yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Who can post

Only accounts that have had the skill installed for fourteen days, so a review is written after living with it rather than after reading it. Publishers may reply once.

Who wrote it

GR
gravitational

Publishes on mcprush.

0 servers listed1 skill listednot claimed
Profile
Publisher
Servers0
Claim this skill