agentsclimarketplace

Github actions workflow design

Skill planifest/planifest-framework/planifest-framework/external-skills/github-actions-workflow-design

A specification framework for agentic development. Agents build from complete specs - not guesses.

Install
npx -y skills add planifest/planifest-framework --skill github-actions-workflow-design

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Design and maintain GitHub Actions workflows with explicit trigger scope, security boundaries, and reliable job orchestration. Use when GitHub automation (build/test/release jobs, triggers, permissions, caching, concurrency, environments) must be created or revised; do not use for non-GitHub runtime architecture or data-layer design.

SKILL.md

2.3 KB, as published. Nobody here has run it

Github Actions Workflow Design

Overview

Use this skill to design CI/CD workflows that are secure, debuggable, and aligned with repository protection policy.

Scope Boundaries

  • Use this skill when the task matches the trigger condition described in description.
  • Do not use this skill when the primary task falls outside this skill's domain.

Shared References

  • Permissions matrix:
    • references/actions-permissions-matrix.md
  • Reusable snippet examples:
    • references/workflow-snippets.md

Templates And Assets

  • Workflow topology template:
    • assets/workflow-topology-template.md
  • Workflow design checklist:
    • assets/workflow-design-checklist.md

Inputs To Gather

  • Required checks and branch protection policy.
  • Build/test/deploy responsibilities and runtime matrix.
  • Secret handling policy and environment separation.
  • Expected runtime budget and failure triage expectations.

Deliverables

  • Workflow topology with explicit triggers and job dependencies.
  • Permission model per job and environment.
  • Cache/artifact strategy with invalidation notes.
  • Verification checklist for PR and protected branch runs.

Workflow

  1. Define topology in assets/workflow-topology-template.md.
  2. Scope triggers to required events and branches only.
  3. Split jobs by responsibility and assign least-privilege permissions.
  4. Add cache/concurrency controls and environment protection.
  5. Validate with assets/workflow-design-checklist.md.

Quality Standard

  • Required checks exactly match branch protection gates.
  • Job permissions are minimal and explicit.
  • Workflow runtime and cache behavior are observable.
  • Failure output is actionable for on-call and contributors.

Failure Conditions

  • Stop when trigger scope can cause unsafe or noisy execution.
  • Stop when deploy job permissions are broader than required.
  • Escalate when workflow design conflicts with repository governance.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.