Skip to main content
agentsSource-backed

Agent Skills Enterprise Librarian Agent

An agent prompt for curating an organization's Agent Skills: reviewing each SKILL.md name and description, scope (personal, project, or plugin) and precedence, per-skill allowed-tools, and whether Claude or the user invokes it.

by JPette1783·added 2026-06-05·
Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://code.claude.com/docs/en/skills, https://github.com/JSONbored/awesome-claude/blob/main/content/agents/agent-skills-enterprise-librarian-agent.mdx
Safety notes
This agent curates and reviews skills; it does not execute them., Recommend tool restrictions (allowed-tools) for skills that touch sensitive actions, and invocation control for skills with side effects., Flag skills whose descriptions could cause the model to auto-invoke them in inappropriate contexts.
Privacy notes
Skill descriptions load each session; keep sensitive workflow detail and secrets out of them., Skills sourced from outside the org should be reviewed before adoption, since their instructions run in your sessions., Use settings-level overrides to hide or disable model-invocation of skills you did not author without editing their files.
Author
JPette1783
Submitted by
JPette1783
Claim status
unclaimed
Last verified
2026-06-05

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

63

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Needs review

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as source-backed.

    Done
  • Metadata reviewed

    No reviewed flag detected in metadata.

    Pending

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    No package verification flag provided.

    Pending
  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

Copy & paste

Copy-ready — paste the snippet to get started.

Adoption plan

Balanced adoption plan

Current risk score 24/100. Use staged verification before broader rollout.

Risk 24

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    No review metadata found; increase manual validation.

    Pending
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Missing required evidence: Metadata review. Risk score 31.

Risk 31

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Missing

Review metadata is missing.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required gaps: Metadata review

Decision timeline

Decision timeline · balanced

Blocking gaps: Check metadata review status. Risk 28.

Risk 28

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is missing.

Pending

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

Blockers: Check metadata review status

Prerequisite readiness

Prerequisite readiness

3 prerequisites to line up before setup.

0/3 ready
Configuration1General2

Safety & privacy surface

Safety & privacy surface

3 safety and 3 privacy notes across 4 risk areas. Review closely: credentials & tokens.

4 areas
  • SafetyExecution & processesThis agent curates and reviews skills; it does not execute them.
  • SafetyGeneralRecommend tool restrictions (allowed-tools) for skills that touch sensitive actions, and invocation control for skills with side effects.
  • SafetyExecution & processesFlag skills whose descriptions could cause the model to auto-invoke them in inappropriate contexts.
  • PrivacyCredentials & tokensSkill descriptions load each session; keep sensitive workflow detail and secrets out of them.
  • PrivacyCredentials & tokensSkills sourced from outside the org should be reviewed before adoption, since their instructions run in your sessions.
  • PrivacyLocal filesUse settings-level overrides to hide or disable model-invocation of skills you did not author without editing their files.

Safety notes

  • This agent curates and reviews skills; it does not execute them.
  • Recommend tool restrictions (allowed-tools) for skills that touch sensitive actions, and invocation control for skills with side effects.
  • Flag skills whose descriptions could cause the model to auto-invoke them in inappropriate contexts.

Privacy notes

  • Skill descriptions load each session; keep sensitive workflow detail and secrets out of them.
  • Skills sourced from outside the org should be reviewed before adoption, since their instructions run in your sessions.
  • Use settings-level overrides to hide or disable model-invocation of skills you did not author without editing their files.

Prerequisites

  • A set of Agent Skills (personal, project, or plugin) with their SKILL.md files.
  • Knowledge of which skills should be org-wide versus project-specific.
  • Ability to edit skill frontmatter and settings such as skill overrides.

Schema details

Install type
copy
Troubleshooting
No
Skill and platform metadata
Retrieval sources
https://code.claude.com/docs/en/skillshttps://code.claude.com/docs/en/settings
Full copyable content
## Content

Agent Skills Enterprise Librarian Agent is a reusable agent prompt for curating an
organization's library of Agent Skills. It reviews SKILL.md quality, descriptions
and triggers, scope and precedence, tool restrictions, and invocation control so
skills are discoverable, consistent, and safe to roll out.

Use it when an organization accumulates many skills across personal, project, and
plugin scopes and needs a librarian to keep the collection healthy.

## Agent Prompt

You are an Agent Skills librarian for an organization using Claude Code. Curate
the skills library for quality, discoverability, and safety. Use the official
Claude Code skills documentation as your reference.

Review workflow:

1. Inventory. List skills and their scope (personal, project, plugin) and note
   precedence, since managed and user skills override project ones by name.
2. Descriptions. Confirm each SKILL.md has a clear description that states when to
   use it, so the model invokes the right skill and avoids overlap.
3. Invocation control. For skills with side effects, recommend disabling model
   invocation so only a user can trigger them.
4. Tool restrictions. Recommend allowed-tools scoping for skills that touch
   sensitive actions, so a skill cannot use more than it needs.
5. Duplication and conflicts. Find overlapping or redundant skills and propose
   consolidation; rely on plugin namespacing to avoid name conflicts.
6. Lifecycle. Recommend ownership, review cadence, and deprecation for stale
   skills.
7. Decision. Approve, request edits, or retire each skill.

Output contract:

- Skills inventory with scope and precedence.
- Findings: weak descriptions, missing invocation control, over-broad tools,
  duplication.
- Required changes with references to the skills docs.
- Curation decisions: keep, edit, consolidate, or retire.

## Features

- Inventories skills across personal, project, and plugin scope.
- Reviews descriptions and triggers for correct model invocation.
- Recommends invocation control and tool restrictions for safety.
- Finds duplication and proposes consolidation and lifecycle rules.

## Use Cases

- Curate a growing organizational Agent Skills library.
- Improve skill descriptions so the model picks the right one.
- Lock down side-effecting skills with invocation control.
- Consolidate duplicate skills and retire stale ones.

## Source Notes

- Claude Code skills use SKILL.md with frontmatter (description, invocation
  control, tool restrictions) and follow the Agent Skills open standard.
- Skills live at personal, project, and plugin scope; by name, managed overrides
  user overrides project, and plugin skills are namespaced. Settings can override
  a skill's visibility without editing its file.

## Duplicate Check

The content tree and open PRs were checked for skills governance, librarian, and
curation agents. No Agent Skills enterprise librarian exists. This entry is
distinct: it is an `agents` prompt focused on curating an organization's Agent
Skills library.

## Editorial Disclosure

Submitted as an independent community agent entry by `JPette1783`, based on
public Claude Code documentation. No paid placement, referral, or affiliate
relationship.

## Sources

- Claude Code skills documentation: https://code.claude.com/docs/en/skills
- Claude Code plugins documentation: https://code.claude.com/docs/en/plugins
- Claude Code features overview: https://code.claude.com/docs/en/features-overview

About this resource

Content

Agent Skills Enterprise Librarian Agent is a reusable agent prompt for curating an organization's library of Agent Skills. It reviews SKILL.md quality, descriptions and triggers, scope and precedence, tool restrictions, and invocation control so skills are discoverable, consistent, and safe to roll out.

Use it when an organization accumulates many skills across personal, project, and plugin scopes and needs a librarian to keep the collection healthy.

Agent Prompt

You are an Agent Skills librarian for an organization using Claude Code. Curate the skills library for quality, discoverability, and safety. Use the official Claude Code skills documentation as your reference.

Review workflow:

  1. Inventory. List skills and their scope (personal, project, plugin) and note precedence, since managed and user skills override project ones by name.
  2. Descriptions. Confirm each SKILL.md has a clear description that states when to use it, so the model invokes the right skill and avoids overlap.
  3. Invocation control. For skills with side effects, recommend disabling model invocation so only a user can trigger them.
  4. Tool restrictions. Recommend allowed-tools scoping for skills that touch sensitive actions, so a skill cannot use more than it needs.
  5. Duplication and conflicts. Find overlapping or redundant skills and propose consolidation; rely on plugin namespacing to avoid name conflicts.
  6. Lifecycle. Recommend ownership, review cadence, and deprecation for stale skills.
  7. Decision. Approve, request edits, or retire each skill.

Output contract:

  • Skills inventory with scope and precedence.
  • Findings: weak descriptions, missing invocation control, over-broad tools, duplication.
  • Required changes with references to the skills docs.
  • Curation decisions: keep, edit, consolidate, or retire.

Features

  • Inventories skills across personal, project, and plugin scope.
  • Reviews descriptions and triggers for correct model invocation.
  • Recommends invocation control and tool restrictions for safety.
  • Finds duplication and proposes consolidation and lifecycle rules.

Use Cases

  • Curate a growing organizational Agent Skills library.
  • Improve skill descriptions so the model picks the right one.
  • Lock down side-effecting skills with invocation control.
  • Consolidate duplicate skills and retire stale ones.

Source Notes

  • Claude Code skills use SKILL.md with frontmatter (description, invocation control, tool restrictions) and follow the Agent Skills open standard.
  • Skills live at personal, project, and plugin scope; by name, managed overrides user overrides project, and plugin skills are namespaced. Settings can override a skill's visibility without editing its file.

Duplicate Check

The content tree and open PRs were checked for skills governance, librarian, and curation agents. No Agent Skills enterprise librarian exists. This entry is distinct: it is an agents prompt focused on curating an organization's Agent Skills library.

Editorial Disclosure

Submitted as an independent community agent entry by JPette1783, based on public Claude Code documentation. No paid placement, referral, or affiliate relationship.

Sources

Source citations

Add this badge to your README

Show that Agent Skills Enterprise Librarian Agent is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/agents/agent-skills-enterprise-librarian-agent.svg)](https://heyclau.de/entry/agents/agent-skills-enterprise-librarian-agent)

How it compares

Agent Skills Enterprise Librarian Agent side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

2 trust signals differ across this comparison (Source provenance, Submitter).

Field

An agent prompt for curating an organization's Agent Skills: reviewing each SKILL.md name and description, scope (personal, project, or plugin) and precedence, per-skill allowed-tools, and whether Claude or the user invokes it.

Open dossier

Expert capability pack for reviewing Claude Code autoMode settings blocks, trusted infrastructure prose, classifier rule overrides, and documented claude auto-mode CLI inspection before enabling permission-free auto mode.

Open dossier

Expert Claude Code sandboxed bash policy capability pack applying documented /sandbox enablement, filesystem and network boundaries, autoAllowBashIfSandboxed review, and fail-closed settings for autonomous shell workflows.

Open dossier

Expert Claude Code deep links runbook capability pack for building safe claude-cli:// URLs, embedding them in incident runbooks, and validating cwd, repo, and prompt parameters before users press Enter.

Open dossier
Next steps
Trust
Review statusNot reviewedNot reviewedNot reviewedNot reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceDiffersSource-backedSubmission linkedSource submissionSubmission linkedSource submissionSubmission linkedSource submission
SubmitterDiffersJPette1783kiannidevkiannidevkiannidev
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
Brand
Categoryagentsskillsskillsskills
SourceSource-backedSource-backedSource-backedSource-backed
AuthorJPette1783kiannidevkiannidevkiannidev
Added2026-06-052026-06-162026-06-162026-06-13
Platforms
Harness
Source repo
Safety notesThis agent curates and reviews skills; it does not execute them. Recommend tool restrictions (allowed-tools) for skills that touch sensitive actions, and invocation control for skills with side effects. Flag skills whose descriptions could cause the model to auto-invoke them in inappropriate contexts.Omitting $defaults from autoMode arrays replaces entire built-in rule lists per docs. Developer-added allow entries can override organization soft_deny rules—use managed permissions.deny for non-negotiable blocks. Auto mode runs without routine permission prompts; permissions.deny still blocks before the classifier.Sandboxing reduces blast radius but does not replace human review of diffs. autoAllowBashIfSandboxed auto-approves some sandboxed commands—pair with deny rules. Missing dependencies can disable sandbox silently unless fail-closed settings apply. Network allowlists still permit egress to listed domains—document allowed hosts.Deep links pre-fill prompts but never auto-send; users must press Enter after reviewing the external-link warning. Untrusted pages can craft malicious prompts; treat every deep link like untrusted input until a human reviews it. Prompts over 1,000 characters show an extended warning; require scroll review before sending long links. Network and UNC paths are rejected for cwd; use absolute local paths or repo slugs instead. If both cwd and repo are passed, cwd wins even when the path does not exist; validate parameters deliberately. Organizations can disable handler registration with disableDeepLinkRegistration in settings or managed policy.
Privacy notesSkill descriptions load each session; keep sensitive workflow detail and secrets out of them. Skills sourced from outside the org should be reviewed before adoption, since their instructions run in your sessions. Use settings-level overrides to hide or disable model-invocation of skills you did not author without editing their files.autoMode.environment prose may describe internal hostnames and bucket names—redact external copies. Recently denied actions in /permissions may expose attempted commands—handle logs internally. Managed settings distribution exposes organization infrastructure descriptions to enrolled clients.Sandbox logs and permission prompts may capture command text and paths. Allowed write paths may include files with secrets—keep credentials out of sandbox scope. Policy summaries for external auditors should omit internal hostnames when possible.Deep link URLs embed prompt text in query parameters, which may expose incident details, customer names, or internal service names in browser history, chat logs, or ticketing systems. repo resolution uses the most recently used local clone path, which can reveal directory layout on shared screens via the welcome header. Runbooks pasted into GitHub-rendered Markdown lose clickable claude-cli:// links; code-block copies still expose full URLs to readers. Public runbooks should use redacted example prompts and generic repo slugs unless the audience is internal-only.
Prerequisites
  • A set of Agent Skills (personal, project, or plugin) with their SKILL.md files.
  • Knowledge of which skills should be org-wide versus project-specific.
  • Ability to edit skill frontmatter and settings such as skill overrides.
  • Permission to edit user, local, or managed settings with autoMode blocks.
  • Inventory of trusted source control orgs, buckets, and internal domains.
  • Security stakeholder for managed permissions.deny hard blocks.
  • Claude Code on macOS, Linux, or WSL with sandbox dependencies installable.
  • Permission to edit project or managed settings.json sandbox blocks.
  • Inventory of bash commands agents run in CI and local workflows.
  • Security stakeholder for production repository policy sign-off.
  • Claude Code v2.1.91 or later on the machines that will click or open the link.
  • At least one prior interactive Claude Code session on each target machine so the claude-cli:// handler registers.
  • For repo links, a local clone where Claude Code has been run at least once so the owner/name slug resolves.
  • Permission to review runbook text, alert templates, and the decoded prompt before users press Enter.
Install
Config
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.