Serviceradar Bazel Guardrails
carverauto/serviceradar
Use before creating a worktree, script, or ad hoc orchestration, handling generated Bazel artifacts, changing native add-ons, or adding serviceradarcore tests.
Start or resume a requested Guardrails implementation or PR takeover in the selected linked worktree with bounded scope and verification.
Install Implementation Kickoff
$ npx skills add openai/openai-guardrails-js --skill implementation-kickoff -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install openai/openai-guardrails-js implementation-kickoff --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/openai/openai-guardrails-js.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/implementation-kickoff .claude/skills/implementation-kickoff && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "implementation-kickoff" agent skill from https://github.com/openai/openai-guardrails-js/tree/main/.agents/skills/implementation-kickoff into .claude/skills/implementation-kickoff/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementation-kickoff", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/openai/openai-guardrails-js/tree/main/.agents/skills/implementation-kickoffType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add openai/openai-guardrails-js --skill implementation-kickoff -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install openai/openai-guardrails-js implementation-kickoff --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openai/openai-guardrails-js.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/implementation-kickoff .agents/skills/implementation-kickoff && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "implementation-kickoff" agent skill from https://github.com/openai/openai-guardrails-js/tree/main/.agents/skills/implementation-kickoff into .agents/skills/implementation-kickoff/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementation-kickoff", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add openai/openai-guardrails-js --skill implementation-kickoff -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install openai/openai-guardrails-js implementation-kickoff --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openai/openai-guardrails-js.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/implementation-kickoff .cursor/skills/implementation-kickoff && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "implementation-kickoff" agent skill from https://github.com/openai/openai-guardrails-js/tree/main/.agents/skills/implementation-kickoff into .cursor/skills/implementation-kickoff/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementation-kickoff", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/openai/openai-guardrails-js.git --path .agents/skills/implementation-kickoff--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add openai/openai-guardrails-js --skill implementation-kickoff -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install openai/openai-guardrails-js implementation-kickoff --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openai/openai-guardrails-js.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/implementation-kickoff .gemini/skills/implementation-kickoff && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "implementation-kickoff" agent skill from https://github.com/openai/openai-guardrails-js/tree/main/.agents/skills/implementation-kickoff into .gemini/skills/implementation-kickoff/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementation-kickoff", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install openai/openai-guardrails-js implementation-kickoffInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add openai/openai-guardrails-js --skill implementation-kickoff -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/openai/openai-guardrails-js.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/implementation-kickoff .github/skills/implementation-kickoff && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "implementation-kickoff" agent skill from https://github.com/openai/openai-guardrails-js/tree/main/.agents/skills/implementation-kickoff into .github/skills/implementation-kickoff/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementation-kickoff", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add openai/openai-guardrails-js --skill implementation-kickoff -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install openai/openai-guardrails-js implementation-kickoff --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openai/openai-guardrails-js.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/implementation-kickoff .opencode/skills/implementation-kickoff && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "implementation-kickoff" agent skill from https://github.com/openai/openai-guardrails-js/tree/main/.agents/skills/implementation-kickoff into .opencode/skills/implementation-kickoff/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementation-kickoff", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
implementation-kickoff- GitHub stars
- 104
- Token cost
- ~1k tokens
- SKILL.md length
- 531 words
- Files
- 2
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- MIT
At a glance
Start or resume a requested Guardrails implementation or PR takeover in the selected linked worktree with bounded scope and verification.
- Tasks that involve Git worktrees
- SKILL.md covers Establish the checkout and scope, Take over an existing PR, Implement and verify and Handoff
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Tasks that involve LLM guardrails
What it does
Implementation Kickoff is an agent skill from openai/openai-guardrails-js, published by the product's own GitHub organization. Start or resume a requested Guardrails implementation or PR takeover in the selected linked worktree with bounded scope and verification.
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in AI & LLM Engineering, covering Git worktrees and LLM guardrails. The repository describes itself as: OpenAI Guardrails - TypeScript / JavaScript. The licence is MIT.
When your agent uses it
- Tasks that involve Git worktrees
- Tasks that involve LLM guardrails
Example prompts
- “/implementation-kickoff”
What it can do on your machine
Read from SKILL.md and the folder at commit 8e88be0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Implementation Kickoff loads about 1k tokens when it runs. Until then it costs about 40 tokens; SKILL.md has 531 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from openai/openai-guardrails-js at commit 8e88be0, republished under its MIT licence (© openai). 531 words, ~1,016 tokens.
Download SKILL.mdSave it as
.claude/skills/implementation-kickoff/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- implementation-kickoff
- description
- Start or resume a requested Guardrails implementation or PR takeover in the selected linked worktree with bounded scope and verification.
Implementation Kickoff
Start from the user's actual implementation request. An investigation or a plan alone is not permission to implement, push, or publish. Preserve authorization already given; this skill adds none. Apply AGENTS.md and implementation-strategy where applicable.
Establish the checkout and scope
Record the original outcome, acceptance criteria, affected paths, non-goals, and intended base. Reuse the current task's selected linked worktree. If running in a primary checkout, follow AGENTS.md and ask to start or hand off to a worktree. Do not automatically create another worktree or change unrelated checkouts.
Refresh remote references and record the full intended starting SHA. For a new independent task use the refreshed default branch unless the user chose another base. For an explicitly requested stack, use the exact previous slice's tip. Verify the checkout equals that SHA before editing a new task. For a resumed task, preserve its existing changes and record HEAD plus the original comparison base instead of resetting it to main. Stop on an unexplained base mismatch.
Inspect tracked and untracked state before edits. Keep task deliverables distinct
from existing user work and operational plans/review notes. Use codex/ branch
names by default, preserving an explicitly selected branch or user preference.
Take over an existing PR
Read current metadata, author commits, discussions, and the complete PR diff. Confirm the PR is still an appropriate source. Preserve its underlying outcome, but evaluate the proposal against the current architecture and toolchain. Import only the accepted scope; a takeover does not require copying the entire patch or preserving intermediate commits.
Record the source PR and verified author/coauthor identities. Credit adapted
work with valid Co-authored-by trailers, without inventing identities. If the
identity needed for attribution cannot be verified, resolve it before committing.
For a split takeover, describe each slice as part of the replacement effort;
do not claim the first slice completes the whole source PR.
Show full SKILL.md (222 more words)Show less
Implement and verify
Keep changes within the agreed scope. Preserve user work and avoid automatic stashing, rebasing, or rewriting unrelated branches. Check integration with an advanced target before submission; if an update is needed, handle only this task's branch and rerun checks/review affected by any content change. Do not force a detached checkout, one-commit topology, or history rewrite to manufacture a clean handoff.
Use verification and final review before pushing or creating or updating a PR. Follow the release guide: ordinary user-visible SDK changes need a changeset; internal workflow changes need none. Leave version and changelog generation to the release PR.
Handoff
Use pr-draft-summary for the final description and authorized submission/follow-up.
Inspect status, full diff statistics, and every task commit before staging or reporting. Stage only task-owned deliverables; keep local planning and review artifacts out of the PR. Preserve hooks and inspect the committed result.
Report branch, base, commit, requested outcome, verification, review status, and remaining blockers. When authorized to submit, follow AGENTS.md for current-head CI monitoring, scoped fixes, root-channel review requests, and feedback replies. For a requested stack, create each PR against its predecessor and verify that relationship. Do not assume all workflows run on feature-branch PR targets: inspect triggers and use an authorized manual CI run on each head when needed. Never merge or close the source PR without authorization.
© openai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in .agents/skills/implementation-kickoff of openai/openai-guardrails-js.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit 8e88be0
Compare with similar skills
Implementation Kickoff next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Implementation Kickoff this skillopenai/openai-guardrails-js | 104 | — | ~1k | Automated safety check: Pass | MIT | |
| Serviceradar Bazel Guardrailscarverauto/serviceradar | 921 | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Explore Codelllllllama/RigorPilot-Skills | 497 | 1 repos | ~648 | Automated safety check: Pass | MIT | |
| AI Coding Agent Guardrailssickn33/agentic-awesome-skills | 47k | 2 repos | ~3.3k | Automated safety check: Notes | MIT | |
| AI Native CLIsickn33/agentic-awesome-skills | 47k | 2 repos | ~3.3k | Automated safety check: Pass | MIT | |
| Hivemindalirezarezvani/claude-skills | 28k | — | ~2.4k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Explore Code
lllllllama/RigorPilot-Skills
Rigor Improve implementation leaf skill for auditable candidate implementation in deep learning research repositories.
AI Coding Agent Guardrails
sickn33/agentic-awesome-skills
Secure AI coding agents (Claude Code, Cursor, Codex, Copilot) with permission boundaries, secret protection, code review gates, and safe sandbox configurations for team environments.
AI Native CLI
sickn33/agentic-awesome-skills
Design spec with 98 rules for building CLI tools that AI agents can safely use.
Hivemind
alirezarezvani/claude-skills
Orchestrate free opencode workers from Claude Code to cut token costs.
Manor Coding Guardrails
manor-os/manor-ai
A skill your agent uses when writing, reviewing, or refactoring Manor code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
More from openai/openai-guardrails-js
- Official
Code Change Verification
openai/openai-guardrails-js
Select and run Guardrails verification for code, dependency, test, tooling, documentation, or repository-workflow changes.
- Official
Implementation Final Review
openai/openai-guardrails-js
Prepare independent review of a complete Guardrails change before pushing or updating a PR, using the repository adversarial-review procedure.
- Official
Implementation Strategy
openai/openai-guardrails-js
Choose bounded implementation scope and existing owning modules before Guardrails runtime, configuration, client, resource, streaming, Agents, or SDK compatibility changes and feedback fixes.
- Official
PR Draft Summary
openai/openai-guardrails-js
Draft a Guardrails PR from its complete final diff and carry out authorized CI and review follow-up, including stacked PRs and takeovers.
Related
Categories
Questions about Implementation Kickoff
What does Implementation Kickoff do?
Start or resume a requested Guardrails implementation or PR takeover in the selected linked worktree with bounded scope and verification. Implementation Kickoff is an agent skill from openai/openai-guardrails-js, published by the product's own GitHub organization. Start or resume a requested Guardrails implementation or PR takeover in the selected linked worktree with bounded scope and verification.
When should I use Implementation Kickoff?
Implementation Kickoff fits situations like: tasks that involve Git worktrees; tasks that involve LLM guardrails.
How do I install Implementation Kickoff in Claude Code?
Run `npx skills add openai/openai-guardrails-js --skill implementation-kickoff -a claude-code`. Or copy the skill folder (.agents/skills/implementation-kickoff in openai/openai-guardrails-js) into .claude/skills/implementation-kickoff in your project. Claude Code loads it when a task matches its description.
How do I install Implementation Kickoff in Codex?
Run `npx skills add openai/openai-guardrails-js --skill implementation-kickoff -a codex`. Or copy the skill folder (.agents/skills/implementation-kickoff in openai/openai-guardrails-js) into .agents/skills/implementation-kickoff in your project. Codex loads it when a task matches its description.
Can I use Implementation Kickoff in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add openai/openai-guardrails-js --skill implementation-kickoff -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/implementation-kickoff, .gemini/skills/implementation-kickoff, .github/skills/implementation-kickoff and .opencode/skills/implementation-kickoff in your project.
What does Implementation Kickoff need to run?
SKILL.md names no scripts, command-line tools or credentials: Implementation Kickoff is instructions for the agent only.
Does Implementation Kickoff access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Implementation Kickoff safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Implementation Kickoff use?
Implementation Kickoff is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Implementation Kickoff use?
About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Implementation Kickoff?
Skills that share tags, products or a category with Implementation Kickoff: Serviceradar Bazel Guardrails (carverauto/serviceradar, 921 stars), Explore Code (lllllllama/RigorPilot-Skills, 497 stars), AI Coding Agent Guardrails (sickn33/agentic-awesome-skills, 47k stars) and AI Native CLI (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Implementation Kickoff?
openai (a GitHub organization, an official publisher) maintains it in openai/openai-guardrails-js, which has 104 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on September 28, 2026.
Source: openai/openai-guardrails-js on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.