Let people delete a skill or playbook they no longer need #286

Skills and playbooks can be created and imported but never removed in the app, so a wrong import or an old playbook stays in the list for good, even though the delete API already exists.

Where to start

1. Add Delete to the skill detail dialog and the playbook detail, using the shared InlineDeleteConfirm.
2. Call deleteSkill from skills-api.ts (it exists and nothing calls it), then refresh the list and close the dialog.
3. Show a plain error line if the delete fails.

Code to look at:

• frontend/app/(library)/skills/skills-api.ts:75
• frontend/app/(library)/skills/skill-detail-dialog.tsx:195
• frontend/app/(library)/playbooks/playbook-detail.tsx:177
• frontend/components/shared/inline-delete-confirm.tsx:10
• backend/src/skills/routes.ts:222

Done when

• Deleting a skill and a playbook removes them from their lists, and they stay gone after a reload.
• Cancel leaves the item untouched, and a test covers the confirm and the list refresh.

Free to try

Sign up free at app.useagent.org. New accounts get free model credits (GLM or Claude Opus, up to a limit) and free cloud sandbox time, enough to finish this task without paying or adding a key.

Send it a small task in plain words and watch it work. You'll see the screens this issue is about. The link in the sign-up email works for 24 hours. Not there? Check spam.

Stuck? Comment here with a screenshot and we'll help.

Keep private details out of here

This page is public. Don't post your real email, phone number, address, payment details, API keys, or screenshots that show any of them. Send anything private, including how you'd like to be paid, to hi@useagent.org with a link to your comment here.

Claim it

Comment /take and the issue is assigned to you. First come, first served.

Rules

• Use the app while you work, and put before and after screenshots or a short recording in your pull request. For backend or docs work, show the result end to end.
• One change per pull request. Run the checks in CONTRIBUTING.md.
• AI help is fine, blind AI output is not. You must understand, run and explain every line you submit.
• Untested or generated pull requests, and pull requests on an issue someone else claimed, are closed without a reply and don't count for Hacktoberfest.