Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →sonichi/submit-use-case
OSS-facing channel to share a Sutando use case with the community. Opens a labeled GitHub issue on sonichi/sutando and (CLA-gated) a PR adding docs/community-use-cases/<slug>.md. Validates outcome-framed titles with the same checker as add-use-case. Default: both; flags --issue-only / --pr-only opt out.
Passed 16 of 19 test cases with the skill, and 6 of 19 without it.
and 13 more in the full report
12 fixed7 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
When an issue is automatically created in sonichi/sutando for a new submission, what label is attached to it for maintainer triage?
| Checked | Without skill | With skill |
|---|---|---|
| Applies label use-case-submission. | Missed | Passed |
The instructions your model reads when the skill loads.
OSS counterpart to add-use-case. add-use-case targets the private
AG2Platform/agent-universe repo (rendered on sutando.ai) and is for the
internal fleet. submit-use-case targets the public sonichi/sutando repo
so external contributors can share a use case without needing access to the
private rendering repo.
python3 "$SKILL_DIR/scripts/submit_use_case.py" \
--title "Your AI plays piano while you sleep" \
--summary "Outcome-first summary that appears on tile + detail page." \
--bullets "bullet1" --bullets "bullet2" \
[--video /abs/path/to/clip.mp4] \
[--media-url https://example.com/clip.jpg] \
[--youtube-id ABCDEFG1234] \
[--x-url https://x.com/...] \
[--linkedin-url https://www.linkedin.com/...] \
[--contact "[email protected] or @yourhandle"] \
[--issue-only | --pr-only] \
[--dry-run]
--dry-run runs the framing check and prints both the rendered issue body
and the rendered docs/community-use-cases/<slug>.md file to stdout. No clone, no
gh calls.
REJECT_PATTERNS + validate_title +
suggest_reframes from add-use-case verbatim. Capability-listy titles
("Ask your AI to ...", "Sutando can ...", "Send a ...") are rejected with
deterministic reframe suggestions. Same rules, same voice.slugify(title) — lowercased, non-alphanum→-, trimmed to 60 chars.--dry-run):
community-use-case/<slug> already exist on sonichi/sutando?
If yes, abort with a pointer to the existing PR.sonichi/sutando with the same title? If yes,test cases passed, vs 6 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.