trieste-dev Skill
Plan and implement Trieste-based compiler passes and AST transformations for rego-cpp. Use when: adding new compiler passes, modifying AST structure, implementing new Rego language features, debugging pass failures, working with well-formedness definitions, or performing any multi-step implementation that touches the T 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 trieste-dev Skill?
Plan and implement Trieste-based compiler passes and AST transformations for rego-cpp. Use when: adding new compiler passes, modifying AST structure, implementing new Rego language features, debugging pass failures, working with well-formedness definitions, or performing any multi-step implementation that touches the T 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/trieste-dev/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 trieste-dev Skill
- Use it for developers using rego-cpp.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/rego-cpp
- Skill file: .github/skills/trieste-dev/SKILL.md
What it does
Plan and implement Trieste-based compiler passes and AST transformations for rego-cpp. Use when: adding new compiler passes, modifying AST structure, implementing new Rego language features, debugging pass failures, working with well-formedness definitions, or performing any multi-step implementation that touches the T
Skill instructions
Trieste Development Workflow Plan and implement Trieste-based compiler passes, AST transformations, and language features in rego-cpp. When to Use - Adding or modifying a compiler pass in the file-to-rego or rego-to-bundle pipeline - Implementing new Rego language syntax (new tokens, grammar rules) - Changing well-formedness definitions - Debugging pass failures or well-formedness violations - Implementing complex multi-step features that touch the AST pipeline - Any task requiring coordination across parser, passes, built-ins, and VM Core Concepts Trieste is a multi-pass term-rewriting system. Understanding these concepts is mandatory before proceeding: - Pass: A PassDef that takes an AST conforming to an input well-formedness (WF) definition and rewrites it to conform to an output WF definition. Passes run repeatedly until no more rules match (fixpoint), unless dir::once is specified. - Well-formedness (WF): A structural specification of valid AST shapes. Each pass declares its outpu
Verified compatibility and discovery
Frequently asked questions
What is trieste-dev?
trieste-dev is a open-source AI agent skill with Copy skill directory. Plan and implement Trieste-based compiler passes and AST transformations for rego-cpp.
Who is trieste-dev best for?
trieste-dev is best for reusing agent instructions, scripts, and references.
How do I install trieste-dev?
Install or run trieste-dev using Copy skill directory. Check trieste-dev for the latest setup command.
Is trieste-dev actively maintained?
trieste-dev 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.