agentleFS
NVIDIAKnown publisherNVIDIA/nemoclaw-community/examples/recipes/nvidia/developer-community-chief-of-staff/agents/hermes/skills/gitlab-readonly-live/SKILL.md

gitlab-readonly-live

Skill142 starsChanged 3 months agoApache-2.0View on GitHub

Read one of the configured GitLab projects through authenticated, policy-scoped REST GET requests.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 2 are distinctive, and 4 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.

  • 4

    Very specific

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

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

    Use this skill for current live data from the GitLab projects listed in $GITLAB_READONLY_PROJECTS.

    line 8
  2. Very specific:

    If there is one project, the helper selects it automatically.

    line 14
  3. Very specific:

    Do not use glab, git, alternate GitLab hosts, GraphQL, or custom requests.

    line 25
  4. Distinctive:

    Always invoke the bundled helper:

    line 29
  5. Very specific:

    Add --project group/project to any get command when more than one project is configured.

    line 37
  6. Distinctive:

    If OpenShell returns a policy 403, report the configured project and route scope.

    line 42

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

gitlab-readonly-live

Use this skill for current live data from the GitLab projects listed in $GITLAB_READONLY_PROJECTS.

Access model

  • The allowlist may contain multiple comma-separated projects.
  • If there is one project, the helper selects it automatically. With multiple projects, pass --project group/project explicitly.
  • Requests use the OpenShell provider placeholder from GITLAB_TOKEN. Never print or inspect that variable or any .env file.
  • Access is limited to GET requests for issues, merge requests, repository content and history, labels, milestones, and releases. Bare project metadata is excluded because GitLab may include sensitive fields for privileged users.
  • Authenticated-user metadata is also excluded because GitLab's current-user response can contain private identity, email, sign-in, and network details.
  • Membership, CI/CD variables, hooks, deploy tokens, runners, and every write method are outside policy.
  • Do not use glab, git, alternate GitLab hosts, GraphQL, or custom requests.

Procedure

Always invoke the bundled helper:

/usr/bin/python3 /sandbox/.hermes-data/skills/gitlab-readonly-live/scripts/gitlab_readonly.py get issues --param state=opened --paginate --count
/usr/bin/python3 /sandbox/.hermes-data/skills/gitlab-readonly-live/scripts/gitlab_readonly.py get merge_requests --param state=opened --paginate --fields iid,title,state,web_url
/usr/bin/python3 /sandbox/.hermes-data/skills/gitlab-readonly-live/scripts/gitlab_readonly.py get repository/tree --param recursive=true --paginate --limit 50 --fields name,path,type

Add --project group/project to any get command when more than one project is configured. Put query parameters in --param KEY=VALUE, not in the route. Use %2F for slashes inside a repository file-path segment, for example repository/files/docs%2Fguide.md.

If OpenShell returns a policy 403, report the configured project and route scope. Do not retry through a different host, binary, or endpoint.

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.