regocpp-builtins Skill
Add, update, or remove OPA Rego built-in functions in rego-cpp. Use when: implementing a new builtin, replacing a placeholder with a real implementation, adding a new OPA builtin namespace, updating builtin declarations to match a new OPA version, removing deprecated builtins, or debugging builtin dispatch/registration Published by microsoft in rego-cpp.
Decision snapshot
Is this a fit?
Developers using rego-cpp, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
2 months ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is regocpp-builtins Skill?
Add, update, or remove OPA Rego built-in functions in rego-cpp. Use when: implementing a new builtin, replacing a placeholder with a real implementation, adding a new OPA builtin namespace, updating builtin declarations to match a new OPA version, removing deprecated builtins, or debugging builtin dispatch/registration Published by microsoft in rego-cpp. 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 rego-cpp
Declared skill metadata
- Source file: .github/skills/regocpp-builtins/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 regocpp-builtins Skill
- Use it for developers using rego-cpp.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/rego-cpp
- Skill file: .github/skills/regocpp-builtins/SKILL.md
What it does
Add, update, or remove OPA Rego built-in functions in rego-cpp. Use when: implementing a new builtin, replacing a placeholder with a real implementation, adding a new OPA builtin namespace, updating builtin declarations to match a new OPA version, removing deprecated builtins, or debugging builtin dispatch/registration
Skill instructions
rego-cpp Built-in Function Development Add, update, and remove OPA Rego built-in functions in rego-cpp. When to Use - Implementing a new builtin (replacing a placeholder or adding from scratch) - Adding a new OPA builtin namespace (new src/builtins/<namespace.cc file) - Updating builtin declarations to track a new OPA version - Replacing placeholder stubs with real implementations - Removing deprecated builtins - Debugging builtin dispatch or registration issues Architecture Overview Built-in functions follow a three-layer architecture: BuiltInsDef::lookup(name) ← Dispatch layer (src/builtins.cc) → builtins::<namespace(name) ← Namespace router (src/builtins/<ns.cc) → <functionfactory() ← Factory (returns BuiltIn with decl + behavior) → <function(args) ← Implementation (unwrap args, compute, return) Key Files | File | Purpose | |------|---------| | src/builtins/builtins.hh | Namespace dispatch function declarations | | src/builtins.cc | BuiltInsDef::lookup — hand-coded binary dispatch t
Verified compatibility and discovery
Frequently asked questions
What is regocpp-builtins?
regocpp-builtins is a open-source AI agent skill with Copy skill directory. Add, update, or remove OPA Rego built-in functions in rego-cpp. Use when: implementing a new builtin, replacing a placeholder with a real implementation, adding a new OPA builtin namespace, updating.
Who is regocpp-builtins best for?
regocpp-builtins is best for reusing agent instructions, scripts, and references.
How do I install regocpp-builtins?
Install or run regocpp-builtins using Copy skill directory. Check regocpp-builtins for the latest setup command.
Is regocpp-builtins actively maintained?
regocpp-builtins 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.
