Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →ontology-of-everything/concept-refine
Analyzes and refines existing software concepts.
Passed 20 of 24 test cases with the skill, and 18 of 24 without it.
2 fixed18 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
Our user management domain model currently has 'UserProfile', 'AccountDetails', and 'IdentityContext' classes, but developers are confused about where specific state and actions belong. Could you inspect our conceptual model, evaluate potential issues like overloading or redundancy using concrete usage scenarios, and provide a structured proposal showing recommended minimal adjustments (such as splitting, merging, or leaving unchanged) along with the expected costs, benefits, and impact scope?
| Checked | Without skill | With skill |
|---|---|---|
| Labels unconfirmed domain assumptions using explicit inference tags. | Missed | Passed |
| Includes operational principles for the analyzed concepts. | Passed | Passed |
| Evaluates structural choices mapped to identified root causes. | Passed | Passed |
The instructions your model reads when the skill loads.
Make the smallest necessary change that helps a concept or concept system fulfill its purpose. Read requirements, specifications, and relevant code; reconstruct purpose, state, actions, operational principle, and synchronizations. Use actual scenarios and counterexamples to investigate overloading, redundancy, excessive narrowness, fragmentation, and under/over-synchronization. Compare split/merge, unify/specialize, and tighten/loosen against the root cause, keeping no change as an option and explaining benefits, costs, and scope of impact. Investigate facts yourself and label inferences. Discuss consequential choices kindly in rounds, only when their prerequisites are settled; give recommendations and reasons. Once the approach is settled, complete authorized changes, distinguishing preserved behavior from intentional changes. Synchronizations must respect concept contracts; verify both local purposes and end-to-end scenarios. Stop when the agreed goal is met without known major regressions, and identify anything not verified.
Before selecting moves, read moves and evidence.
test cases passed, vs 18 / 24 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.