Score story changes against acceptance criteria in a read-only session.
npx skills add https://github.com/memorysaver/SIBYL --skill sibyl-story-eval
Please help me install this Agent Skill. Skill: sibyl-story-eval Source: https://github.com/memorysaver/SIBYL/tree/main/apps/harness/skills/sibyl-story-eval Command: npx skills add https://github.com/memorysaver/SIBYL --skill sibyl-story-eval
This Skill provides a structured process for evaluating story changes in a software development environment, ensuring that changes meet specified criteria before they are accepted.
As an evaluator, initiate the sibyl-story-eval skill to review the latest story change and provide your assessment by calling submit_eval with the appropriate result and scores.
High-intent search queries and answers about installing and using this skill.
You can evaluate code changes against acceptance criteria by running a read-only review session that scores story changes across Completeness, Correctness, Security, and Code-Quality on a 1 to 5 scale.
Automating story review involves applying a deterministic PASS rule to the change surface and submitting dimensional scores via a structured evaluation process to ensure software quality and requirements compliance.
Yes, story evaluation operates in a separate, read-only session to maintain strict separation from the change generator, ensuring an objective code review without altering the original environment.
You score code review completeness and security by initiating an evaluation session and calling the submission function with results that rate the story change on defined quality dimensions from 1 to 5.
You need a separate story evaluation process when you want to verify that story changes meet specified acceptance criteria before acceptance, applying a deterministic PASS rule to the change surface to ensure quality.
The deterministic PASS rule requires a comprehensive review of the change surface and mandates specific dimensional scores, meaning any incomplete evaluation or failing score will block the story change from being accepted.
bketelsenEvaluate delivered work against predefined success metrics and acceptance criteria.
HellblazerAccept RDRs after gate pass and update frontmatter status.
ChrstprJohnApply Clean Architecture and Domain-Driven Design principles to software projects.
R2W1csLint and validate JavaScript and Python code for syntax and style issues.
