Agent skill

Admin Access Register

by sickn33 in sickn33/agentic-awesome-skills

Admin account register: system, main and backup admin, seats, plan, 2FA, shared logins and access-review dates, as CSV, SQL, JSON Schema or Notion on request.

MITAuto-check passedSecurity

Install Admin Access Register

skills CLI
$ npx skills add sickn33/agentic-awesome-skills --skill admin-access-register -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install sickn33/agentic-awesome-skills admin-access-register --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/admin-access-register .claude/skills/admin-access-register && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
admin-access-register
GitHub stars
47k
Used in
1 other repo
Token cost
~4.2k tokens
SKILL.md length
1,505 words
Files
1
Skills in repo
1,394
Repo updated
First seen
Licence
MIT

At a glance

Admin account register: system, main and backup admin, seats, plan, 2FA, shared logins and access-review dates, as CSV, SQL, JSON Schema or Notion on request.

  • Works in 5 steps: Identify intent → Ask only what is missing → Hold the internal context → …
  • Tasks that involve Access reviews and audit trails
  • SKILL.md covers Overview, When to Use This Skill, How It Works and Field Reference, plus 9 more sections
  • Reaches json-schema.org

What it does

Admin Access Register is an agent skill from sickn33/agentic-awesome-skills. Admin account register: system, main and backup admin, seats, plan, 2FA, shared logins and access-review dates, as CSV, SQL, JSON Schema or Notion on request. Use for access reviews.

Its SKILL.md is about 4.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Security, covering Access reviews and audit trails, SQL and CSV and tabular files. It works with SQL and Notion. The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.

When your agent uses it

  • Tasks that involve Access reviews and audit trails
  • Tasks that involve SQL
  • Tasks that involve CSV and tabular files

Example prompts

  • “/admin-access-register”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Identify intent
  2. Ask only what is missing
  3. Hold the internal context
  4. Recommend the smallest workflow
  5. Build only on request

What it can do on your machine

Read from SKILL.md and the folder at commit 1e53ce2. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml, csv, sql, json and markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • json-schema.org

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Admin Access Register loads about 4.2k tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 1,505 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~51
When it runs · the whole SKILL.md, loaded when a task matches
~4.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from sickn33/agentic-awesome-skills at commit 1e53ce2, republished under its MIT licence (© sickn33). 1,505 words, ~4,188 tokens.

Download SKILL.mdSave it as .claude/skills/admin-access-register/SKILL.md (or your agent's skills folder).
name
admin-access-register
description
Admin account register: system, main and backup admin, seats, plan, 2FA, shared logins and access-review dates, as CSV, SQL, JSON Schema or Notion on request. Use for access reviews.
category
business
risk
safe
source
self
source_type
self
date_added
2026-09-26
author
WHOISABHISHEKADHIKARI
tags
sme, business, operations, database, csv, notion, sql, protect
source_repo
WHOISABHISHEKADHIKARI/sme-ops-system-builder

Admin Access Register

What it is: Who holds admin rights on each system, with a backup admin and review dates.

Overview

Works out the smallest useful Admin Access Register setup for the business in front of it, then builds it only when asked. The default output is a short recommendation, not a spreadsheet. Artifacts - CSV, SQL DDL, JSON Schema, Notion mapping - are produced on request, from one field list so they cannot drift apart.

Layer: Layer 7: Protect. Fits: Growth stage. Table code: n/a.

When to Use This Skill

  • admin access register
  • system access review
  • privileged account list
  • quarterly access review

Also use it when the user says "who holds admin rights on each system, with a backup admin and review dates", or describes the same process happening in a spreadsheet, a document or someone inboxes.

Do not use it for: payroll calculation, tax filing, or legal advice. This skill produces empty templates only - it never holds or processes real employee or customer data.

How It Works

Follow the shared execution contract. The module-specific rules below define only domain fields, decisions, calculations, and safety constraints.

Step 1 - Identify intent

Read the request and pick the intent before asking anything.

  • "set up" or "build" or "create" -> the user wants artifacts; go to Step 2.
  • "our process is ..." or "it is in a sheet" -> the user wants to move an existing process; capture it, then Step 2.
  • "is this right" or "review" or "audit" -> the user wants a check, not a build; answer from what they share.
  • "how do I ..." -> advice question; answer directly and offer the build only if it helps.

Ask only if this is the highest-value missing fact; otherwise proceed without an opener:

Q: How many admin accounts exist?

Step 2 - Ask only what is missing

Skip anything the user already answered, in any earlier message. Ask the rest one at a time, and stop as soon as the remaining answers would not change the output.

  • Scope - Which systems? / How many admins? / Vendor or employee admins?
  • Ownership - Who approves access? / Named owner per account? / Any shared logins?
  • Review - How often reviewed? / What happens on leaving? / Evidence kept?
  • Current process - Is it recorded now? / IT ticket or nothing? / Is it current?
  • Outcome - What do you need? / A register, a review cycle or both?

Never invent an answer. If the user does not know, record it as unknown and carry on.

Step 3 - Hold the internal context

Hold the answers in this shape. It stays internal - it is not shown to the user unless they ask, and it never carries a value the user did not give.

yaml
module: admin-access-register
intent: null            # setup | advice | review | fix | build | convert | export
scale: null             # Starter | Growth | Scale, only if the answer changes it
areas:
  "Scope": null
  "Ownership": null
  "Review": null
  "Current process": null
  "Outcome": null
requested_outputs: []   # csv | sql | json | notion | xlsx - requested formats only
confirmed_facts: []     # only what the user actually said
open_questions: []      # the unanswered ones, in the order worth asking
Step 4 - Recommend the smallest workflow

If an artifact was requested, build it after resolving essential missing facts. Otherwise give a short recommendation and offer the relevant artifact.

Recommended approach: Keep one row per named admin account with a system, an owner and a last-reviewed date. Shared logins are the first thing to fix.

Why this one: Privileged accounts are the ones that matter after someone leaves. Naming an owner per account is what makes removal possible.

Workflow: System listed → Admin account → Owner and approver → Periodic review → Removal

Step 5 - Build only on request

Once the user asks for it, derive the fields from the confirmed context and emit the requested artifacts. For machine-readable text, keep prose outside the data; for files, provide a usable link. Report material validation failures or limitations separately.

A selected Notion output is rendered by notion-manual-import, so route the Notion step there. When the user selects Notion, hand that step to @notion-manual-import: it holds the CSV, the property mapping, the import steps and the verification checklist, and it renders the Field Reference below instead of defining a table of its own. Do not restate the mapping here and do not improvise the import steps. Manual CSV and mapping outputs need no connection. For requested workspace changes, follow the shared contract: verify actual tool access and the target before writing. A user saying "connected" is not tool evidence. Never ask for a Notion password or token.

For an Excel-compatible CSV, use UTF-8 with a byte order mark so Excel opens the text correctly. A CSV is not an .xlsx workbook; create .xlsx only when the user requests a workbook. A CSV carries no types, so after it, name the columns that need a number, date or currency format applied.

csv
System or Tool,Category,Main Admin,Backup Admin,Department,Access Level,Number of Admin Users,Billing Owner,Plan,Seats,Renewal Date,Company Owned Account,Shared Login,Password Manager Entry,Two Factor On,Last Access Review,Next Access Review,Offboarding Checklist Item,Risk Level,Status,Notes,Admin ID
Example Product,General,Example Admin,Example Backup Admin,Delivery,Full,3,Example Owner,Business,5,2026-01-15,TRUE,FALSE,Shared vault - Finance,TRUE,2026-01-15,2026-01-15,"Remove from payroll, revoke accounts, collect laptop",Low,Provisioned,Shared logins retired after the February access review; two orphaned accounts still need an owner.,
sql
CREATE TABLE admin_access_register (
  system_or_tool VARCHAR(255),
  category VARCHAR(100) NOT NULL,
  main_admin VARCHAR(255),
  backup_admin VARCHAR(255),
  department VARCHAR(255),
  access_level VARCHAR(100) NOT NULL,
  number_of_admin_users NUMERIC NOT NULL,
  billing_owner VARCHAR(255),
  plan VARCHAR(255),
  seats NUMERIC NOT NULL,
  renewal_date DATE NOT NULL,
  company_owned_account BOOLEAN NOT NULL,
  shared_login BOOLEAN NOT NULL,
  password_manager_entry VARCHAR(255),
  two_factor_on BOOLEAN NOT NULL,
  last_access_review DATE NOT NULL,
  next_access_review DATE NOT NULL,
  offboarding_checklist_item VARCHAR(255),
  risk_level VARCHAR(100) NOT NULL,
  status VARCHAR(100) NOT NULL,
  notes TEXT,
  admin_id SERIAL PRIMARY KEY,
  created_at TIMESTAMP DEFAULT NOW(),
  updated_at TIMESTAMP DEFAULT NOW()
);

CREATE INDEX idx_admin_access_register_status ON admin_access_register (status);
json
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "Admin Access Register",
  "type": "object",
  "additionalProperties": false,
  "properties": {
      "System or Tool": { "type": "string" },
      "Category": { "type": "string" },
      "Main Admin": { "type": "string" },
      "Backup Admin": { "type": "string" },
      "Department": { "type": "string" },
      "Access Level": { "type": "string" },
      "Number of Admin Users": { "type": "number" },
      "Billing Owner": { "type": "string" },
      "Plan": { "type": "string" },
      "Seats": { "type": "number" },
      "Renewal Date": { "type": "string", "format": "date" },
      "Company Owned Account": { "type": "boolean" },
      "Shared Login": { "type": "boolean" },
      "Password Manager Entry": { "type": "string" },
      "Two Factor On": { "type": "boolean" },
      "Last Access Review": { "type": "string", "format": "date" },
      "Next Access Review": { "type": "string", "format": "date" },
      "Offboarding Checklist Item": { "type": "string" },
      "Risk Level": { "type": "string" },
      "Status": { "type": "string" },
      "Notes": { "type": "string" },
      "Admin ID": { "type": "integer" }
  },
  "required": [
      "Category",
      "Access Level",
      "Number of Admin Users",
      "Seats",
      "Renewal Date",
      "Last Access Review",
      "Next Access Review",
      "Risk Level",
      "Status"
  ]
}
markdown
| CSV column | Notion property | Set after import |
|---|---|---|
| System or Tool | Title | Use as the database title |
| Category | Select (add options after import) | Convert to Select, add options: "General", "Operations", "Finance", "People", "Compliance" |
| Main Admin | Text | Leave as Text |
| Backup Admin | Text | Leave as Text |
| Department | Text | Leave as Text |
| Access Level | Select (add options after import) | Convert to Select, add options: "Full", "Write", "Read", "No Access" |
| Number of Admin Users | Number | Convert to Number |
| Billing Owner | Text | Leave as Text |
| Plan | Text | Leave as Text |
| Seats | Number | Convert to Number |
| Renewal Date | Date | Convert to Date |
| Company Owned Account | Checkbox | Convert to Checkbox |
| Shared Login | Checkbox | Convert to Checkbox |
| Password Manager Entry | Text | Leave as Text |
| Two Factor On | Checkbox | Convert to Checkbox |
| Last Access Review | Date | Convert to Date |
| Next Access Review | Date | Convert to Date |
| Offboarding Checklist Item | Text | Leave as Text |
| Risk Level | Select (add options after import) | Convert to Select, add options: "Low", "Medium", "High", "Critical" |
| Status | Select (add options after import) | Convert to Select, add options: "Requested", "Approved", "Provisioned", "Review Due", "Revoked" |
| Notes | Text | Leave as Text |
| Admin ID | Text (preserve source ID) | Keep imported IDs as Text; optionally add a separate Unique ID property |

The rows above are documentation examples only. Emit empty templates unless the user explicitly requests examples. Money stays currency, dates stay date, and anything pointing at another table stays relation.

Field Reference

#FieldTypeSQLJSON SchemaNotionCSV example
1System or TooltextVARCHAR(255)stringTextExample Product
2CategoryselectVARCHAR(100)stringSelect (add options after import)General
3Main AdmintextVARCHAR(255)stringTextExample Admin
4Backup AdmintextVARCHAR(255)stringTextExample Backup Admin
5DepartmenttextVARCHAR(255)stringTextDelivery
6Access LevelselectVARCHAR(100)stringSelect (add options after import)Full
7Number of Admin UsersnumberNUMERICnumberNumber3
8Billing OwnertextVARCHAR(255)stringTextExample Owner
9PlantextVARCHAR(255)stringTextBusiness
10SeatsnumberNUMERICnumberNumber5
11Renewal DatedateDATEstring, format: dateDate2026-01-15
12Company Owned AccountcheckboxBOOLEANbooleanCheckboxTRUE
13Shared LogincheckboxBOOLEANbooleanCheckboxFALSE
14Password Manager EntrytextVARCHAR(255)stringTextShared vault - Finance
15Two Factor OncheckboxBOOLEANbooleanCheckboxTRUE
16Last Access ReviewdateDATEstring, format: dateDate2026-01-15
17Next Access ReviewdateDATEstring, format: dateDate2026-01-15
18Offboarding Checklist ItemtextVARCHAR(255)stringTextRemove from payroll, revoke accounts, collect laptop
19Risk LevelselectVARCHAR(100)stringSelect (add options after import)Low
20StatusselectVARCHAR(100)stringSelect (add options after import)Provisioned
21Noteslong_textTEXTstringTextShared logins retired after the February access review; two orphaned accounts still need an owner.
22Admin IDidSERIAL PRIMARY KEYintegerText (preserve source ID)(blank)
Show full SKILL.md (503 more words)Show less

Select Options

Category

General | Operations | Finance | People | Compliance

Access Level

Full | Write | Read | No Access

Risk Level

Low | Medium | High | Critical

Status

Requested | Approved | Provisioned | Review Due | Revoked

Relations

Link fields: none

Examples

Prompt

We have admin accounts for people who left two years ago.

Context first - one question per message, nothing already answered:

Q: Which systems? A: Accounting, CRM and email.

Q: Named owner each? A: Not always.

Q: Shared logins? A: Yes, one or two.

Recommended next step - offered, not built:

Keep one row per named admin account with a system, an owner and a last-reviewed date. Shared logins are the first thing to fix.

Workflow: System listed → Admin account → Owner and approver → Periodic review → Removal

Want the CSV, SQL, JSON Schema and Notion mapping for this?

Best Practices

  • Build when requested; recommend and offer a build for advice-only requests.
  • One question per message. A batched intake reads as a form and gets guessed at.
  • Keep display names identical across CSV and JSON; document normalized SQL identifiers.
  • Use relation for anything that points at another table, text only for free text.
  • Money fields are currency, never text. Dates are date, never free text.
  • If the user requests an example row, keep it obviously fake so nobody imports it as real data.

Limitations

  • Empty template only. It does not compute payroll, tax, leave balances or KPIs.
  • Notion relations need both databases imported before the link column resolves.
  • Select options are a starting set. Rename them to match how the business talks.
  • No automation, reminders or sync. Those need the integration layer.
  • Does not grant, change or revoke access on any system.
  • Legal, tax and HR review is still required before this drives real decisions.

Security & Safety Notes

  • Never fill in real names, salaries, medical or banking data. Placeholders only.
  • Label example rows as synthetic, and keep bank details masked.
  • Local reads, generation commands, and validation are part of a requested artifact build. External writes, messages, provisioning, and publication require authorization for that action and target; existing explicit authorization does not need to be repeated.
  • If sensitive data is supplied, avoid repeating unnecessary identifiers. Use only what the requested review needs; keep generated templates empty. Do not claim deletion from the conversation or service storage.
  • Privacy, legal and disciplinary cases need a qualified human reviewer before anything is acted on.

Common Pitfalls

  • Problem: a static mapping is described as a completed workspace build. Solution: deliver manual mappings without a connection; claim a live change only after the authorized tool operation succeeds.
  • Problem: asked all six questions in one message. Solution: ask one, wait, and drop any the first answer already covered.
  • Problem: built a full system when one table was asked for. Solution: build what was requested; mention the parent skill separately.
  • Problem: all four artifacts drift apart. Solution: derive all four from the field list in this file, never by hand.
  • Problem: Notion import shows every column as Text. Solution: that is expected. Apply the property mapping table once, after import.
  • Module Catalog - find the relevant module, then read its skill.
  • @people-directory - the employee master record most modules link to.
  • @notification-reminder-hub - turns due dates in this module into reminders.

Reusable Prompt

I want to set up who holds admin rights on each system, with a backup admin and review dates for my company.
Ask me one short question at a time, and only about what I have not already told you.
Then recommend the smallest setup that fits, and wait for me to ask before you build it.
When I ask, output CSV, SQL DDL, JSON Schema, a Notion property mapping or an Excel workbook. Data only.

© sickn33, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/admin-access-register of sickn33/agentic-awesome-skills.

Open the folder on GitHubat commit 1e53ce2

Used in 1 other repository

We found 5 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Admin Access Register next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Admin Access Register compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Admin Access Register this skillsickn33/agentic-awesome-skills47k1 repos~4.2kAutomated safety check: PassMIT
Rust SQL Testshencangsheng/easydb_app590—~1.2kAutomated safety check: PassMIT
Dummy Datasetkillvxk/pm-skills-zh167—~595Automated safety check: PassMIT
Notcrawlsteipete/agent-scripts7.3k—~272Automated safety check: PassMIT
Duckdb EnaAAaqwq/AGI-Super-Team1051 repos~1.6kAutomated safety check: PassMIT
Excel and CSV Data Analysisbytedance/deer-flow83k4 repos~2.2kAutomated safety check: PassMIT

Similar skills

  • Rust SQL Test

    shencangsheng/easydb_app

    Enforces unit test requirements for the Rust data-processing modules in src-tauri/src/sql/ (generator.rs, parse.rs) and src-tauri/src/reader/ (excel.rs and other readers).

    590 GitHub stars~1.2k tokensUpdated 1 mo ago
    Documents & OfficeAuto-check passed
  • Dummy Dataset

    killvxk/pm-skills-zh

    生成用于测试的逼真虚拟数据集,支持自定义列、约束条件及输出格式(CSV、JSON、SQL、Python 脚本)。适用于创建测试数据、构建模拟数据集,或为开发和演示生成示例数据。

    167 GitHub stars~595 tokensUpdated 6 mo ago
    DatabasesAuto-check passed
  • Notcrawl

    steipete/agent-scripts

    Notion archive: desktop/API sync, Markdown export, page search, read-only SQL.

    7.3k GitHub stars~272 tokensUpdated 3 days ago
    DatabasesAuto-check passed
  • Duckdb En

    aAAaqwq/AGI-Super-Team

    DuckDB CLI specialist for SQL analysis, data processing and file conversion.

    105 GitHub starsUsed in 1 repo~1.6k tokens
    DatabasesAuto-check passed
  • Excel and CSV Data Analysis

    bytedance/deer-flow

    Analyzes uploaded Excel and CSV files with SQL through DuckDB, producing schema inspections, statistical summaries and exports to CSV, JSON or Markdown.

    83k GitHub starsUsed in 4 repos~2.2k tokens
    Data & AnalyticsAuto-check passed
  • Chdb SQL

    vemetric/vemetric

    A skill your agent uses when the user wants to run SQL — especially analytical SQL — on local files (parquet/csv/json), URLs, S3 paths, or remote databases (Postgres, MySQL, MongoDB, ClickHouse…

    394 GitHub starsUsed in 1 repo~1.2k tokens
    DatabasesAuto-check passed

More from sickn33/agentic-awesome-skills

All 1,394 skills in this repo
  • Liuguang Banlan UI

    sickn33/agentic-awesome-skills

    Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • User Thoughts Memory

    sickn33/agentic-awesome-skills

    Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • Using LWC Memory and Graphs

    sickn33/agentic-awesome-skills

    Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.

    47k GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed
  • Find Complementary Founders

    sickn33/agentic-awesome-skills

    Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.

    47k GitHub starsUsed in 1 repo~4.8k tokens
    Auto-check passed
  • Whatsapp Cloud API

    sickn33/agentic-awesome-skills

    Integracao com WhatsApp Business Cloud API (Meta). An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 2 repos~4.5k tokens
    Auto-check passed
  • Cline Pilot

    sickn33/agentic-awesome-skills

    Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.

    47k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed

Works with

Questions about Admin Access Register

What does Admin Access Register do?

Admin account register: system, main and backup admin, seats, plan, 2FA, shared logins and access-review dates, as CSV, SQL, JSON Schema or Notion on request. Admin Access Register is an agent skill from sickn33/agentic-awesome-skills. Admin account register: system, main and backup admin, seats, plan, 2FA, shared logins and access-review dates, as CSV, SQL, JSON Schema or Notion on request.

When should I use Admin Access Register?

Admin Access Register fits situations like: tasks that involve Access reviews and audit trails; tasks that involve SQL; tasks that involve CSV and tabular files.

How do I install Admin Access Register in Claude Code?

Run `npx skills add sickn33/agentic-awesome-skills --skill admin-access-register -a claude-code`. Or copy the skill folder (skills/admin-access-register in sickn33/agentic-awesome-skills) into .claude/skills/admin-access-register in your project. Claude Code loads it when a task matches its description.

How do I install Admin Access Register in Codex?

Run `npx skills add sickn33/agentic-awesome-skills --skill admin-access-register -a codex`. Or copy the skill folder (skills/admin-access-register in sickn33/agentic-awesome-skills) into .agents/skills/admin-access-register in your project. Codex loads it when a task matches its description.

Can I use Admin Access Register in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sickn33/agentic-awesome-skills --skill admin-access-register -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/admin-access-register, .gemini/skills/admin-access-register, .github/skills/admin-access-register and .opencode/skills/admin-access-register in your project.

What does Admin Access Register need to run?

SKILL.md names no scripts, command-line tools or credentials: Admin Access Register is instructions for the agent only.

Does Admin Access Register access the network?

SKILL.md names 1 domain. In commands or code: json-schema.org; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Admin Access Register safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Admin Access Register use?

Admin Access Register is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Admin Access Register use?

About 4.2k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Admin Access Register?

Skills that share tags, products or a category with Admin Access Register: Rust SQL Test (shencangsheng/easydb_app, 590 stars), Dummy Dataset (killvxk/pm-skills-zh, 167 stars), Notcrawl (steipete/agent-scripts, 7.3k stars) and Duckdb En (aAAaqwq/AGI-Super-Team, 105 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Admin Access Register?

sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,304 GitHub stars. The repository holds 1,394 skills in this directory. The repository was last updated on October 6, 2026.

Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.