snap-o / host
openai/snap-o/tool-sdk/host/AGENTS.md
No summary in the file. Open it to read it.
One search for your own team's files and the public ecosystem. See how real projects write their agent instructions, and bring the good ideas home.
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
openai/snap-o/tool-sdk/host/AGENTS.md
No summary in the file. Open it to read it.
openai/openai-guardrails-js/AGENTS.md
Monitor PR CI. Fix only introduced/worsened failures or narrowly necessary corrections; report unrelated failures and retry transient/flaky checks when appropriate. After CI passes, request review in root #sdk-reviews, never a thread. For feedback fixes, push, explain the correction in the review comment, then resolve it. Before implementation/review, define the requested outcome, acceptance criteria, affected paths/tests, and non-goals. Justify every changed file and behavior. Classify findings: (1) introduced/worsened defect, (2) narrowly necessary correction, (3) unrelated preexisting defect, (4) broader improvement, or…
openai/openai-guardrails-js/.agents/skills/code-change-verification/SKILL.md
Select and run Guardrails verification for code, dependency, test, tooling, documentation, or repository-workflow changes.
openai/openai-guardrails-js/.agents/skills/implementation-final-review/SKILL.md
Prepare independent review of a complete Guardrails change before pushing or updating a PR, using the repository adversarial-review procedure.
openai/openai-guardrails-js/.agents/skills/implementation-kickoff/SKILL.md
Start or resume a requested Guardrails implementation or PR takeover in the selected linked worktree with bounded scope and verification.
openai/openai-guardrails-js/.agents/skills/implementation-strategy/SKILL.md
Choose bounded implementation scope and existing owning modules before Guardrails runtime, configuration, client, resource, streaming, Agents, or SDK compatibility changes and feedback fixes.
openai/openai-guardrails-js/.agents/skills/pr-draft-summary/SKILL.md
Draft a Guardrails PR from its complete final diff and carry out authorized CI and review follow-up, including stacked PRs and takeovers.
openai/redcard/AGENTS.md
This repo is designed to be opened in the ChatGPT macOS app and operated through Codex. The normal Codex activation path is the repo-owned $redcard skill. Red Card watches for a physical red card through the webcam. When detected during a Google Meet call, it runs the full sequence: The default entrypoint is: The default config is: The README is the public handoff. Once the user asks for help setting up, running, or debugging Red Card, Codex should become the…
openai/redcard/codex-skill/redcard/SKILL.md
Install, diagnose, and run the self-contained Red Card runtime through Codex in the ChatGPT macOS app from any task or project. Use when the user invokes $redcard or asks Codex to install, configure, troubleshoot, or run Red Card. Codex owns every shell command and requests scoped outside-sandbox execution for installation, dependency downloads, and real runs that need macOS hardware or app access; the user only handles required approval, macOS, Chrome, and Google-account UI actions.
openai/openai-developers-for-claude/plugins/openai-developers/skills/agents-sdk/SKILL.md
Use when the user wants to build, adapt, run, or evaluate an OpenAI Agents SDK app from Claude Code. Prefer a docs-first workflow and route API credential decisions through openai-platform-api-key before API-backed work.
Often used withnextjs-on-cloudflaresandbox-sdkbasin
openai/openai-developers-for-claude/plugins/openai-developers/skills/build-chatgpt-app/SKILL.md
Use when the user explicitly wants a ChatGPT App, Apps SDK project, MCP server plus widget UI, ChatGPT-compatible tool UI, or submission/deployment work for that surface. Build, scaffold, refactor, or troubleshoot those projects from Claude Code, consult openai-docs before generating code, and use openai-platform-api-key before any app path that requires live OpenAI API credentials.
openai/openai-developers-for-claude/plugins/openai-developers/skills/chatgpt-app-submission/SKILL.md
Use when a developer needs a ChatGPT Apps submission import file from an MCP server. Inspect the implementation, generate chatgpt-app-submission.json with app info, tool-hint justifications, positive and negative test cases, then report review findings and outputSchema warnings.
openai/openai-developers-for-claude/plugins/openai-developers/skills/openai-docs/SKILL.md
Use whenever the user asks anything about OpenAI products, APIs, models, or SDKs — including factual lookups, coding requests, latest/current/default model selection, prompting guidance, model upgrades, and citation requests. Invoke before calling any openaiDeveloperDocs MCP tool.
openai/homebrew-tools/AGENTS.md
This is the openai/tools Homebrew tap. It distributes generated Ruby recipes for prebuilt tools; it does not contain their application source or generators. Read and follow CONTRIBUTING.md and SECURITY.md before making changes. The recipe and upstream inventory is in Generated recipes. - Before editing, state the requested outcome, acceptance criteria, affected paths, and non-goals. Keep changes limited to that outcome; ask before changing public interfaces, crossing ownership boundaries, or restructuring architecture. - Use a linked Git worktree, verify its intended…
openai/community-plugins/AGENTS.md
These conventions apply throughout this repository and reflect the maintainer's preferred organization. Follow the existing Grafana, ReviewOps and React Native to SwiftUI plugins when adding or changing a plugin. - Keep each installable package in plugins/<plugin-name>/. Repository companion tests belong in tests/<plugin-name>/, with unit/, integration/, security/ and support/ directories where applicable. Existing deeper package suites should remain connected to the root master command. - Provide one canonical root npm run test:<plugin-name> command that runs the complete automated suite: package, functional,…
openai/community-plugins/plugins/autodesk-fusion/skills/create-fusion-deliverables/SKILL.md
Stage and verify Fusion exports, drawing PDFs, flat-pattern DXF, viewport images and local renders. Use for engineering deliverables, not automatic publication or release.
openai/community-plugins/plugins/autodesk-fusion/skills/edit-fusion-design/SKILL.md
Prepare, execute and verify authorized Fusion CAD changes using resolved entities, explicit units and state-bound plans. Use for reviewed parameter, sketch, feature, assembly or configuration operations.
openai/community-plugins/plugins/autodesk-fusion/skills/handoff-fusion-engineering/SKILL.md
Prepare a traceable local Fusion engineering review draft with source identities, artifacts and unresolved assurance gates. Not for sending, publication or release approval.
openai/community-plugins/plugins/autodesk-fusion/skills/inspect-fusion-design/SKILL.md
Inspect an explicit Fusion design, parameters, geometry, references, configuration and health without editing it. Use for model understanding or engineering audits.
openai/community-plugins/plugins/autodesk-fusion/skills/prepare-fusion-manufacturing/SKILL.md
Prepare qualified Fusion CAM setups, operations, toolpaths and quarantined NC candidates using explicit manufacturing assets and authority. Never controls physical equipment.
Plain text files in a repository that tell a coding agent how the project works: commands to run, conventions to follow and things to avoid. CLAUDE.md, AGENTS.md, cursor rules and skills are the common kinds.
CLAUDE.md is read by Claude Code. AGENTS.md is an open format that Codex, Cursor and other agents read. Many projects keep one and point the other at it.
A folder with a SKILL.md that describes one capability, such as filling PDFs or reviewing code. The agent loads it only when the task calls for it.
Your agents already can, over MCP, limited to the files you're allowed to read. Searching them from this page is coming.