ingesting-spec Skill
Guide for ingesting the latest OpenAI TypeSpec specification into the openai-dotnet SDK. Use this when asked to update or ingest OpenAI API specs, copy base TypeSpec files from upstream, fix client TSP compile errors, or run code generation for new API areas. Published by openai in openai-dotnet.
Decision snapshot
Is this a fit?
Developers using openai-dotnet, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
28 days ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is ingesting-spec Skill?
Guide for ingesting the latest OpenAI TypeSpec specification into the openai-dotnet SDK. Use this when asked to update or ingest OpenAI API specs, copy base TypeSpec files from upstream, fix client TSP compile errors, or run code generation for new API areas. Published by openai in openai-dotnet. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Developers using openai-dotnet
Declared skill metadata
- Source file: .github/skills/ingesting-spec/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use ingesting-spec Skill
- Use it for developers using openai-dotnet.
Built with
Editorial notes
Source
- Creator: openai
- Repository: openai/openai-dotnet
- Skill file: .github/skills/ingesting-spec/SKILL.md
What it does
Guide for ingesting the latest OpenAI TypeSpec specification into the openai-dotnet SDK. Use this when asked to update or ingest OpenAI API specs, copy base TypeSpec files from upstream, fix client TSP compile errors, or run code generation for new API areas.
Skill instructions
Spec Ingestion Overview This skill describes how to ingest the latest OpenAI TypeSpec specification (from the upstream microsoft/openai-openapi-pr repository) into the openai-dotnet SDK, area by area. The process involves: 1. Copying updated base specs from upstream (exact copy, no modifications) 2. Reporting any compile errors in the base TSP (do NOT fix — base spec must stay unmodified) 3. Fixing compile errors in the client TSP layer 4. Preserving custom C code (renames, stubs) 5. Running code generation 6. Verifying the output Skill Documents This skill is split across multiple files for easier navigation: | Document | Description | |----------|-------------| | steps.md | Step-by-step process — the full 9-step workflow from copying spec to post-generation verification | | file-locations.md | Key file locations — quick reference for all upstream and local paths, area mappings | | patterns-and-gotchas.md | Common patterns & gotchas — lessons learned, pitfalls, and conventions to foll
Verified compatibility and discovery
Frequently asked questions
What is ingesting-spec?
ingesting-spec is a open-source AI agent skill with Copy skill directory. Guide for ingesting the latest OpenAI TypeSpec specification into the openai-dotnet SDK.
Who is ingesting-spec best for?
ingesting-spec is best for reusing agent instructions, scripts, and references.
How do I install ingesting-spec?
Install or run ingesting-spec using Copy skill directory. Check ingesting-spec for the latest setup command.
Is ingesting-spec actively maintained?
ingesting-spec may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
