How to use
- Copy the installation command and review the source package before installing it in your own agent environment.
- Check the source document for required tools, credentials and supported hosts.
- Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/leek/agent-skills --skill verifyBefore you start
- Installation does not include a model subscription, API allowance or permission to access your files.
- Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document
Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.
Verify
Tests passing is not the finish line. Exercise the actual flow once, in the running application, and report what you observed: never what should happen.
Process
- Pick the flow the change owns. The route a user would hit, the command an operator would run, the job the system would dispatch, the Filament/Livewire page a back-office user would open. One realistic pass; this is not a test suite.
- Run it for real.
- HTTP / UI: the app is served (Herd serves Laravel apps at
https://<dir>.test: never start a server that's already running). Use the project's browser tooling (agent-browser, Boost'sbrowser-logs) to load the page, perform the action, and screenshot the result. - Console: run the artisan command with realistic arguments.
- Jobs / listeners: dispatch through the real path (
dispatchSyncor trigger the event), then check the side effect where it lands, database rows, storage, logs.
- Check the seams the tests can't see. Before driving the flow, watch them under
Monitorwhere available:tail -f storage/logs/laravel.log | grep --line-buffered -E 'ERROR|CRITICAL|Exception', plusphp artisan queue:workwhen a queued job is involved, so each error arrives tied to the action that caused it. Otherwise read the log tail after each action. Look for browser console errors, the Laravel log (storage/logs/or Boost'sread-log-entries/last-error), a queue that needed a running worker, an unbuilt frontend (a Vite manifest error means runnpm run build, not that the change is broken). - Report faithfully. What you did, what you saw (status codes, redirects, rendered state, rows written), and anything that surprised you: with the evidence. If a step couldn't be exercised (needs credentials, a webhook, a human), say so plainly instead of marking it verified. List each screenshot's path, so a PR opened later can embed it.
Guardrails
- Verify against local/dev: never run mutating flows against a real environment's data without explicit approval.
- Leave no residue: throwaway records created during verification get cleaned up, or created under an obviously-fake identity the seeds already use.
