Agent skill

Frappe Core Permissions

by Impertio-Studio in Impertio-Studio/Frappe_Claude_Skill_Package

A skill your agent uses when implementing the Frappe/ERPNext permission system.

MITAuto-check passedBackend & APIs

Install Frappe Core Permissions

skills CLI
$ npx skills add Impertio-Studio/Frappe_Claude_Skill_Package --skill frappe-core-permissions -a claude-code

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

GitHub CLI
$ gh skill install Impertio-Studio/Frappe_Claude_Skill_Package frappe-core-permissions --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/Impertio-Studio/Frappe_Claude_Skill_Package.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/source/core/frappe-core-permissions .claude/skills/frappe-core-permissions && 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
frappe-core-permissions
GitHub stars
189
Token cost
~2.9k tokens
SKILL.md length
688 words
Files
6 (incl. references)
Skills in repo
61
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when implementing the Frappe/ERPNext permission system.

  • Works in 10 steps: ALWAYS use frappe.has_permission() —… → ALWAYS use frappe.get_list() for… → ALWAYS escape SQL in query hooks —… → …
  • Implementing the Frappe/ERPNext permission system
  • SKILL.md covers Permission Layers, Decision Tree, Permission Types and Automatic Roles, plus 14 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Frappe Core Permissions is an agent skill from Impertio-Studio/Frappe_Claude_Skill_Package. Use when implementing the Frappe/ERPNext permission system. Covers roles, user permissions, perm levels, data masking, and permission hooks for v14/v15/v16. Prevents common access control mistakes and security issues. Keywords: permissions, roles, user permissions, perm levels, data masking,, restrict records, who can see what, department access, row-level, user cannot see document, access denied. access control, security, haspermission.

Its SKILL.md is about 2.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `references/anti-patterns.md`, `references/examples.md` and `references/permission-api-reference.md`). Compatibility notes: Claude Code, Claude.ai Projects, Claude API. Frappe v14-v16.

It sits in Backend & APIs, covering Authorization and RBAC. The repository describes itself as: 60 deterministic Claude AI skills for Frappe Framework & ERPNext v14-v16 development and operations. The licence is MIT.

When your agent uses it

  • Implementing the Frappe/ERPNext permission system
  • Tasks that involve Authorization and RBAC

Example prompts

  • “/frappe-core-permissions”

Requirements

  • Python 3
  • Compatibility (from SKILL.md): Claude Code, Claude.ai Projects, Claude API. Frappe v14-v16.

Workflow steps

10 steps, taken from the first numbered list in SKILL.md.

  1. ALWAYS use frappe.has_permission() — NEVER check roles directly for access control
  2. ALWAYS use frappe.get_list() for user-facing queries — NEVER get_all()
  3. ALWAYS escape SQL in query hooks — frappe.db.escape(user)
  4. ALWAYS prefix table names in query hooks — tabDocType.fieldname
  5. ALWAYS return None in has_permission hooks by default — NEVER True
  6. ALWAYS clear cache after permission changes — frappe.clear_cache()
  7. ALWAYS document ignore_permissions usage with a comment
  8. NEVER throw errors in has_permission hooks — return False to deny
  9. NEVER grant permlevel 1+ without granting permlevel 0 first
  10. NEVER assume data masking applies to custom SQL queries [v16+]

What it can do on your machine

Read from SKILL.md and the folder at commit 36cfa80. 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 python and json).

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

  • Network

    No URLs in SKILL.md.

    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.

  • Compatibility

    Claude Code, Claude.ai Projects, Claude API. Frappe v14-v16.

    From compatibility in the SKILL.md frontmatter.

Context cost

Frappe Core Permissions loads about 2.9k tokens when it runs, and up to ~10k if it reads all its reference files. Until then it costs about 117 tokens; SKILL.md has 688 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~117
When it runs · the whole SKILL.md, loaded when a task matches
~2.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~10k

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 Impertio-Studio/Frappe_Claude_Skill_Package at commit 36cfa80, republished under its MIT licence (© Impertio-Studio). 688 words, ~2,921 tokens.

Download SKILL.mdSave it as .claude/skills/frappe-core-permissions/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
frappe-core-permissions
description
Use when implementing the Frappe/ERPNext permission system. Covers roles, user permissions, perm levels, data masking, and permission hooks for v14/v15/v16. Prevents common access control mistakes and security issues. Keywords: permissions, roles, user permissions, perm levels, data masking,, restrict records, who can see what, department access, row-level, user cannot see document, access denied. access control, security, has_permission.
compatibility
Claude Code, Claude.ai Projects, Claude API. Frappe v14-v16.
license
MIT
metadata.author
OpenAEC-Foundation
metadata.version
2.0

Frappe Permissions

Deterministic patterns for the five-layer Frappe permission system.


Permission Layers

LayerControlsConfigured ViaVersion
Role PermissionsWhat users CAN doDocType permissions tableAll
User PermissionsWHICH records users seeUser Permission DocTypeAll
Perm LevelsWHICH fields users see/editField permlevel propertyAll
Permission HooksCustom deny logichooks.pyAll
Data MaskingMasked field valuesField mask property[v16+]

Decision Tree

Need to control access?
├── Who can Create/Read/Write/Delete a DocType? → Role Permissions
├── Which specific records can a user see? → User Permissions
├── Which fields should be hidden? → Perm Levels (permlevel 1+)
├── Which fields show masked values? → Data Masking [v16+]
├── Custom runtime deny logic? → has_permission hook
├── Filter list queries dynamically? → permission_query_conditions hook
└── Share one document with one user? → frappe.share

Checking permissions in code?
├── Before action → frappe.has_permission() or doc.has_permission()
├── Raise on denial → doc.check_permission() or throw=True
├── System bypass → doc.flags.ignore_permissions = True (ALWAYS document why)
└── List query → ALWAYS use frappe.get_list() for user-facing data

Permission Types

TypeAPI CheckApplies To
readfrappe.has_permission(dt, "read")All DocTypes
writefrappe.has_permission(dt, "write")All DocTypes
createfrappe.has_permission(dt, "create")All DocTypes
deletefrappe.has_permission(dt, "delete")All DocTypes
submitfrappe.has_permission(dt, "submit")Submittable only
cancelfrappe.has_permission(dt, "cancel")Submittable only
amendfrappe.has_permission(dt, "amend")Submittable only
selectfrappe.has_permission(dt, "select")Link fields [v14+]
reportN/AReport Builder access
exportN/AExcel/CSV export
importN/AData Import Tool
shareN/AShare with other users
printN/APrint/PDF generation
emailN/ASend email
maskRole permission for unmasked viewData Masking [v16+]

Automatic Roles

RoleAssigned ToNotes
GuestEveryone (including anonymous)Public pages
AllAll registered usersBasic authenticated access
AdministratorOnly the Administrator userALWAYS has all permissions
Desk UserSystem Users only[v15+]

Essential API

Check Permission
python
# DocType-level
frappe.has_permission("Sales Order", "write")

# Document-level (by name or object)
frappe.has_permission("Sales Order", "write", "SO-00001")
frappe.has_permission("Sales Order", "write", doc=doc)

# For specific user
frappe.has_permission("Sales Order", "read", user="john@example.com")

# Throw on denial
frappe.has_permission("Sales Order", "delete", throw=True)

# Debug mode — prints evaluation steps
frappe.has_permission("Sales Order", "read", debug=True)
print(frappe.local.permission_debug_log)
Document Instance Methods
python
doc = frappe.get_doc("Sales Order", "SO-00001")

# Returns bool
if doc.has_permission("write"):
    doc.status = "Approved"
    doc.save()

# Raises frappe.PermissionError if denied
doc.check_permission("write")
Get Effective Permissions
python
from frappe.permissions import get_doc_permissions

perms = get_doc_permissions(doc)
# {'read': 1, 'write': 1, 'create': 0, 'delete': 0, ...}

perms = get_doc_permissions(doc, user="john@example.com")

User Permissions (Record-Level)

Restrict users to specific Link field values (e.g., specific Company, Territory).

python
from frappe.permissions import add_user_permission, remove_user_permission

# Restrict user to one company
add_user_permission(
    doctype="Company",
    name="My Company",
    user="john@example.com",
    is_default=1,            # auto-fill in new documents
    applicable_for="Sales Order"  # only for this DocType (optional)
)

# Remove restriction
remove_user_permission("Company", "My Company", "john@example.com")

# Query current restrictions
from frappe.permissions import get_user_permissions
perms = get_user_permissions("john@example.com")
# {"Company": [{"doc": "My Company", "is_default": 1}], ...}

Sharing (Document-Level)

Grant access to a single document for a specific user.

python
from frappe.share import add as add_share, remove as remove_share

add_share("Sales Order", "SO-00001", "jane@example.com",
          read=1, write=1, share=0, notify=1)

remove_share("Sales Order", "SO-00001", "jane@example.com")

# Share with everyone
add_share("Sales Order", "SO-00001", everyone=1, read=1)

Field-Level Permissions (Perm Levels)

Group fields by permlevel (0-9). Level 0 MUST be granted before higher levels.

json
{
  "fields": [
    {"fieldname": "employee_name", "permlevel": 0},
    {"fieldname": "salary",        "permlevel": 1}
  ],
  "permissions": [
    {"role": "Employee",   "permlevel": 0, "read": 1},
    {"role": "HR Manager", "permlevel": 0, "read": 1, "write": 1},
    {"role": "HR Manager", "permlevel": 1, "read": 1, "write": 1}
  ]
}

Rule: Levels do NOT imply hierarchy. Level 2 is not "higher" than level 1. They are independent field groups.


Data Masking [v16+]

Fields with mask=1 show masked values (e.g., ****, +91-811XXXXXXX) to users without mask permission.

json
{
  "fieldname": "phone_number", "fieldtype": "Data", "mask": 1
}

Grant mask permission to roles that MUST see unmasked values:

json
{"role": "HR Manager", "permlevel": 0, "read": 1, "mask": 1}

CRITICAL: Data masking does NOT apply to frappe.db.sql() or Query Reports with raw SQL. You MUST mask manually in custom SQL queries.


Permission Hooks

has_permission: Custom Deny Logic

Can only deny access. NEVER returns True to grant. ALWAYS returns None to continue standard checks.

python
# hooks.py
has_permission = {
    "Sales Order": "myapp.permissions.check_order_permission"
}
python
# myapp/permissions.py
def check_order_permission(doc, ptype, user):
    if ptype == "write" and doc.docstatus == 2:
        if "Sales Manager" not in frappe.get_roles(user):
            return False
    return None  # ALWAYS return None by default
permission_query_conditions: Filter List Queries

Returns SQL WHERE clause fragment. Only affects get_list(), NOT get_all().

python
# hooks.py
permission_query_conditions = {
    "Customer": "myapp.permissions.customer_query"
}
python
def customer_query(user):
    if not user:
        user = frappe.session.user
    if "Sales Manager" in frappe.get_roles(user):
        return ""
    return f"`tabCustomer`.owner = {frappe.db.escape(user)}"

ALWAYS use frappe.db.escape() — NEVER use string concatenation with raw user input.


get_list vs get_all

MethodUser PermissionsQuery HookUse For
frappe.get_list()AppliedAppliedUser-facing queries
frappe.get_all()IgnoredIgnoredSystem/background queries

ALWAYS use get_list() when returning data to users. get_all() bypasses ALL permission filtering.


Common Patterns

Owner-Only Edit
json
{"role": "Sales User", "read": 1, "write": 1, "create": 1, "if_owner": 1}
Role-Restricted Endpoint
python
@frappe.whitelist()
def sensitive_action():
    frappe.only_for(["Manager", "Administrator"])
    # Only reaches here if user has one of these roles
Bypass Permissions (Document Why!)
python
# On document — ALWAYS add a comment explaining the reason
doc.flags.ignore_permissions = True
doc.save()

# On method call
doc.save(ignore_permissions=True)
doc.insert(ignore_permissions=True)

Show full SKILL.md (294 more words)Show less

Critical Rules

  1. ALWAYS use frappe.has_permission() — NEVER check roles directly for access control
  2. ALWAYS use frappe.get_list() for user-facing queries — NEVER get_all()
  3. ALWAYS escape SQL in query hooks — frappe.db.escape(user)
  4. ALWAYS prefix table names in query hooks — `tabDocType`.fieldname
  5. ALWAYS return None in has_permission hooks by default — NEVER True
  6. ALWAYS clear cache after permission changes — frappe.clear_cache()
  7. ALWAYS document ignore_permissions usage with a comment
  8. NEVER throw errors in has_permission hooks — return False to deny
  9. NEVER grant permlevel 1+ without granting permlevel 0 first
  10. NEVER assume data masking applies to custom SQL queries [v16+]

Anti-Patterns

Do NOTDo Instead
if "Role" in frappe.get_roles() for accessfrappe.has_permission(dt, ptype)
frappe.get_all() for user queriesfrappe.get_list()
return True in has_permission hookreturn None
f"owner = '{user}'" in SQLf"owner = {frappe.db.escape(user)}"
frappe.throw() in permission hooksreturn False
frappe.db.set_value() for user-facing updatesdoc.save() with permission check
Sensitive data in error messagesGeneric frappe.PermissionError

Version Differences

Featurev14v15v16
select permissionYesYesYes
Desk User roleNoYesYes
Data Masking (mask field)NoNoYes
mask permission typeNoNoYes
Custom Permission TypesNoNoExperimental

Permission Precedence

  1. Administrator — ALWAYS has all permissions (cannot be restricted)
  2. Role Permissions — Based on assigned roles
  3. User Permissions — Restricts to specific document values
  4. has_permission hook — Can only deny (any False = denied)
  5. Sharing — Grants access to shared documents
  6. if_owner — Further restricts to owned documents

Reference Files

FileContents
permission-types-reference.mdAll permission types with options
permission-api-reference.mdComplete API with all signatures
permission-hooks-reference.mdHook patterns and examples
examples.mdWorking implementation examples
anti-patterns.mdCommon mistakes and fixes
  • frappe-core-database — Database operations that respect permissions
  • frappe-core-api — API endpoints with permission checks
  • frappe-syntax-controllers — Controller permission validation
  • frappe-syntax-hooks — Hook configuration patterns

Verified against Frappe docs 2026-03-20 | Frappe v14/v15/v16

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

Files

SKILL.md and 5 other files (references) in skills/source/core/frappe-core-permissions of Impertio-Studio/Frappe_Claude_Skill_Package.

  • SKILL.md
  • references/anti-patterns.md
  • references/examples.md
  • references/permission-api-reference.md
  • references/permission-hooks-reference.md
  • references/permission-types-reference.md

Open the folder on GitHubat commit 36cfa80

Compare with similar skills

Frappe Core Permissions 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.

Frappe Core Permissions compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Frappe Core Permissions this skillImpertio-Studio/Frappe_Claude_Skill_Package189—~2.9kAutomated safety check: PassMIT
Configuring Horizoncoollabsio/coolify63k4 repos~898Automated safety check: PassMIT
K8s Security PoliciesCybereason-Public/owLSM28012 repos~2kAutomated safety check: PassGPL-2.0
Payloadpayloadcms/payload45k5 repos~6.2kAutomated safety check: PassMIT
Convex Setup Authspokvulcan/poker-planning1148 repos~1.8kAutomated safety check: PassMIT
Cognitoitsmostafa/aws-agent-skills1.2k1 repos~2.3kAutomated safety check: PassMIT

Similar skills

  • Configuring Horizon

    coollabsio/coolify

    A skill your agent uses whenever the user mentions Horizon by name in a Laravel context.

    63k GitHub starsUsed in 4 repos~898 tokens
    Backend & APIsAuto-check passed
  • K8s Security Policies

    Cybereason-Public/owLSM

    Comprehensive guide for implementing NetworkPolicy, PodSecurityPolicy, RBAC, and Pod Security Standards in Kubernetes.

    280 GitHub starsUsed in 12 repos~2k tokens
    Backend & APIsAuto-check passed
  • Payload

    payloadcms/payload

    A skill your agent uses when working with Payload projects (payload.config.ts, collections, fields, hooks, access control, Payload API).

    45k GitHub starsUsed in 5 repos~6.2k tokens
    Backend & APIsAuto-check passed
  • Convex Setup Auth

    spokvulcan/poker-planning

    Sets up Convex auth, identity mapping, and access control. An agent skill from spokvulcan/poker-planning.

    114 GitHub starsUsed in 8 repos~1.8k tokens
    Backend & APIsAuto-check passed
  • Cognito

    itsmostafa/aws-agent-skills

    AWS Cognito user authentication and authorization service. An agent skill from itsmostafa/aws-agent-skills.

    1.2k GitHub starsUsed in 1 repo~2.3k tokens
    Backend & APIsAuto-check passed
  • Abp Authorization

    abpframework/abp

    ABP permission system - PermissionDefinitionProvider, [Authorize] attribute, CheckPolicyAsync, IsGrantedAsync, ICurrentUser, IPermissionManager, multi-tenancy side.

    14k GitHub stars~1.3k tokensUpdated yesterday
    Backend & APIsAuto-check passed

More from Impertio-Studio/Frappe_Claude_Skill_Package

All 61 skills in this repo
  • Frappe Ops Website Deploy

    Impertio-Studio/Frappe_Claude_Skill_Package

    Deploy HTML/CSS websites to ERPNext/Frappe (v15/v16) as Web Pages via the REST API.

    189 GitHub stars~2.5k tokensUpdated 23 days ago
    Auto-check passed
  • Frappe Agent Architect

    Impertio-Studio/Frappe_Claude_Skill_Package

    A skill your agent uses when designing multi-app Frappe architectures, deciding whether to split functionality into separate apps, or implementing cross-app communication patterns.

    189 GitHub stars~2.8k tokensUpdated 23 days ago
    Auto-check passed
  • Frappe Agent Debugger

    Impertio-Studio/Frappe_Claude_Skill_Package

    A skill your agent uses when debugging Frappe errors, using bench console for live inspection, analyzing tracebacks, or reading Frappe log files.

    189 GitHub stars~2.9k tokensUpdated 23 days ago
    Auto-check passed
  • Frappe Agent Interpreter

    Impertio-Studio/Frappe_Claude_Skill_Package

    A skill your agent uses when receiving vague or unclear ERPNext/Frappe development requests that need interpretation.

    189 GitHub stars~3.2k tokensUpdated 23 days ago
    Auto-check passed
  • Frappe Agent Migrator

    Impertio-Studio/Frappe_Claude_Skill_Package

    A skill your agent uses when migrating a Frappe app between major versions, detecting breaking API changes, or resolving post-migration errors.

    189 GitHub stars~2.8k tokensUpdated 23 days ago
    Auto-check: notes
  • Frappe Agent Validator

    Impertio-Studio/Frappe_Claude_Skill_Package

    A skill your agent uses when reviewing or validating Frappe/ERPNext code against best practices and common pitfalls.

    189 GitHub stars~2.8k tokensUpdated 23 days ago
    Auto-check passed

Categories

Questions about Frappe Core Permissions

What does Frappe Core Permissions do?

A skill your agent uses when implementing the Frappe/ERPNext permission system. Frappe Core Permissions is an agent skill from Impertio-Studio/Frappe_Claude_Skill_Package. Use when implementing the Frappe/ERPNext permission system.

When should I use Frappe Core Permissions?

Frappe Core Permissions fits situations like: implementing the Frappe/ERPNext permission system; tasks that involve Authorization and RBAC.

How do I install Frappe Core Permissions in Claude Code?

Run `npx skills add Impertio-Studio/Frappe_Claude_Skill_Package --skill frappe-core-permissions -a claude-code`. Or copy the skill folder (skills/source/core/frappe-core-permissions in Impertio-Studio/Frappe_Claude_Skill_Package) into .claude/skills/frappe-core-permissions in your project. Claude Code loads it when a task matches its description.

How do I install Frappe Core Permissions in Codex?

Run `npx skills add Impertio-Studio/Frappe_Claude_Skill_Package --skill frappe-core-permissions -a codex`. Or copy the skill folder (skills/source/core/frappe-core-permissions in Impertio-Studio/Frappe_Claude_Skill_Package) into .agents/skills/frappe-core-permissions in your project. Codex loads it when a task matches its description.

Can I use Frappe Core Permissions 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 Impertio-Studio/Frappe_Claude_Skill_Package --skill frappe-core-permissions -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/frappe-core-permissions, .gemini/skills/frappe-core-permissions, .github/skills/frappe-core-permissions and .opencode/skills/frappe-core-permissions in your project.

What does Frappe Core Permissions need to run?

SKILL.md names no scripts, command-line tools or credentials: Frappe Core Permissions is instructions for the agent only. Our summary lists: Python 3. Compatibility (from SKILL.md): Claude Code, Claude.ai Projects, Claude API. Frappe v14-v16..

Does Frappe Core Permissions access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Frappe Core Permissions 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 Frappe Core Permissions use?

Frappe Core Permissions is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Frappe Core Permissions use?

About 2.9k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 7.4k tokens, read only when the agent opens those files.

What are the alternatives to Frappe Core Permissions?

Skills that share tags, products or a category with Frappe Core Permissions: Configuring Horizon (coollabsio/coolify, 63k stars), K8s Security Policies (Cybereason-Public/owLSM, 280 stars), Payload (payloadcms/payload, 45k stars) and Convex Setup Auth (spokvulcan/poker-planning, 114 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Frappe Core Permissions?

Impertio-Studio (a GitHub organization) maintains it in Impertio-Studio/Frappe_Claude_Skill_Package, which has 189 GitHub stars. The repository holds 61 skills in this directory. The repository was last updated on September 17, 2026.

Source: Impertio-Studio/Frappe_Claude_Skill_Package on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.