using-psters-workflow
Meta-skill for selecting and invoking the right workflow skill before acting; use when starting or switching task type to avoid bypassing required discipline.
Meta-skill for selecting and invoking the right workflow skill before acting; use when starting or switching task type to avoid bypassing required discipline.
Module Loop and Iteration Skill for orchestrating multi-phase penetration testing workflows. Use when coordinating sequential tool execution, managing dependencies between reconnaissance and vulnerability scanning modules, implementing adaptive fallback strategies, or managing workflow state across iterations. Triggers on tasks requiring dependency chaining (e.g., Nmap results feeding into Nuclei), adaptive workflow adjustments based on results, or stateful iteration management to avoid redundant scans.
Create a GitHub deployment for the current branch using the deploy-review workflow
Provides comprehensive guidance for GitLab CI/CD including pipeline configuration, runners, artifacts, environments, and deployment automation. Use when the user asks about GitLab CI, needs to create pipelines, configure runners, or automate builds and deployments.
Install and configure nvm in Docker containers and CI/CD pipelines, including non-interactive shell loading via BASH_ENV or ENTRYPOINT. Use when the user asks about nvm in Docker, CI/CD nvm setup, GitHub Actions node version management, or troubleshooting nvm in non-interactive shells.
Skill to merge upstream master into a local branch following rebranding rules.
Use when a ClawdStrike lane branch is ready for review and integration and needs verification, scope-drift checks, shared-file wiring, and merge-gate enforcement before landing.
Use when specs are mature enough to split work into parallel ClawdStrike lanes with explicit ownership, dependency graphs, verification gates, merge order, and agent briefs.
Use this skill when the user says 'CI/CD', 'GitHub Actions', 'pipeline', 'continuous integration', 'continuous deployment', 'ci-cd-pipeline', 'automate deploys', or needs to set up automated build, test, and deployment pipelines. Do NOT use for one-time manual deployments.
Validate a plan or spec before implementation using multi-model council. Answer: Is this good enough to implement? Triggers: "pre-mortem", "validate plan", "validate spec", "is this ready".
Use when you have 2+ tasks that Codex agents should execute. Runtime-native: Codex sub-agents when available, Codex CLI fallback otherwise. Handles file conflicts via merge/wave strategies. Triggers: "codex team", "spawn codex", "codex agents", "use codex for", "codex fix".
Wrap up completed work. Council validates the implementation, then extract and process learnings. Triggers: "post-mortem", "wrap up", "close epic", "what did we learn".
Meta skill explaining the AgentOps operating model. Hook-capable runtimes inject it at session start; Codex uses it through the explicit startup fallback. Covers bookkeeping, validation, primitives, flows, the RPI lifecycle, and the skill catalog.
Standardized setup for new Go (Golang) projects and services. Activate to ensure clean, idiomatic project structures (Standard Layout) and implement production-ready patterns (graceful shutdown, package separation) from day one.
Real-time source of truth for software and model versions. Activate when adding dependencies, installing packages, or identifying Gemini model names. Bypasses internal knowledge cutoffs by querying live registries (NPM, PyPI, Go Proxy) and official documentation.
Configures Model Armor security policies (Prompt Injection, Jailbreak, RAI filters).
Expert-level ArgoCD GitOps deployment, application management, sync strategies, and production operations
Use when you have a written implementation plan to execute in a separate session with review checkpoints