[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77VJXQSHD16SZ9GE3DFVT77":3,"skill-same:01M77VJXQSHD16SZ9GE3DFVT77":52},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M77VJXQSHD16SZ9GE3DFVT77","python-observability",null,"Python observability patterns including structured logging, metrics, and distributed tracing. Use when adding logging, implementing metrics collection, setting up tracing, or debugging production systems.","Reihantt6\u002Fsns-myagent","Reihantt6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F219822095?v=4","01M77KK94PV8B7C2D9XWXNS8DJ","Mohamad Reihan tegar prasetya","01M77KK958QFMTHYXGXFV7KZ79",2,"MIT","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fpython-observability\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"Python observability patterns including structured logging, metrics, and distributed tracing. Use when adding logging, implementing metrics collection, setting up tracing, or debugging production systems.\"\n---\n# Python Observability\n\nInstrument Python applications with structured logs, metrics, and traces. When something breaks in production, you need to answer \"what, where, and why\" without deploying new code.\n\n## When to Use This Skill\n\n- Adding structured logging to applications\n- Implementing metrics collection with Prometheus\n- Setting up distributed tracing across services\n- Propagating correlation IDs through request chains\n- Debugging production issues\n- Building observability dashboards\n\n## Core Concepts\n\n### 1. Structured Logging\n\nEmit logs as JSON with consistent fields for production environments. Machine-readable logs enable powerful queries and alerts. For local development, consider human-readable formats.\n\n### 2. The Four Golden Signals\n\nTrack latency, traffic, errors, and saturation for every service boundary.\n\n### 3. Correlation IDs\n\nThread a unique ID through all logs and spans for a single request, enabling end-to-end tracing.\n\n### 4. Bounded Cardinality\n\nKeep metric label values bounded. Unbounded labels (like user IDs) explode storage costs.\n\n## Quick Start\n\n```python\nimport structlog\n\nstructlog.configure(\n    processors=[\n        structlog.processors.TimeStamper(fmt=\"iso\"),\n        structlog.processors.JSONRenderer(),\n    ],\n)\n\nlogger = structlog.get_logger()\nlogger.info(\"Request processed\", user_id=\"123\", duration_ms=45)\n```\n\n## Fundamental Patterns\n\n### Pattern 1: Structured Logging with Structlog\n\nConfigure structlog for JSON output with consistent fields.\n\n```python\nimport logging\nimport structlog\n\ndef configure_logging(log_level: str = \"INFO\") -> None:\n    \"\"\"Configure structured logging for the application.\"\"\"\n    structlog.configure(\n        processors=[\n            structlog.contextvars.merge_contextvars,\n            structlog.processors.add_log_level,\n            structlog.processors.TimeStamper(fmt=\"iso\"),\n            structlog.processors.StackInfoRenderer(),\n            structlog.processors.format_exc_info,\n            structlog.processors.JSONRenderer(),\n        ],\n        wrapper_class=structlog.make_filtering_bound_logger(\n            getattr(logging, log_level.upper())\n        ),\n        context_class=dict,\n        logger_factory=structlog.PrintLoggerFactory(),\n        cache_logger_on_first_use=True,\n    )\n\n# Initialize at application startup\nconfigure_logging(\"INFO\")\nlogger = structlog.get_logger()\n```\n\n### Pattern 2: Consistent Log Fields\n\nEvery log entry should include standard fields for filtering and correlation.\n\n```python\nimport structlog\nfrom contextvars import ContextVar\n\n# Store correlation ID in context\ncorrelation_id: ContextVar[str] = ContextVar(\"correlation_id\", default=\"\")\n\nlogger = structlog.get_logger()\n\ndef process_request(request: Request) -> Response:\n    \"\"\"Process request with structured logging.\"\"\"\n    logger.info(\n        \"Request received\",\n        correlation_id=correlation_id.get(),\n        method=request.method,\n        path=request.path,\n        user_id=request.user_id,\n    )\n\n    try:\n        result = handle_request(request)\n        logger.info(\n            \"Request completed\",\n            correlation_id=correlation_id.get(),\n            status_code=200,\n            duration_ms=elapsed,\n        )\n        return result\n    except Exception as e:\n        logger.error(\n            \"Request failed\",\n            correlation_id=correlation_id.get(),\n            error_type=type(e).__name__,\n            error_message=str(e),\n        )\n        raise\n```\n\n### Pattern 3: Semantic Log Levels\n\nUse log levels consistently across the application.\n\n| Level | Purpose | Examples |\n|-------|---------|----------|\n| `DEBUG` | Development diagnostics | Variable values, internal state |\n| `INFO` | Request lifecycle, operations | Request start\u002Fend, job completion |\n| `WARNING` | Recoverable anomalies | Retry attempts, fallback used |\n| `ERROR` | Failures needing attention | Exceptions, service unavailable |\n\n```python\n# DEBUG: Detailed internal information\nlogger.debug(\"Cache lookup\", key=cache_key, hit=cache_hit)\n\n# INFO: Normal operational events\nlogger.info(\"Order created\", order_id=order.id, total=order.total)\n\n# WARNING: Abnormal but handled situations\nlogger.warning(\n    \"Rate limit approaching\",\n    current_rate=950,\n    limit=1000,\n    reset_seconds=30,\n)\n\n# ERROR: Failures requiring investigation\nlogger.error(\n    \"Payment processing failed\",\n    order_id=order.id,\n    error=str(e),\n    payment_provider=\"stripe\",\n)\n```\n\nNever log expected behavior at `ERROR`. A user entering a wrong password is `INFO`, not `ERROR`.\n\n### Pattern 4: Correlation ID Propagation\n\nGenerate a unique ID at ingress and thread it through all operations.\n\n```python\nfrom contextvars import ContextVar\nimport uuid\nimport structlog\n\ncorrelation_id: ContextVar[str] = ContextVar(\"correlation_id\", default=\"\")\n\ndef set_correlation_id(cid: str | None = None) -> str:\n    \"\"\"Set correlation ID for current context.\"\"\"\n    cid = cid or str(uuid.uuid4())\n    correlation_id.set(cid)\n    structlog.contextvars.bind_contextvars(correlation_id=cid)\n    return cid\n\n# FastAPI middleware example\nfrom fastapi import Request\n\nasync def correlation_middleware(request: Request, call_next):\n    \"\"\"Middleware to set and propagate correlation ID.\"\"\"\n    # Use incoming header or generate new\n    cid = request.headers.get(\"X-Correlation-ID\") or str(uuid.uuid4())\n    set_correlation_id(cid)\n\n    response = await call_next(request)\n    response.headers[\"X-Correlation-ID\"] = cid\n    return response\n```\n\nPropagate to outbound requests:\n\n```python\nimport httpx\n\nasync def call_downstream_service(endpoint: str, data: dict) -> dict:\n    \"\"\"Call downstream service with correlation ID.\"\"\"\n    async with httpx.AsyncClient() as client:\n        response = await client.post(\n            endpoint,\n            json=data,\n            headers={\"X-Correlation-ID\": correlation_id.get()},\n        )\n        return response.json()\n```\n\n## Detailed worked examples and patterns\n\nDetailed sections (starting with `## Advanced Patterns`) live in `references\u002Fdetails.md`. Read that file when the navigation summary above is insufficient.\n\n## Best Practices Summary\n\n1. **Use structured logging** - JSON logs with consistent fields\n2. **Propagate correlation IDs** - Thread through all requests and logs\n3. **Track the four golden signals** - Latency, traffic, errors, saturation\n4. **Bound label cardinality** - Never use unbounded values as metric labels\n5. **Log at appropriate levels** - Don't cry wolf with ERROR\n6. **Include context** - User ID, request ID, operation name in logs\n7. **Use context managers** - Consistent timing and error handling\n8. **Separate concerns** - Observability code shouldn't pollute business logic\n9. **Test your observability** - Verify logs and metrics in integration tests\n10. **Set up alerts** - Metrics are useless without alerting\n","# Python Observability\n\nInstrument Python applications with structured logs, metrics, and traces. When something breaks in production, you need to answer \"what, where, and why\" without deploying new code.\n\n## When to Use This Skill\n\n- Adding structured logging to applications\n- Implementing metrics collection with Prometheus\n- Setting up distributed tracing across services\n- Propagating correlation IDs through request chains\n- Debugging production issues\n- Building observability dashboards\n\n## Core Concepts\n\n### 1. Structured Logging\n\nEmit logs as JSON with consistent fields for production environments. Machine-readable logs enable powerful queries and alerts. For local development, consider human-readable formats.\n\n### 2. The Four Golden Signals\n\nTrack latency, traffic, errors, and saturation for every service boundary.\n\n### 3. Correlation IDs\n\nThread a unique ID through all logs and spans for a single request, enabling end-to-end tracing.\n\n### 4. Bounded Cardinality\n\nKeep metric label values bounded. Unbounded labels (like user IDs) explode storage costs.\n\n## Quick Start\n\n```python\nimport structlog\n\nstructlog.configure(\n    processors=[\n        structlog.processors.TimeStamper(fmt=\"iso\"),\n        structlog.processors.JSONRenderer(),\n    ],\n)\n\nlogger = structlog.get_logger()\nlogger.info(\"Request processed\", user_id=\"123\", duration_ms=45)\n```\n\n## Fundamental Patterns\n\n### Pattern 1: Structured Logging with Structlog\n\nConfigure structlog for JSON output with consistent fields.\n\n```python\nimport logging\nimport structlog\n\ndef configure_logging(log_level: str = \"INFO\") -> None:\n    \"\"\"Configure structured logging for the application.\"\"\"\n    structlog.configure(\n        processors=[\n            structlog.contextvars.merge_contextvars,\n            structlog.processors.add_log_level,\n            structlog.processors.TimeStamper(fmt=\"iso\"),\n            structlog.processors.StackInfoRenderer(),\n            structlog.processors.format_exc_info,\n            structlog.processors.JSONRenderer(),\n        ],\n        wrapper_class=structlog.make_filtering_bound_logger(\n            getattr(logging, log_level.upper())\n        ),\n        context_class=dict,\n        logger_factory=structlog.PrintLoggerFactory(),\n        cache_logger_on_first_use=True,\n    )\n\n# Initialize at application startup\nconfigure_logging(\"INFO\")\nlogger = structlog.get_logger()\n```\n\n### Pattern 2: Consistent Log Fields\n\nEvery log entry should include standard fields for filtering and correlation.\n\n```python\nimport structlog\nfrom contextvars import ContextVar\n\n# Store correlation ID in context\ncorrelation_id: ContextVar[str] = ContextVar(\"correlation_id\", default=\"\")\n\nlogger = structlog.get_logger()\n\ndef process_request(request: Request) -> Response:\n    \"\"\"Process request with structured logging.\"\"\"\n    logger.info(\n        \"Request received\",\n        correlation_id=correlation_id.get(),\n        method=request.method,\n        path=request.path,\n        user_id=request.user_id,\n    )\n\n    try:\n        result = handle_request(request)\n        logger.info(\n            \"Request completed\",\n            correlation_id=correlation_id.get(),\n            status_code=200,\n            duration_ms=elapsed,\n        )\n        return result\n    except Exception as e:\n        logger.error(\n            \"Request failed\",\n            correlation_id=correlation_id.get(),\n            error_type=type(e).__name__,\n            error_message=str(e),\n        )\n        raise\n```\n\n### Pattern 3: Semantic Log Levels\n\nUse log levels consistently across the application.\n\n| Level | Purpose | Examples |\n|-------|---------|----------|\n| `DEBUG` | Development diagnostics | Variable values, internal state |\n| `INFO` | Request lifecycle, operations | Request start\u002Fend, job completion |\n| `WARNING` | Recoverable anomalies | Retry attempts, fallback used |\n| `ERROR` | Failures needing attention | Exceptions, service unavailable |\n\n```python\n# DEBUG: Detailed internal information\nlogger.debug(\"Cache lookup\", key=cache_key, hit=cache_hit)\n\n# INFO: Normal operational events\nlogger.info(\"Order created\", order_id=order.id, total=order.total)\n\n# WARNING: Abnormal but handled situations\nlogger.warning(\n    \"Rate limit approaching\",\n    current_rate=950,\n    limit=1000,\n    reset_seconds=30,\n)\n\n# ERROR: Failures requiring investigation\nlogger.error(\n    \"Payment processing failed\",\n    order_id=order.id,\n    error=str(e),\n    payment_provider=\"stripe\",\n)\n```\n\nNever log expected behavior at `ERROR`. A user entering a wrong password is `INFO`, not `ERROR`.\n\n### Pattern 4: Correlation ID Propagation\n\nGenerate a unique ID at ingress and thread it through all operations.\n\n```python\nfrom contextvars import ContextVar\nimport uuid\nimport structlog\n\ncorrelation_id: ContextVar[str] = ContextVar(\"correlation_id\", default=\"\")\n\ndef set_correlation_id(cid: str | None = None) -> str:\n    \"\"\"Set correlation ID for current context.\"\"\"\n    cid = cid or str(uuid.uuid4())\n    correlation_id.set(cid)\n    structlog.contextvars.bind_contextvars(correlation_id=cid)\n    return cid\n\n# FastAPI middleware example\nfrom fastapi import Request\n\nasync def correlation_middleware(request: Request, call_next):\n    \"\"\"Middleware to set and propagate correlation ID.\"\"\"\n    # Use incoming header or generate new\n    cid = request.headers.get(\"X-Correlation-ID\") or str(uuid.uuid4())\n    set_correlation_id(cid)\n\n    response = await call_next(request)\n    response.headers[\"X-Correlation-ID\"] = cid\n    return response\n```\n\nPropagate to outbound requests:\n\n```python\nimport httpx\n\nasync def call_downstream_service(endpoint: str, data: dict) -> dict:\n    \"\"\"Call downstream service with correlation ID.\"\"\"\n    async with httpx.AsyncClient() as client:\n        response = await client.post(\n            endpoint,\n            json=data,\n            headers={\"X-Correlation-ID\": correlation_id.get()},\n        )\n        return response.json()\n```\n\n## Detailed worked examples and patterns\n\nDetailed sections (starting with `## Advanced Patterns`) live in `references\u002Fdetails.md`. Read that file when the navigation summary above is insufficient.\n\n## Best Practices Summary\n\n1. **Use structured logging** - JSON logs with consistent fields\n2. **Propagate correlation IDs** - Thread through all requests and logs\n3. **Track the four golden signals** - Latency, traffic, errors, saturation\n4. **Bound label cardinality** - Never use unbounded values as metric labels\n5. **Log at appropriate levels** - Don't cry wolf with ERROR\n6. **Include context** - User ID, request ID, operation name in logs\n7. **Use context managers** - Consistent timing and error handling\n8. **Separate concerns** - Observability code shouldn't pollute business logic\n9. **Test your observability** - Verify logs and metrics in integration tests\n10. **Set up alerts** - Metrics are useless without alerting\n",{"description":7},"main","58843b159d7a4050d6b785a98b908cce505c0b92","agent\u002Fskills\u002Fpython-observability",0,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent","https:\u002F\u002Fgithub.com\u002FReihantt6","reihsns.web.id","2026-08-19 20:08:18",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Reihantt6\u002Fsns-myagent --skill python-observability",{"tool":38,"command":39},"bunx","bunx skills add Reihantt6\u002Fsns-myagent --skill python-observability",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Reihantt6\u002Fsns-myagent --skill python-observability","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fpython-observability\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fdetails.md","REFERENCE","参考文档",5033,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fpython-observability\u002Freferences\u002Fdetails.md",[53,60,67,74,81,88],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M77XDCYZ407XYMF2T4P6F7VT","youtube-transcript","Extract transcripts from YouTube videos. Use when the user asks for a transcript, subtitles, or captions of a YouTube video and provides a YouTube URL (youtube.com\u002Fwatch?v=, youtu.be\u002F, or similar). Supports output with or without timestamps.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-transcript\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M77XD7PBC98J6MXGJJ2TJ8DX","youtube-thumbnail-design","YouTube thumbnail design with specific dimensions, contrast rules, and mobile preview optimization. Covers safe zones, text placement, face expression psychology, and A\u002FB testing. Use for: YouTube thumbnails, video cover images, click-through optimization. Triggers: youtube thumbnail, thumbnail design, video thumbnail, click through rate, ctr optimization, youtube cover, video cover image, thumbnail maker, thumbnail tips, youtube design, video preview image","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-thumbnail-design\u002FSKILL.md",[],[],{"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":19},"01M77XD2541C8HXJ6RHYZP4NGJ","youtube-short-maker","Make YouTube Shorts that hold attention with Pexo — vertical 9:16, fast-paced, hook in the first 3 seconds. Describe your topic and Pexo writes the script, generates the shots, picks the models, and assembles a finished Short with music and captions. Use for YouTube Shorts: \"youtube short\", \"make a youtube short\", \"shorts video\", \"short-form video\". NOT for long-form or landscape video.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-short-maker\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M77XCXKVSYK7KTZ3PQBVVGFD","xcode-project-setup","Safely modifies Xcode projects (.pbxproj) to add Swift Packages and link files. Use this skill whenever an iOS project needs dependencies installed (e.g. Firebase, Alamofire).","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fxcode-project-setup\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M77XCR1DV8ZQK2NHWKVY4EWX","x402","Set up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key. Two setups it works out up front — \"just use it\" (set up a wallet so you or Claude Code can run cloud browser tasks paid from the wallet — Claude writes and runs throwaway scripts, nothing touches your codebase) or \"build it in\" (install the SDK and write the key + code into your project). Walks through wallet setup, funding, .env, and a ~$1 test run. Use when the user asks about x402, pay-per-use, USDC payments, or wants Browser Use Cloud without an API key. For the free-tier signup (reverse-CAPTCHA → API key), use `browser-use cloud signup` or the `cloud` skill instead.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fx402\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M77XCMD3R3ZBZQQSW6E0793B","x-twitter-scraper","Build GitHub Copilot workflows with Xquik X API SDKs, REST endpoints, hosted Apify Actor runs, MCP tools, TweetClaw OpenClaw plugin installs, signed webhooks, tweet search, user lookup, follower exports, media actions, and agent automation.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fx-twitter-scraper\u002FSKILL.md",[],[]]