Behavior characterization
Skill andresnator/agents-orchestrator/skills/behavior-characterization
npx -y skills add andresnator/agents-orchestrator --skill behavior-characterizationAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Trigger: behavior characterization, observable behavior. Record what legacy code does today.
The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.3 KB, as published. Nobody here has run it
Behavior Characterization
Detect what the system does today without judging whether it is ideal.
Observable signals
- Return values.
- Exceptions and error codes.
- Side effects and state changes.
- Persistence writes/reads.
- Published events.
- Relevant logs.
- External calls.
- Edge conditions and branch behavior.
- Implicit business rules.
Every behavior claim needs code evidence or must be marked as a hypothesis.
Characterization method
- Write an assertion expected to fail, run it, and read the actual value from the failure message; anchor that value as the expected result. The test documents what the code does, not what it should do.
- Characterize only the zone the plan will touch (targeted characterization), not the whole unit by default.
Bugs found while characterizing
Characterize the bug as-is: the test anchors today's wrong output. Never fix it in the same step — record it, finish the safety net, and schedule the fix as a follow-up behavior change to run with the net in place.