Persona Design
kangarooking/system-prompt-skills
当需要为 AI 产品定义核心身份、角色声明和能力边界时调用此 skill。典型场景包括：设计新 AI 产品的 system prompt 首段、为不同场景创建差异化角色（如教学助手 vs 编程代理）、重新定义 AI 与用户的关系框架。
Choose bounded implementation scope and existing owning modules before Guardrails runtime, configuration, client, resource, streaming, Agents, or SDK compatibility changes and feedback fixes.
Install Implementation Strategy
$ npx skills add openai/openai-guardrails-js --skill implementation-strategy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install openai/openai-guardrails-js implementation-strategy --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-strategy .claude/skills/implementation-strategy && 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-strategy" agent skill from https://github.com/openai/openai-guardrails-js/tree/main/.agents/skills/implementation-strategy into .claude/skills/implementation-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementation-strategy", 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-strategyType 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-strategy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install openai/openai-guardrails-js implementation-strategy --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-strategy .agents/skills/implementation-strategy && 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-strategy" agent skill from https://github.com/openai/openai-guardrails-js/tree/main/.agents/skills/implementation-strategy into .agents/skills/implementation-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementation-strategy", 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-strategy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install openai/openai-guardrails-js implementation-strategy --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-strategy .cursor/skills/implementation-strategy && 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-strategy" agent skill from https://github.com/openai/openai-guardrails-js/tree/main/.agents/skills/implementation-strategy into .cursor/skills/implementation-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementation-strategy", 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-strategy--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-strategy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install openai/openai-guardrails-js implementation-strategy --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-strategy .gemini/skills/implementation-strategy && 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-strategy" agent skill from https://github.com/openai/openai-guardrails-js/tree/main/.agents/skills/implementation-strategy into .gemini/skills/implementation-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementation-strategy", 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-strategyInstalls 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-strategy -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-strategy .github/skills/implementation-strategy && 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-strategy" agent skill from https://github.com/openai/openai-guardrails-js/tree/main/.agents/skills/implementation-strategy into .github/skills/implementation-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementation-strategy", 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-strategy -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-strategy --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-strategy .opencode/skills/implementation-strategy && 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-strategy" agent skill from https://github.com/openai/openai-guardrails-js/tree/main/.agents/skills/implementation-strategy into .opencode/skills/implementation-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementation-strategy", 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-strategy- GitHub stars
- 105
- Token cost
- ~951 tokens
- SKILL.md length
- 413 words
- Files
- 2
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- MIT
At a glance
Choose bounded implementation scope and existing owning modules before Guardrails runtime, configuration, client, resource, streaming, Agents, or SDK compatibility changes and feedback fixes.
- Tasks that involve LLM guardrails
- SKILL.md covers Find the owning boundary and Match tests to the changed…
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Implementation Strategy is an agent skill from openai/openai-guardrails-js, published by the product's own GitHub organization. Choose bounded implementation scope and existing owning modules before Guardrails runtime, configuration, client, resource, streaming, Agents, or SDK compatibility changes and feedback fixes.
Its SKILL.md is about 950 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 LLM guardrails. It works with OpenAI. The repository describes itself as: OpenAI Guardrails - TypeScript / JavaScript. The licence is MIT.
When your agent uses it
- Tasks that involve LLM guardrails
Example prompts
- “/implementation-strategy”
What it can do on your machine
Read from SKILL.md and the folder at commit d28dc28. 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 Strategy loads about 951 tokens when it runs. Until then it costs about 54 tokens; SKILL.md has 413 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 d28dc28, republished under its MIT licence (© openai). 413 words, ~951 tokens.
Download SKILL.mdSave it as
.claude/skills/implementation-strategy/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- implementation-strategy
- description
- Choose bounded implementation scope and existing owning modules before Guardrails runtime, configuration, client, resource, streaming, Agents, or SDK compatibility changes and feedback fixes.
Implementation Strategy
Before implementation or a feedback fix, record the requested outcome, acceptance criteria, affected paths, compatibility requirements, and non-goals. Apply scope discipline. An issue's suggested implementation is evidence, not an approved API design.
Find the owning boundary
Read the repository map and SDK migration guide. Use existing configuration, validation, registry, conversation, and resource pipelines. Identify whether the affected contract is a public export, declaration, configuration format, request/response shape, exception, CLI option, or internal helper. Compare ownership changes against the intended PR base; consult a verified release tag separately when evaluating released compatibility. Report an unavailable or stale release baseline rather than treating branch-only behavior as a released guarantee.
| Boundary | Preserve and inspect |
|---|---|
| OpenAI/Azure clients | Async create factories, separate check client, caller options and credentials, and initialized guarded clones from withOptions() |
| Resources | Chat/Responses parameters and request options, SDK-compatible types, and the explicit guardrails namespace; do not imply every inherited SDK method is guarded |
| OpenAI 7 | Native Fetch Response/Headers, provider-specific options, and inherited SDK method contracts |
| Zod 4 | Existing schemas and their owning validation boundary; GuardrailSpec.schema() returns the definition, not JSON Schema |
| Agents | Public @openai/agents imports, built CommonJS behavior, session history, and preflight guards blocking model dispatch |
| Pipeline | pre_flight, input, output ordering and each integration's documented execution model; distinguish tripwires from execution errors |
| Streaming and history | Resource-specific output checks, conversation ordering and roles, tool-call identity, masking, and output error policy |
Do not add new guarded SDK methods, normalize omitted options into arbitrary defaults, or duplicate schema/conversation conversion just to accommodate a suggested implementation. Escalate a substantive public API or architecture change before expanding the diff.
Show full SKILL.md (149 more words)Show less
Match tests to the changed contract
Use existing unit tests beside the owning area. For SDK boundaries, inspect
src/__tests__/integration/sdk-compat.test.ts, sdk-types.test.ts, and
sdk-migration-feedback.test.ts: they cover built-package behavior and consumer
types that source-only mocks can miss. Build before running these tests. Use
Vitest mocks/spies or SDK-provided testing utilities where they model the real
protocol. Add only tests needed for the changed behavior.
For a touched security surface, review the relevant trust boundary: untrusted configuration, provider responses, conversation content, or eval inputs, and where validation occurs before side effects. Keep this review scoped to the change; do not convert it into unrelated hardening.
Classify feedback using AGENTS.md. Fix introduced/worsened defects and narrowly necessary corrections. Record broader improvements separately. If repeated special cases suggest the approach fights an existing invariant, revisit the smallest design at the owning boundary before adding more machinery.
Use code-change-verification for checks and the release guide for changeset impact.
© 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-strategy of openai/openai-guardrails-js.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit d28dc28
Compare with similar skills
Implementation Strategy 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 Strategy this skillopenai/openai-guardrails-js | 105 | — | ~951 | Automated safety check: Pass | MIT | |
| Persona Designkangarooking/system-prompt-skills | 205 | 1 repos | ~956 | Automated safety check: Pass | MIT | |
| Safety Guardrailskangarooking/system-prompt-skills | 205 | — | ~1.2k | Automated safety check: Pass | MIT | |
| AI Engineerkid-sid/claude-spellbook | 189 | — | ~3.7k | Automated safety check: Pass | MIT | |
| Ak Dev New Guardrail Provideryaalalabs/agent-kernel | 191 | — | ~3.5k | Automated safety check: Pass | Apache-2.0 | |
| Migrating Openai Agents SDK To Pydantic AIpydantic/pydantic-ai | 20k | — | ~1.8k | Automated safety check: Pass | MIT |
Similar skills
Safety Guardrails
kangarooking/system-prompt-skills
当需要为 AI 系统设计多层安全防线、内容过滤策略和伦理边界时调用此 skill。典型场景包括：设计拒绝策略与升级机制、防御 prompt 注入攻击、实现领域特定安全规则（教育、医疗、金融等）、定义 AI 的价值观锚点。
AI Engineer
kid-sid/claude-spellbook
A skill your agent uses when building production LLM applications — designing RAG pipelines, choosing vector databases, implementing agent orchestration, optimizing cost, or adding AI safety…
Ak Dev New Guardrail Provider
yaalalabs/agent-kernel
Step-by-step guide for adding a new guardrail provider to Agent Kernel.
- Official
Migrating Openai Agents SDK To Pydantic AI
pydantic/pydantic-ai
Migrate Python OpenAI Agents SDK applications to Pydantic AI and, when warranted, Pydantic AI Harness.
Openai Agents
majiayu000/claude-skill-registry
Build AI applications with OpenAI Agents SDK - text agents, voice agents, multi-agent handoffs, tools with Zod schemas, guardrails, and streaming.
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 Kickoff
openai/openai-guardrails-js
Start or resume a requested Guardrails implementation or PR takeover in the selected linked worktree with bounded scope and verification.
- 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
Works with
Categories
Questions about Implementation Strategy
What does Implementation Strategy do?
Choose bounded implementation scope and existing owning modules before Guardrails runtime, configuration, client, resource, streaming, Agents, or SDK compatibility changes and feedback fixes. Implementation Strategy is an agent skill from openai/openai-guardrails-js, published by the product's own GitHub organization. Choose bounded implementation scope and existing owning modules before Guardrails runtime, configuration, client, resource, streaming, Agents, or SDK compatibility changes and feedback fixes.
When should I use Implementation Strategy?
Implementation Strategy fits situations like: tasks that involve LLM guardrails.
How do I install Implementation Strategy in Claude Code?
Run `npx skills add openai/openai-guardrails-js --skill implementation-strategy -a claude-code`. Or copy the skill folder (.agents/skills/implementation-strategy in openai/openai-guardrails-js) into .claude/skills/implementation-strategy in your project. Claude Code loads it when a task matches its description.
How do I install Implementation Strategy in Codex?
Run `npx skills add openai/openai-guardrails-js --skill implementation-strategy -a codex`. Or copy the skill folder (.agents/skills/implementation-strategy in openai/openai-guardrails-js) into .agents/skills/implementation-strategy in your project. Codex loads it when a task matches its description.
Can I use Implementation Strategy 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-strategy -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-strategy, .gemini/skills/implementation-strategy, .github/skills/implementation-strategy and .opencode/skills/implementation-strategy in your project.
What does Implementation Strategy need to run?
SKILL.md names no scripts, command-line tools or credentials: Implementation Strategy is instructions for the agent only.
Does Implementation Strategy 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 Strategy 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 Strategy use?
Implementation Strategy 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 Strategy use?
About 951 tokens (SKILL.md is roughly 3.8k 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 Strategy?
Skills that share tags, products or a category with Implementation Strategy: Persona Design (kangarooking/system-prompt-skills, 205 stars), Safety Guardrails (kangarooking/system-prompt-skills, 205 stars), AI Engineer (kid-sid/claude-spellbook, 189 stars) and Ak Dev New Guardrail Provider (yaalalabs/agent-kernel, 191 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Implementation Strategy?
openai (a GitHub organization, an official publisher) maintains it in openai/openai-guardrails-js, which has 105 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 8, 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.