agentleFS
Sign inStart free
euisuheuisuh/nginx-proxy-manager-mcp/skills/nginx-proxy-manager/SKILL.md

nginx-proxy-manager

Skill2 starsChanged 4 months agoMITView on GitHub

Manage Nginx Proxy Manager hosts, HTTPS certificates, streams, and access lists through the configured NPM MCP tools with request previews and user approval.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. hoktaar/claude-skills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use these tools when the user asks to expose an app, inspect routing, manage certificates, or change streams or access lists in NPM.

    line 6
  2. Very specific:

    Use create_proxy_host_with_letsencrypt for new HTTPS hosts.

    line 18
  3. Distinctive:

    Never delete without explicit user confirmation naming the resource and ID.

    line 19
  4. Distinctive:

    Never request credentials in chat.

    line 20
  5. Very specific:

    If the HTTPS workflow fails, report failed_step and any created certificate.

    line 21

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Use these tools when the user asks to expose an app, inspect routing, manage certificates, or change streams or access lists in NPM. The MCP server must already be configured for the intended NPM instance.

Rules

  • List the relevant resources before an update; verify the target ID and current state.
  • For every mutation, always call with dry_run=True first.
  • Show the complete request preview (method, path, and json if present).
  • For workflows, show every preview in steps before requesting approval.
  • Apply only after the user approves the shown preview, using the same arguments with dry_run=False. Changed arguments require a new preview and approval.
  • Use create_proxy_host_with_letsencrypt for new HTTPS hosts.
  • Never delete without explicit user confirmation naming the resource and ID.
  • Never request credentials in chat; use the server's configured credentials.
  • If the HTTPS workflow fails, report failed_step and any created certificate; do not retry blindly or delete the certificate without explicit confirmation.

Example

User: “expose app on port 3000 at blog.example.com”. With upstream app call create_proxy_host_with_letsencrypt with domain_names=["blog.example.com"], forward_scheme="http", forward_host="app", forward_port=3000, and dry_run=True (NPM before 2.13 also needs a user-approved email). Show both previews. Apply only after user OK.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free