Approved submission is not persisted when database save fails

[gregkonush]

I tried submitting https://github.com/proompteng/bilig through the public submit API/page.

The validation step passed:

• repo: proompteng/bilig
• stars: 23
• license: MIT
• language: TypeScript
• has README: true

The submit call returned HTTP 200 and success: true, with the automated review approving it at 36/40. The response included this warning though:

"warning": "Skill created but database save failed"

The returned skill slug was proompteng-bilig, but searching the public skills page for bilig still returns an empty result set.

Expected: approved submissions are persisted and show up in search/listing.
Actual: API returns success/approved, but the skill is not visible because persistence appears to fail.

This repo now includes a root skill at skills/bilig-workpaper/SKILL.md, so it should be ingestible by SKILL.md registries.

[Leon-Drq]

Thanks for the detailed report, and apologies for the delayed response. You found a real persistence bug.

This has now been fixed in production. Reviewed submissions use the controlled submit_reviewed_skill database flow, and the API only returns success: true after it receives a persisted skill record. If the database save fails, the endpoint now returns HTTP 500 with success: false and code: "SAVE_FAILED", instead of reporting a successful submission with a warning.

The original proompteng/bilig submission was not persisted, so its old skill URL is still unavailable. The repository now has 34 GitHub stars and meets the current 10-star submission requirement. Please resubmit it here:

https://www.openagentskill.com/submit

It should appear in the registry after a successful response. If it still does not, reply here with the approximate submission time and we will trace that request. We'll keep this issue open until the resubmission is confirmed.