orc-evaluate
FreeSet up LLM-as-judge evaluation for ORC workflows
The English summary is being prepared. Showing the original description.
19 skills (repositories by ObneyAI) · sorted by popularity
Set up LLM-as-judge evaluation for ORC workflows
The English summary is being prepared. Showing the original description.
Set up GEPA prompt optimization for an ORC workflow
The English summary is being prepared. Showing the original description.
Create scheduled background jobs that run on cron schedules
The English summary is being prepared. Showing the original description.
Implement query handlers that read from event-sourced read models
The English summary is being prepared. Showing the original description.
Build read models by reducing events into queryable state
The English summary is being prepared. Showing the original description.
Define Malli schemas for commands, events, and queries using defschemas
The English summary is being prepared. Showing the original description.
Create a complete Grain domain service with schemas, read models, commands, queries, and tests
The English summary is being prepared. Showing the original description.
Implement event-driven side effects that react to domain events
The English summary is being prepared. Showing the original description.
Connect to the project's nREPL server using the nrepl MCP tool
The English summary is being prepared. Showing the original description.
Give your AI agents something more useful than a prompt. Velocity through clarity.
The English summary is being prepared. Showing the original description.
Extract an Allium specification from an existing codebase. Use when the user has existing code and wants to distil behaviour into a spec, reverse engineer a specification from implementation, generate a spec from code, turn implementation into a behavioural specification, or document what a codebase does in Allium terms.
The English summary is being prepared. Showing the original description.
Run a structured discovery session to build an Allium specification through conversation. Use when the user wants to create a new spec from scratch, elicit or gather requirements, capture domain behaviour, specify a feature or system, define what a system should do, or is describing functionality and needs help shaping it into a specification.
The English summary is being prepared. Showing the original description.
Tend the Allium garden. Use when the user wants to write, edit, update, add to, improve, clarify, refine, restructure, fix or migrate Allium specs. Covers adding entities, rules, triggers, surfaces and contracts, fixing syntax or validation errors, renaming or refactoring within specs, migrating specs to a new language version, and translating requirements into well-formed specifications. Pushes back on vague requirements.
The English summary is being prepared. Showing the original description.
Implement command handlers that validate state and emit events using the Grain framework
The English summary is being prepared. Showing the original description.
Run the E2E QA test suite against the live application using Playwright MCP and nREPL. Use when testing the app end-to-end.
The English summary is being prepared. Showing the original description.
Build an ORC behavior tree workflow using the DSL
The English summary is being prepared. Showing the original description.
Run the project test suite using Polylith's poly test command
The English summary is being prepared. Showing the original description.
Generate tests from Allium specifications. Use when the user wants to propagate tests, generate test files from a spec, write tests for a specification, create property-based tests, produce state machine tests, check test coverage against spec obligations, or understand what tests a specification requires.
The English summary is being prepared. Showing the original description.
Weed the Allium garden. Find where Allium specifications and implementation code have diverged, and help resolve the divergences. Use when the user wants to check spec-code alignment, compare specs against implementation, audit for spec drift or violations, sync specs with code or code with specs, or verify whether the implementation matches what the spec says.
The English summary is being prepared. Showing the original description.