Index of every page on this site: llms.txt
All skills
pingdotgg avatar

/ci-maintenance

@b5453de
by Ping.ggpingdotgg/t3code67k stars
11,639
Run it yourself

GitHub Actions maintenance. Use when authoring or reviewing workflows or composite actions, especially event, permission, action-reference, artifact, setup, or concurrency changes.

  • 2 files
  • 3.7 KB
  • Updated 2 months ago
  • GitHub
Use this Skill: https://skilld.dev/gh/pingdotgg/t3code/ci-maintenance

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈49 tokens for metadata: the name and description. ≈622 when used: this file. ≈263 more on demand in 1 file.

Description uses 2.5% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈197 characters, or 2.5%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Audit the trust boundary before editing. This skill owns Actions event semantics, workflow security, permissions, action pinning, setup reuse, untrusted inputs, timeouts, concurrency, and artifact trust boundaries.

Workflow

  1. Decide whether this is a review or an implementation. Reviews produce evidence-backed findings without editing; implementations continue through the smallest boundary-preserving change.
  2. Inspect every affected workflow, composite action, and caller. List all affected jobs and actions before proceeding.
  3. For each job, record the trigger, actor/fork status, workflow revision, checked-out revision, permissions, credentials, and every external input and consumer. Include artifacts, caches, outputs, PR fields, refs, dispatch inputs, generated files, and called actions.
  4. Consult current GitHub documentation for every platform-sensitive decision. Repository examples establish local convention, not platform semantics.
  5. Apply every applicable rule:
    • Default workflow permissions to empty and grant minimal job permissions.
    • Reuse the repository's shared setup action unless the environment must differ.
    • Give executable jobs intentional matrices and realistic timeouts.
    • Pin external actions and reusable workflows to full commit SHAs with readable release comments; verify each SHA belongs to that upstream release.
    • Analyze event choice, checkout revision, and credential persistence together.
    • Pass untrusted expressions through environment variables; validate and quote them before use.
    • Derive concurrency from interruption safety.
  6. For forks, privileged credentials, publication, or cross-run data, read privileged-workflows.md.
  7. Run the narrowest syntax and repository checks, inspect the complete diff, and identify behavior testable only on GitHub-hosted runners.

For local patterns, inspect the current shared setup action and the nearest workflow with the same trust boundary. Use ordinary check workflows for routine precedent and privileged publication workflows only for equivalent trust boundaries.

The task is complete when every affected job and caller has a recorded trust boundary, every applicable rule has evidence or a compensating control, local checks pass, and GitHub-only verification is identified. Reviews report every failure with evidence; implementations resolve every failure and contain only intended behavior.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at b5453de. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 months ago

README badge

README badge for pingdotgg/t3code/ci-maintenance