agentleFS
Sign inStart free
opendatahub-ioopendatahub-io/docs-skills/skills/validate-plugin-prereqs/SKILL.md

validate-plugin-prereqs

Skill4 starsChanged 4 months agoApache-2.0View on GitHub

Check that all environment variables and CLI tools required by the docs-skills plugin are available. Use when setting up a new environment, troubleshooting missing prerequisites, or before running a workflow for the first time.

  • Pipes a download into a shell
  • Reads credentials

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Run the prerequisite checker:

    line 8
  2. Distinctive:

    If any required items are missing, tell the user what's needed and how to fix it:

    line 16
  3. Very specific:

    GITHUB_TOKEN: Add to ~/.env or .env. Needed for GitHub-based skills (git-pr-reader, understand-pull-request).

    line 19
  4. Very specific:

    GITLAB_TOKEN: Add to ~/.env or .env. Needed only for GitLab-based repositories.

    line 20

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

Validate plugin prerequisites

Run the prerequisite checker:

bash ${CLAUDE_SKILL_DIR}/scripts/validate_prereqs.sh

The script loads ~/.env and ./.env, then checks all required and optional environment variables and CLI tools. It prints a human-readable table and exits with code 0 (all required items present) or 1 (something missing).

If any required items are missing, tell the user what's needed and how to fix it:

  • JIRA_API_TOKEN / JIRA_EMAIL: Add to ~/.env or .env. Required for JIRA-related skills (jira-reader, jira-writer, create-jira, jira-ready).
  • GITHUB_TOKEN: Add to ~/.env or .env. Needed for GitHub-based skills (git-pr-reader, understand-pull-request).
  • GITLAB_TOKEN: Add to ~/.env or .env. Needed only for GitLab-based repositories.
  • python3: Install Python 3.10+.
  • uv: Install with curl -LsSf https://astral.sh/uv/install.sh | sh.
  • git: Install via system package manager.
  • jq: Install via system package manager.
  • gh: Install from https://cli.github.com/.
  • glab: Install from https://gitlab.com/gitlab-org/cli. Required for GitLab workflows (create-merge-request, git-pr-reader).
  • vale: Install from https://vale.sh/docs/install/. Optional — only needed for style review skills.
  • shellcheck / ruff: Optional dev/CI tools.

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