[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CT9G7R033F05EY7A2BF75B":3,"skill-same:01M6CT9G7R033F05EY7A2BF75B":66},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":29,"linkOnly":30,"markdownContent":31,"markdownBody":32,"frontMatter":33,"refName":34,"commitSha":35,"skillDirectory":36,"forksCount":37,"repositoryHtmlUrl":38,"repositoryHomepageUrl":6,"ownerHtmlUrl":39,"ownerBlogUrl":6,"ownerDescription":40,"updatedAt":41,"install":42,"resources":55},"01M6CT9G7R033F05EY7A2BF75B","observability-baseline",null,"Sets logging, metrics and tracing conventions for the codebase. Use when setting up or auditing monitoring.","vibbs\u002Fcompany-os","vibbs","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F7379149?v=4","01M6CT6M03CAS1H7RA89F3965B","Vibbs Dod","01M6CT6M4MY60C9FFQ3AAR2RSK",6,"MIT","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fobservability-baseline\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28],"observability","baseline","observability baseline","logging","metrics","tracing","monitoring","use","up","conventions","2026-11-10 10:12:30",false,"---\nname: observability-baseline\ndescription: Sets logging, metrics and tracing conventions for the codebase. Use when setting up or auditing monitoring.\nuser-invocable: false\n---\n\n# Observability Baseline\n\n## Reference\n- **ID**: S-ENG-15\n- **Category**: Engineering\n- **Inputs**: service architecture, SLOs, existing logging\u002Fmetrics setup\n- **Outputs**: observability standards document → artifacts\u002Fengineering\u002F\n- **Used by**: Engineering Agent\n- **Tool scripts**: .\u002Ftools\u002Fartifact\u002Fvalidate.sh\n\n## Purpose\nDefines the baseline conventions for structured logging, application metrics, and distributed tracing so that every service produces consistent, queryable telemetry data from day one.\n\n## Procedure\n\n### Step 0: Tech Stack Detection\n\nRead `observability.*` from `company.config.yaml` to determine logging, metrics, and tracing providers.\n\n**Provider-specific patterns:**\n\n| Provider | Logging | Metrics | Tracing |\n|----------|---------|---------|---------|\n| Datadog | Pino → `dd-trace` auto-inject | StatsD via `hot-shots` | `dd-trace` auto-instrumentation |\n| Sentry | `@sentry\u002Fnode` breadcrumbs | Sentry performance metrics | Sentry transactions |\n| OpenTelemetry | OTLP exporter | OTLP metrics | OTLP spans |\n| CloudWatch | `winston` + CloudWatch transport | CloudWatch embedded metrics | X-Ray SDK |\n\n**Structured log required fields:**\n```json\n{\n  \"timestamp\": \"ISO-8601\",\n  \"level\": \"info|warn|error|debug\",\n  \"message\": \"Human-readable description\",\n  \"request_id\": \"uuid\",\n  \"user_id\": \"optional\",\n  \"tenant_id\": \"optional (if multi-tenant)\",\n  \"duration_ms\": \"optional (for timed operations)\",\n  \"error\": { \"code\": \"string\", \"stack\": \"string\" }\n}\n```\n\n**Cross-references:** See deployment-strategy for infrastructure setup, incident-response for alert routing.\n\n1. Audit the current observability setup: what logging, metrics, and tracing exist today.\n2. Define structured logging conventions: log levels, required fields (request_id, tenant_id, user_id), format (JSON).\n3. Define application metrics conventions: naming scheme, label cardinality limits, standard metrics (request duration, error rate, queue depth).\n4. Define distributed tracing conventions: span naming, context propagation, sampling strategy.\n5. Establish SLO-aligned alerting: map each SLO to a metric and define alert thresholds.\n6. Document correlation strategy: how to go from an alert to logs to traces.\n7. Define sensitive data handling in telemetry: what must never be logged (PII, secrets).\n8. Create example code snippets for each convention.\n9. Save the standards document to `artifacts\u002Fengineering\u002F`.\n10. Validate the artifact using `.\u002Ftools\u002Fartifact\u002Fvalidate.sh`.\n\n## Quality Checklist\n- [ ] Structured logging format is defined with required fields\n- [ ] Metric naming conventions follow a consistent scheme\n- [ ] Distributed tracing spans are named consistently\n- [ ] SLO-to-alert mapping is documented\n- [ ] Correlation path (alert → logs → traces) is clear\n- [ ] PII\u002Fsecret exclusion rules are specified\n- [ ] Example code snippets are provided\n- [ ] Artifact passes validation\n","# Observability Baseline\n\n## Reference\n- **ID**: S-ENG-15\n- **Category**: Engineering\n- **Inputs**: service architecture, SLOs, existing logging\u002Fmetrics setup\n- **Outputs**: observability standards document → artifacts\u002Fengineering\u002F\n- **Used by**: Engineering Agent\n- **Tool scripts**: .\u002Ftools\u002Fartifact\u002Fvalidate.sh\n\n## Purpose\nDefines the baseline conventions for structured logging, application metrics, and distributed tracing so that every service produces consistent, queryable telemetry data from day one.\n\n## Procedure\n\n### Step 0: Tech Stack Detection\n\nRead `observability.*` from `company.config.yaml` to determine logging, metrics, and tracing providers.\n\n**Provider-specific patterns:**\n\n| Provider | Logging | Metrics | Tracing |\n|----------|---------|---------|---------|\n| Datadog | Pino → `dd-trace` auto-inject | StatsD via `hot-shots` | `dd-trace` auto-instrumentation |\n| Sentry | `@sentry\u002Fnode` breadcrumbs | Sentry performance metrics | Sentry transactions |\n| OpenTelemetry | OTLP exporter | OTLP metrics | OTLP spans |\n| CloudWatch | `winston` + CloudWatch transport | CloudWatch embedded metrics | X-Ray SDK |\n\n**Structured log required fields:**\n```json\n{\n  \"timestamp\": \"ISO-8601\",\n  \"level\": \"info|warn|error|debug\",\n  \"message\": \"Human-readable description\",\n  \"request_id\": \"uuid\",\n  \"user_id\": \"optional\",\n  \"tenant_id\": \"optional (if multi-tenant)\",\n  \"duration_ms\": \"optional (for timed operations)\",\n  \"error\": { \"code\": \"string\", \"stack\": \"string\" }\n}\n```\n\n**Cross-references:** See deployment-strategy for infrastructure setup, incident-response for alert routing.\n\n1. Audit the current observability setup: what logging, metrics, and tracing exist today.\n2. Define structured logging conventions: log levels, required fields (request_id, tenant_id, user_id), format (JSON).\n3. Define application metrics conventions: naming scheme, label cardinality limits, standard metrics (request duration, error rate, queue depth).\n4. Define distributed tracing conventions: span naming, context propagation, sampling strategy.\n5. Establish SLO-aligned alerting: map each SLO to a metric and define alert thresholds.\n6. Document correlation strategy: how to go from an alert to logs to traces.\n7. Define sensitive data handling in telemetry: what must never be logged (PII, secrets).\n8. Create example code snippets for each convention.\n9. Save the standards document to `artifacts\u002Fengineering\u002F`.\n10. Validate the artifact using `.\u002Ftools\u002Fartifact\u002Fvalidate.sh`.\n\n## Quality Checklist\n- [ ] Structured logging format is defined with required fields\n- [ ] Metric naming conventions follow a consistent scheme\n- [ ] Distributed tracing spans are named consistently\n- [ ] SLO-to-alert mapping is documented\n- [ ] Correlation path (alert → logs → traces) is clear\n- [ ] PII\u002Fsecret exclusion rules are specified\n- [ ] Example code snippets are provided\n- [ ] Artifact passes validation\n",{"name":5,"description":7,"user-invocable":30},"main","e842fb6d0e04360c47db78bc2e2e2987314d64d4",".claude\u002Fskills\u002Fobservability-baseline",2,"https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os","https:\u002F\u002Fgithub.com\u002Fvibbs","Principal Engineer · Applied AI · building ArcAI @ GrowthArc","2026-10-21 02:08:08",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add vibbs\u002Fcompany-os --skill observability-baseline",{"tool":48,"command":49},"bunx","bunx skills add vibbs\u002Fcompany-os --skill observability-baseline",{"tool":51,"command":52},"pnpm","pnpm dlx skills add vibbs\u002Fcompany-os --skill observability-baseline","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fobservability-baseline\u002FSKILL.md",true,[56,62],{"path":57,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":61},"scripts\u002Freview_case.py","SCRIPT","脚本",20559,"https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FReverse-Analysis\u002Fcase-review\u002Fscripts\u002Freview_case.py",{"path":63,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":64,"sourceHtmlUrl":65},"tests\u002Ftest_review_case.py",6924,"https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FReverse-Analysis\u002Fcase-review\u002Ftests\u002Ftest_review_case.py",[67,76,84,94,110,128],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":29},"01M6CTHBW1E64ECYGD105N4S5E","typo-field","Fixture skill with a misspelled top-level field.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Ftypo-field\u002FSKILL.md",[],[74,75],"typo field","fixture skill",{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":29},"01M6CTHABTV8FKVDHFMMKPAV51","spaced-comments","Fixture skill with comments and spaces after block keys.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Fspaced-comments\u002FSKILL.md",[],[83,75],"spaced comments",{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":29},"01M6CTH8MHC14KB65ZDHYBJW1N","crlf-comments","Fixture skill with Windows line endings.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Fcrlf-comments\u002FSKILL.md",[],[91,92,93,75],"crlf comments","CRLF","windows",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":29},"01M6CTH6TBKTDP9G8QB1Z2K0TY","claude-fields","Fixture skill using top-level fields Claude Code documents.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Fclaude-fields\u002FSKILL.md",[],[101,102,103,104,105,106,75,107,108,109],"claude fields","explore","documents","src","grep","read","Bash","code","testing",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":121,"publishedAt":29},"01M6CTH46BGKXH80RWS876Y2CW","workflow-router","Maps an objective to the artifacts, stages and agents it needs. Use when deciding what happens next or which agents to involve.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Fos\u002Fskills\u002Fworkflow-router\u002FSKILL.md",[116],{"categoryNo":117,"categoryName":118,"taxonomyType":119,"taxonomyTypeDesc":120},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[122,123,124,125,126,26,127],"workflow","router","workflow router","next","maps","artifacts",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":29},"01M6CTH27653SRVP2FMEQN3J5B","weekly-review","Summarizes your week: what shipped, AI spend, support themes, security health and next priorities. Use at the end of each week.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Fos\u002Fskills\u002Fweekly-review\u002FSKILL.md",[],[135,136,137,125,26,138,139,140,141],"weekly review","review","priorities","health","save","support","security"]