agentleFS
avivsinaiavivsinai/jenkins-cli/skills/jk/SKILL.md

jk

Skill98 starsChanged 8 months agoMITView on GitHub

Manage Jenkins controllers with jk, including jobs, runs, logs, artifacts, credentials, nodes, queues, and plugins.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    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. Very specific:

    Use jk for Jenkins reads and changes.

    line 12
  2. Distinctive:

    Read only the rule that matches the request:

    line 18
  3. Distinctive:

    Test reports: rules/test.md

    line 25
  4. Distinctive:

    Use the active context unless the user names another controller.

    line 37
  5. Very specific:

    Prefer structured output (--json or --yaml) when another tool or script will consume the result.

    line 39
  6. Distinctive:

    Treat job configuration, credentials, nodes, plugins, queue cancellation, and run deletion as state-changing operations.

    line 43
  7. Distinctive:

    Never print, store, or echo Jenkins tokens or credential secrets.

    line 46
  8. Distinctive:

    Do not weaken TLS verification unless the user explicitly chooses that risk.

    line 48
  9. Distinctive:

    Use the relevant rule file before composing a write command.

    line 63

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

Jenkins CLI

Use jk for Jenkins reads and changes. Inspect jk --help or a subcommand's help when syntax is uncertain. Check installation or version only when the command is unavailable or a requested feature has a known minimum version.

Route the task

Read only the rule that matches the request:

  • Authentication and SSO: rules/auth.md
  • Saved controllers and context selection: rules/context.md
  • Jobs, folders, configuration, and scans: rules/job.md
  • Runs, parameters, reruns, and logs: rules/run.md
  • Artifacts: rules/artifact.md
  • Test reports: rules/test.md
  • Credentials: rules/cred.md
  • Nodes: rules/node.md
  • Queue: rules/queue.md
  • Plugins: rules/plugin.md
  • Other administrative commands: rules/other.md

For exact flags and output modes, search references/commands.md for the subcommand.

Shared operating rules

  • Use the active context unless the user names another controller. Verify the target context before a state-changing or security-sensitive operation.
  • Prefer structured output (--json or --yaml) when another tool or script will consume the result.
  • Inspect a job's declared parameters before starting a parameterized run; do not guess names or values.
  • Treat job configuration, credentials, nodes, plugins, queue cancellation, and run deletion as state-changing operations. Show the resolved target and follow the user's authorization.
  • Never print, store, or echo Jenkins tokens or credential secrets. Browser SSO access tokens are not Jenkins API tokens; follow rules/auth.md.
  • Do not weaken TLS verification unless the user explicitly chooses that risk.

Common reads

jk job ls
jk job view team/app
jk run ls team/app
jk run view team/app 128
jk log team/app 128 --follow
jk artifact ls team/app 128
jk test report team/app 128
jk queue ls

Use the relevant rule file before composing a write command.

References

<!-- auto-generated by cmd/docgen — do not edit below this line -->
  • artifact — Work with run artifacts
  • auth — Authenticate with Jenkins instances
  • context — Manage Jenkins contexts
  • cred — Manage Jenkins credentials
  • job — Manage Jenkins jobs and pipelines
  • node — Inspect and manage Jenkins nodes
  • plugin — Inspect and manage Jenkins plugins
  • queue — Inspect the build queue
  • run — Interact with job runs
  • test — Inspect test results
  • other — log, search, version
<!-- end auto-generated -->

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.