agentsclimarketplace

Observability logging

Skill planifest/planifest-framework/planifest-framework/external-skills/observability-logging

A specification framework for agentic development. Agents build from complete specs - not guesses.

Install
npx -y skills add planifest/planifest-framework --skill observability-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

  • 0 stars0 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.

What its author says it does

Copied from the file, not written here

Observability logging workflow for structured schema, correlation, and incident triage utility. Use when services need logging standards or revisions for diagnosable incidents; do not use for business-feature implementation logic.

SKILL.md

1.9 KB, as published. Nobody here has run it

Observability Logging

Overview

Use this skill to standardize logs so incidents can be diagnosed quickly and safely.

Scope Boundaries

  • Use this skill when the task matches the trigger condition described in description.
  • Do not use this skill when the primary task falls outside this skill's domain.

Shared References

  • Logging field and retention rules:
    • references/logging-field-and-retention-rules.md

Templates And Assets

  • Logging schema template:
    • assets/logging-schema-template.md
  • Log triage checklist:
    • assets/log-triage-checklist.md

Inputs To Gather

  • Incident triage requirements and common failure modes.
  • Required correlation fields and security constraints.
  • Retention, redaction, and access policy requirements.
  • Queryability needs for on-call workflows.

Deliverables

  • Logging schema and policy baseline.
  • Redaction/retention controls.
  • Triage validation evidence for key incident scenarios.

Workflow

  1. Define schema in assets/logging-schema-template.md.
  2. Apply retention/redaction policy from references/logging-field-and-retention-rules.md.
  3. Validate triage utility using assets/log-triage-checklist.md.
  4. Fix gaps in correlation and error context fields.
  5. Publish logging standard and ownership.

Quality Standard

  • Logs contain required triage context and correlation IDs.
  • Sensitive data handling is explicit and enforced.
  • Retention and access are policy-compliant.

Failure Conditions

  • Stop when logs lack required incident context.
  • Stop when sensitive data redaction is not reliable.
  • Escalate when logging policy conflicts with compliance requirements.

Keep looking

Skills are one crate of 328,083. 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.