agentsclimarketplace
Sign in

Exception handling and logging

Skill soden46/syarif-laravel-ai-skills/skills/exception-handling-and-logging

Laravel guidance to use reportable/renderable exceptions, structured logs, and channel strategy for observability and graceful failuresFrom its SKILL.md

Install
npx -y skills add soden46/syarif-laravel-ai-skills --skill exception-handling-and-logging

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.0 KB, 353 tokens by cl100k_base, as published. Nobody here has run it

Exception Handling And Logging

Use this skill when a Laravel task involves exception handling and logging.

This skill is adapted to the personal Laravel standards in this repository. It maps the public exception-handling-and-logging topic from jpcaparas/superpowers-laravel into the local exception-handling-and-logging catalog without copying third-party skill body text.

Syarif Defaults

  • Follow Laravel conventions before introducing custom abstractions.
  • Prefer project-local patterns when they are explicit and tested.
  • Keep controllers focused on HTTP orchestration.
  • Put validation, authorization, transactions, side effects, and integrations at clear boundaries.
  • Keep client names, credentials, internal URLs, provider secrets, and project-specific business rules out of reusable standards.
  • Verify important behavior with the smallest meaningful tests and quality checks.

Workflow

  1. Detect the Laravel version, PHP version, runner, package manager, and existing project conventions.
  2. Identify the smallest local skill set that overlaps this topic.
  3. Implement or review the change using Laravel-native APIs first.
  4. Add abstractions only when they reduce real complexity or protect a meaningful boundary.
  5. Run targeted tests and available quality checks before handoff.

Checkpoints

  • Authorization and validation boundaries are explicit.
  • Query shape, transactions, queues, cache, files, and external calls are intentional when touched.
  • User-facing behavior has feature, unit, browser, or integration tests at the right level.
  • Logs and errors are useful without exposing secrets or unnecessary personal data.
  • Documentation or proposals avoid importing source-project names or one-off business rules.

Related Skills

  • using-laravel-standards
  • architecture
  • testing
  • security

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most log analysis skills give in 353 tokens

Counted across 325 of the 341 authors here whose files we hold, read 2026-09-06

  • Use structured JSON loggingin 32 of 325, across 30 files
  • Link every alert to a runbookin 15 of 325, across 13 files
  • Alert on symptoms, not causesin 11 of 325, across 10 files
  • Include correlation IDs in every log linein 10 of 325
  • Propagate trace context across service boundariesin 9 of 325, across 8 files
  • Include request IDs for correlationin 8 of 325, across 6 files
  • Include trace_id in every structured log entryin 8 of 325, across 7 files
  • Include request and user context in every log entryin 8 of 325
  • Correlate logs and traces with shared trace IDin 7 of 325, across 6 files
  • Record exceptions and set span status on errorsin 7 of 325
  • Confirm connection is ACTIVE before running workflowsin 6 of 325, across 3 files
  • Call RUBE_SEARCH_TOOLS first for current schemasin 6 of 325, across 3 files

Said here and by no other author read

  • Use reportable and renderable exceptions
  • Use structured logs and channel strategy
  • Follow Laravel conventions before custom abstractions
  • Prefer explicit, tested project-local patterns
  • Keep controllers focused on HTTP orchestration
  • Put validation, authorization, transactions, and integrations at clear boundaries

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.