agentleFS
roronoazoroshao369roronoazoroshao369/vibe-coding-os/skills/core/external-skill/SKILL.md

external-skill

Skill1 starsChanged 5 months agoMITView on GitHub

Example skill demonstrating the isolated sandbox-marker level. Use as a template when authoring third-party or marketplace skills. When you are about to install or reference a third-party skill from a marketplace or external source. This skill shows the canonical frontmatter pattern for sandbox.level: isolated.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 1 is distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When you are about to install or reference a third-party skill from a marketplace or external source.

    line 25
  2. Distinctive:

    Verify the marketplace URL matches an allowlisted source.

    line 35
  3. Very specific:

    Check the license (permissive/copyleft/proprietary).

    line 36
  4. Very specific:

    Run npm run validate:sandbox-marker to confirm compliance.

    line 38
  5. Very specific:

    Run npm run validate:injection to scan the imported content.

    line 39
  6. Very specific:

    Run vibe-license-surface to update the project's NOTICE file.

    line 40

≈ “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

Skill: External Skill (Example)

Purpose

Example skill demonstrating the isolated sandbox-marker level. Use as a template when authoring third-party or marketplace skills.

When to use

When you are about to install or reference a third-party skill from a marketplace or external source. This skill shows the canonical frontmatter pattern for sandbox.level: isolated.

Inputs

  • Marketplace URL
  • License metadata
  • Provenance chain (signatures, hashes)

Workflow

  1. Verify the marketplace URL matches an allowlisted source.
  2. Check the license (permissive/copyleft/proprietary).
  3. Apply sandbox: { level: isolated, isolation: network=block,fs=read-only,exec=none,audit=on }.
  4. Run npm run validate:sandbox-marker to confirm compliance.
  5. Run npm run validate:injection to scan the imported content.
  6. Run vibe-license-surface to update the project's NOTICE file.

Outputs

  • A sandboxed, licensed, audited external skill ready for use.

Failure modes

  1. Missing sandbox marker — gate FAIL. Apply the frontmatter above.
  2. Missing isolation policy — gate FAIL. isolated level requires isolation: field.
  3. Missing license — flag in NOTICE. Add license: to frontmatter.
  4. Provenance gap — refuse to import.

Verification checklist

  • Frontmatter has sandbox: { level: isolated, ... }
  • content_sources is a YAML list of source patterns
  • isolation: policy is set
  • validate:sandbox-marker exits 0
  • License is declared and compatible
  • Provenance is verified (signatures, hashes)
  • NOTICE file is updated via vibe-license-surface

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.