[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6NPXQ8DC3R2ZZ1Z565KZ71W":3,"skill-same:01M6NPXQ8DC3R2ZZ1Z565KZ71W":75},{"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":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":14,"repositoryHtmlUrl":52,"repositoryHomepageUrl":53,"ownerHtmlUrl":54,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":55,"install":56,"resources":69},"01M6NPXQ8DC3R2ZZ1Z565KZ71W","error-handling",null,"Error handling across languages — Result types, exceptions, retries, circuit breakers, and structured error responses. Use when designing error handling for a module or service, choosing between Result types and exceptions, building error hierarchies, implementing retries or circuit breakers, or reviewing code for missing or poor error handling.","projectious-work\u002Fprocesskit","projectious-work","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F263889726?v=4","01M6N97TJJ118WQ35CHRV8RD0E","projectious.work","01M6N97TPWJPF0BMKYQ4PBY5W8",0,"MIT","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fengineering\u002Ferror-handling\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,5,34,35,36],"error handling","error","result","code","for","implementing","circuit","reviewing code","types","retries","missing","module","service","structured","across","use","work","engineering","2026-11-10 10:12:30",false,"---\nname: error-handling\ndescription: |\n  Error handling across languages — Result types, exceptions, retries, circuit breakers, and structured error responses. Use when designing error handling for a module or service, choosing between Result types and exceptions, building error hierarchies, implementing retries or circuit breakers, or reviewing code for missing or poor error handling.\nmetadata:\n  processkit:\n    apiVersion: processkit.projectious.work\u002Fv2\n    id: SKILL-error-handling\n    version: \"1.1.0\"\n    created: 2026-04-06T00:00:00Z\n    category: engineering\n---\n\n# Error Handling\n\n## Intro\n\nErrors are part of the type system, not an afterthought. Make\nfailure paths explicit, separate user-facing messages from internal\ndiagnostics, and reach for retries and circuit breakers only when\nthe failure is genuinely transient.\n\n## Overview\n\n### Result types vs exceptions\n\nUse algebraic types where the language supports them — they make\nerror paths explicit in the signature.\n\n- **Rust:** `Result\u003CT, E>` for recoverable errors, `Option\u003CT>` for\n  missing values. Propagate with `?`. Define domain error enums\n  with `thiserror`.\n- **TypeScript:** discriminated unions or a `Result\u003CT, E>` library.\n  Avoid `throw` for expected failures (validation, not-found).\n  Reserve exceptions for truly unexpected conditions.\n- **Python:** exceptions are idiomatic, but consider returning\n  `None` or a result tuple in tight loops where try\u002Fexcept overhead\n  matters.\n- **Java:** checked exceptions for recoverable conditions the\n  caller must handle, unchecked (`RuntimeException`) for\n  programming errors. Prefer specific types over `Exception`.\n\n### Error hierarchies\n\nDesign errors in layers:\n\n1. **Domain errors** — business rule violations\n   (`InsufficientFunds`, `ItemOutOfStock`).\n2. **Application errors** — workflow failures (`OrderNotFound`,\n   `Unauthorized`).\n3. **Infrastructure errors** — external system failures\n   (`DatabaseUnavailable`, `TimeoutError`).\n\nEach layer exposes only errors meaningful at that level.\nInfrastructure errors are mapped to application errors before\nreaching the domain.\n\n### User-facing vs internal\n\nNever leak stack traces, SQL, or file paths to end users.\n\n- **Internal errors:** full context for debugging — stack trace,\n  request ID, input values.\n- **User-facing errors:** human-readable message, error code,\n  optional field-level details.\n- Map at the boundary (HTTP handler, CLI output). Log the internal\n  error with a correlation ID; return the ID to the user for\n  support.\n\n### Error codes and structured responses\n\nUse namespaced, stable error codes (`PAYMENT.DECLINED`,\n`AUTH.TOKEN_EXPIRED`, `VALIDATION.FIELD_REQUIRED`). Document them\nin a central registry. Never reuse or rename codes once shipped.\n\nFor APIs, return a consistent error shape:\n\n```json\n{\n  \"error\": {\n    \"code\": \"VALIDATION.FIELD_REQUIRED\",\n    \"message\": \"The 'email' field is required.\",\n    \"details\": [\n      { \"field\": \"email\", \"reason\": \"required\" }\n    ],\n    \"request_id\": \"req-abc123\"\n  }\n}\n```\n\n### Retries and circuit breakers\n\nRetry only transient failures (network timeouts, 503s, lock\ncontention). Use exponential backoff with jitter: base delay\n100–500ms, multiply by 2 each attempt, add random jitter (0–100% of\ndelay) to prevent thundering herd. Cap retries (3–5) and total\ntimeout. **Never retry** 4xx client errors (except 429), validation\nfailures, or auth errors.\n\nCircuit breakers prevent cascading failures when a downstream\nservice is unhealthy:\n\n- **Closed** (normal): requests flow through; track failure rate.\n- **Open** (tripped): requests fail immediately; return a fallback.\n- **Half-open** (probing): allow one request after a timeout. On\n  success, close. On failure, reopen.\n\nConfigure failure threshold (e.g. 5 failures in 30s), open duration\n(e.g. 60s), and half-open probe count.\n\n## Gotchas\n\nAgent-specific failure modes — provider-neutral pause-and-self-check items:\n\n- **Catching `Exception` (or bare `except:`) and swallowing it.** Silent error swallowing is the most common cause of production mysteries where \"nothing went wrong, but nothing worked either.\" Catch specific error types; log and re-raise everything else.\n- **Leaking stack traces, SQL, or file paths in HTTP responses.** Internal error details in user-facing responses are both a security vulnerability and a poor user experience. Map internal errors to user-facing codes at the boundary; log the full context internally with a correlation ID.\n- **Retrying non-idempotent operations without a deduplication key.** Retrying a payment, an email send, or an inventory decrement without idempotency protection causes double-charges and double-sends. Add an idempotency key at the call site before wiring retry logic.\n- **Retrying 4xx errors as if they were transient.** A 400 (bad request) or 401 (unauthorized) will not change on retry — it reflects a problem with the request, not the server. Retry only transient failures: 429, 500, 502, 503, 504, and network-level errors.\n- **Retrying without exponential backoff and jitter.** Fixed-interval retries on a struggling service create a thundering herd that prevents recovery. Use exponential backoff with random jitter; cap the total number of retries and the total elapsed time.\n- **Sentinel return values instead of explicit errors.** Returning `-1`, `null`, or an empty string to signal failure requires every caller to know and check the convention. Make failure explicit in the type: `Result\u003CT, E>`, `Option\u003CT>`, or a domain error type.\n- **Renaming or reusing error codes after shipping.** Error codes are a public contract. Consumers build conditional logic on them. Renaming `PAYMENT.DECLINED` or reusing a retired code silently breaks consumer error handling.\n\n## Full reference\n\n### Error reporting\n\n- Log with structured fields: `level`, `error_code`, `message`,\n  `stack`, `request_id`, `user_id`.\n- Send unhandled exceptions to an error tracker (Sentry, Datadog,\n  Honeybadger).\n- Alert on error rate spikes, not individual errors.\n- Group errors by root cause, not by message string.\n\n### Domain error enum (Rust)\n\n```rust\nuse thiserror::Error;\n\n#[derive(Error, Debug)]\npub enum PaymentError {\n    #[error(\"insufficient funds: required {required}, available {available}\")]\n    InsufficientFunds { required: u64, available: u64 },\n\n    #[error(\"card declined: {reason}\")]\n    CardDeclined { reason: String },\n\n    #[error(\"payment provider unavailable\")]\n    ProviderUnavailable(#[source] reqwest::Error),\n}\n\npub fn charge(amount: u64, balance: u64) -> Result\u003CReceipt, PaymentError> {\n    if amount > balance {\n        return Err(PaymentError::InsufficientFunds {\n            required: amount,\n            available: balance,\n        });\n    }\n    Ok(Receipt { amount })\n}\n```\n\n### Retry with backoff (Python)\n\n```python\nimport time\nimport random\nimport httpx\n\ndef fetch_with_retry(url: str, max_retries: int = 4) -> httpx.Response:\n    base_delay = 0.3\n    for attempt in range(max_retries + 1):\n        try:\n            resp = httpx.get(url, timeout=5.0)\n            if resp.status_code == 429:\n                retry_after = float(resp.headers.get(\"Retry-After\", base_delay))\n                time.sleep(retry_after + random.uniform(0, 0.5))\n                continue\n            resp.raise_for_status()\n            return resp\n        except httpx.TransportError:\n            if attempt == max_retries:\n                raise\n            delay = base_delay * (2 ** attempt) + random.uniform(0, base_delay)\n            time.sleep(delay)\n    raise httpx.HTTPError(f\"Failed after {max_retries} retries\")\n```\n\n### Structured API error response (TypeScript)\n\n```typescript\nclass AppError extends Error {\n  constructor(\n    public code: string,\n    message: string,\n    public statusCode: number = 500,\n    public details?: { field: string; reason: string }[],\n  ) {\n    super(message);\n  }\n}\n\n\u002F\u002F In route handler\napp.post(\"\u002Forders\", async (req, res) => {\n  try {\n    const order = await createOrder(req.body);\n    res.status(201).json(order);\n  } catch (err) {\n    if (err instanceof AppError) {\n      res.status(err.statusCode).json({\n        error: {\n          code: err.code,\n          message: err.message,\n          details: err.details,\n          request_id: req.id,\n        },\n      });\n    } else {\n      console.error(\"Unhandled error\", { request_id: req.id, err });\n      res.status(500).json({\n        error: {\n          code: \"INTERNAL.UNEXPECTED\",\n          message: \"An unexpected error occurred.\",\n          request_id: req.id,\n        },\n      });\n    }\n  }\n});\n```\n\n### Anti-patterns\n\n- Catching `Exception` (or bare `except:`) and swallowing it\n- Returning sentinel values (`-1`, empty string) instead of an\n  explicit error\n- Leaking SQL, stack traces, or filesystem paths in HTTP responses\n- Retrying non-idempotent operations without a deduplication key\n- Retrying 4xx errors as if they were transient\n- Renaming or reusing error codes after shipping them\n- Alerting on every individual error instead of rate spikes\n","# Error Handling\n\n## Intro\n\nErrors are part of the type system, not an afterthought. Make\nfailure paths explicit, separate user-facing messages from internal\ndiagnostics, and reach for retries and circuit breakers only when\nthe failure is genuinely transient.\n\n## Overview\n\n### Result types vs exceptions\n\nUse algebraic types where the language supports them — they make\nerror paths explicit in the signature.\n\n- **Rust:** `Result\u003CT, E>` for recoverable errors, `Option\u003CT>` for\n  missing values. Propagate with `?`. Define domain error enums\n  with `thiserror`.\n- **TypeScript:** discriminated unions or a `Result\u003CT, E>` library.\n  Avoid `throw` for expected failures (validation, not-found).\n  Reserve exceptions for truly unexpected conditions.\n- **Python:** exceptions are idiomatic, but consider returning\n  `None` or a result tuple in tight loops where try\u002Fexcept overhead\n  matters.\n- **Java:** checked exceptions for recoverable conditions the\n  caller must handle, unchecked (`RuntimeException`) for\n  programming errors. Prefer specific types over `Exception`.\n\n### Error hierarchies\n\nDesign errors in layers:\n\n1. **Domain errors** — business rule violations\n   (`InsufficientFunds`, `ItemOutOfStock`).\n2. **Application errors** — workflow failures (`OrderNotFound`,\n   `Unauthorized`).\n3. **Infrastructure errors** — external system failures\n   (`DatabaseUnavailable`, `TimeoutError`).\n\nEach layer exposes only errors meaningful at that level.\nInfrastructure errors are mapped to application errors before\nreaching the domain.\n\n### User-facing vs internal\n\nNever leak stack traces, SQL, or file paths to end users.\n\n- **Internal errors:** full context for debugging — stack trace,\n  request ID, input values.\n- **User-facing errors:** human-readable message, error code,\n  optional field-level details.\n- Map at the boundary (HTTP handler, CLI output). Log the internal\n  error with a correlation ID; return the ID to the user for\n  support.\n\n### Error codes and structured responses\n\nUse namespaced, stable error codes (`PAYMENT.DECLINED`,\n`AUTH.TOKEN_EXPIRED`, `VALIDATION.FIELD_REQUIRED`). Document them\nin a central registry. Never reuse or rename codes once shipped.\n\nFor APIs, return a consistent error shape:\n\n```json\n{\n  \"error\": {\n    \"code\": \"VALIDATION.FIELD_REQUIRED\",\n    \"message\": \"The 'email' field is required.\",\n    \"details\": [\n      { \"field\": \"email\", \"reason\": \"required\" }\n    ],\n    \"request_id\": \"req-abc123\"\n  }\n}\n```\n\n### Retries and circuit breakers\n\nRetry only transient failures (network timeouts, 503s, lock\ncontention). Use exponential backoff with jitter: base delay\n100–500ms, multiply by 2 each attempt, add random jitter (0–100% of\ndelay) to prevent thundering herd. Cap retries (3–5) and total\ntimeout. **Never retry** 4xx client errors (except 429), validation\nfailures, or auth errors.\n\nCircuit breakers prevent cascading failures when a downstream\nservice is unhealthy:\n\n- **Closed** (normal): requests flow through; track failure rate.\n- **Open** (tripped): requests fail immediately; return a fallback.\n- **Half-open** (probing): allow one request after a timeout. On\n  success, close. On failure, reopen.\n\nConfigure failure threshold (e.g. 5 failures in 30s), open duration\n(e.g. 60s), and half-open probe count.\n\n## Gotchas\n\nAgent-specific failure modes — provider-neutral pause-and-self-check items:\n\n- **Catching `Exception` (or bare `except:`) and swallowing it.** Silent error swallowing is the most common cause of production mysteries where \"nothing went wrong, but nothing worked either.\" Catch specific error types; log and re-raise everything else.\n- **Leaking stack traces, SQL, or file paths in HTTP responses.** Internal error details in user-facing responses are both a security vulnerability and a poor user experience. Map internal errors to user-facing codes at the boundary; log the full context internally with a correlation ID.\n- **Retrying non-idempotent operations without a deduplication key.** Retrying a payment, an email send, or an inventory decrement without idempotency protection causes double-charges and double-sends. Add an idempotency key at the call site before wiring retry logic.\n- **Retrying 4xx errors as if they were transient.** A 400 (bad request) or 401 (unauthorized) will not change on retry — it reflects a problem with the request, not the server. Retry only transient failures: 429, 500, 502, 503, 504, and network-level errors.\n- **Retrying without exponential backoff and jitter.** Fixed-interval retries on a struggling service create a thundering herd that prevents recovery. Use exponential backoff with random jitter; cap the total number of retries and the total elapsed time.\n- **Sentinel return values instead of explicit errors.** Returning `-1`, `null`, or an empty string to signal failure requires every caller to know and check the convention. Make failure explicit in the type: `Result\u003CT, E>`, `Option\u003CT>`, or a domain error type.\n- **Renaming or reusing error codes after shipping.** Error codes are a public contract. Consumers build conditional logic on them. Renaming `PAYMENT.DECLINED` or reusing a retired code silently breaks consumer error handling.\n\n## Full reference\n\n### Error reporting\n\n- Log with structured fields: `level`, `error_code`, `message`,\n  `stack`, `request_id`, `user_id`.\n- Send unhandled exceptions to an error tracker (Sentry, Datadog,\n  Honeybadger).\n- Alert on error rate spikes, not individual errors.\n- Group errors by root cause, not by message string.\n\n### Domain error enum (Rust)\n\n```rust\nuse thiserror::Error;\n\n#[derive(Error, Debug)]\npub enum PaymentError {\n    #[error(\"insufficient funds: required {required}, available {available}\")]\n    InsufficientFunds { required: u64, available: u64 },\n\n    #[error(\"card declined: {reason}\")]\n    CardDeclined { reason: String },\n\n    #[error(\"payment provider unavailable\")]\n    ProviderUnavailable(#[source] reqwest::Error),\n}\n\npub fn charge(amount: u64, balance: u64) -> Result\u003CReceipt, PaymentError> {\n    if amount > balance {\n        return Err(PaymentError::InsufficientFunds {\n            required: amount,\n            available: balance,\n        });\n    }\n    Ok(Receipt { amount })\n}\n```\n\n### Retry with backoff (Python)\n\n```python\nimport time\nimport random\nimport httpx\n\ndef fetch_with_retry(url: str, max_retries: int = 4) -> httpx.Response:\n    base_delay = 0.3\n    for attempt in range(max_retries + 1):\n        try:\n            resp = httpx.get(url, timeout=5.0)\n            if resp.status_code == 429:\n                retry_after = float(resp.headers.get(\"Retry-After\", base_delay))\n                time.sleep(retry_after + random.uniform(0, 0.5))\n                continue\n            resp.raise_for_status()\n            return resp\n        except httpx.TransportError:\n            if attempt == max_retries:\n                raise\n            delay = base_delay * (2 ** attempt) + random.uniform(0, base_delay)\n            time.sleep(delay)\n    raise httpx.HTTPError(f\"Failed after {max_retries} retries\")\n```\n\n### Structured API error response (TypeScript)\n\n```typescript\nclass AppError extends Error {\n  constructor(\n    public code: string,\n    message: string,\n    public statusCode: number = 500,\n    public details?: { field: string; reason: string }[],\n  ) {\n    super(message);\n  }\n}\n\n\u002F\u002F In route handler\napp.post(\"\u002Forders\", async (req, res) => {\n  try {\n    const order = await createOrder(req.body);\n    res.status(201).json(order);\n  } catch (err) {\n    if (err instanceof AppError) {\n      res.status(err.statusCode).json({\n        error: {\n          code: err.code,\n          message: err.message,\n          details: err.details,\n          request_id: req.id,\n        },\n      });\n    } else {\n      console.error(\"Unhandled error\", { request_id: req.id, err });\n      res.status(500).json({\n        error: {\n          code: \"INTERNAL.UNEXPECTED\",\n          message: \"An unexpected error occurred.\",\n          request_id: req.id,\n        },\n      });\n    }\n  }\n});\n```\n\n### Anti-patterns\n\n- Catching `Exception` (or bare `except:`) and swallowing it\n- Returning sentinel values (`-1`, empty string) instead of an\n  explicit error\n- Leaking SQL, stack traces, or filesystem paths in HTTP responses\n- Retrying non-idempotent operations without a deduplication key\n- Retrying 4xx errors as if they were transient\n- Renaming or reusing error codes after shipping them\n- Alerting on every individual error instead of rate spikes\n",{"name":5,"metadata":42,"description":48},{"processkit":43},{"id":44,"created":45,"version":46,"category":36,"apiVersion":47},"SKILL-error-handling",1775433600000,"1.1.0","processkit.projectious.work\u002Fv2","Error handling across languages — Result types, exceptions, retries, circuit breakers, and structured error responses. Use when designing error handling for a module or service, choosing between Result types and exceptions, building error hierarchies, implementing retries or circuit breakers, or reviewing code for missing or poor error handling.\n","main","7231f100e266e30d2c1699ecde5c00602471dc3c","src\u002Fcontext\u002Fskills\u002Fengineering\u002Ferror-handling","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit","https:\u002F\u002Fprojectious-work.github.io\u002Fprocesskit\u002F","https:\u002F\u002Fgithub.com\u002Fprojectious-work","2026-11-11 23:24:18",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add projectious-work\u002Fprocesskit --skill error-handling",{"tool":62,"command":63},"bunx","bunx skills add projectious-work\u002Fprocesskit --skill error-handling",{"tool":65,"command":66},"pnpm","pnpm dlx skills add projectious-work\u002Fprocesskit --skill error-handling","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fengineering\u002Ferror-handling\u002FSKILL.md",true,[70],{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":14,"sourceHtmlUrl":74},"scripts\u002F.gitkeep","SCRIPT","脚本","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fengineering\u002Ferror-handling\u002Fscripts\u002F.gitkeep",[76,83,90,96,123,143],{"skillNo":77,"name":78,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":82},"01M7665G2ED3624R3X93304265","standard-ui-design","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstandard-ui-design\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":82},"01M76651QTC6W0HJ4AFW2MMR3V","standard-agent-use","Company standard for working with AI agents. Use when deciding what to delegate to agents, capturing open work, keeping agent memory or knowledge notes, improving an agent workflow, or introducing agent work in a team or for a client.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstandard-agent-use\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":82},"01M76650NN4T8P241021NBR64S","standard-agent-building","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstandard-agent-building\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":107,"publishedAt":37},"01M6X5MTC89B4ZGXW3JVSQCPF8","skill-management","Manage Skill package manifests as v1 ontology entities.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fskill-management\u002FSKILL.md",[102],{"categoryNo":103,"categoryName":104,"taxonomyType":105,"taxonomyTypeDesc":106},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[108,109,110,111,112,113,35,114,115,116,117,118,98,119,120,121,122],"management","skill management","ontology","v1","create","as","transition","get","manage","update","alpha","list","package","skill package","manifests",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":130,"publishedAt":37},"01M6X5MCV74NHW5MEDNHZRF2C8","schema-management","Manage generated processkit schema contracts through deterministic MCP rebuild and inspection workflows.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fschema-management\u002FSKILL.md",[129],{"categoryNo":103,"categoryName":104,"taxonomyType":105,"taxonomyTypeDesc":106},[131,132,108,133,134,135,136,137,138,139,140,141,35,115,116,118,142],"schema","schema management","contract","rebuild","contracts","workflows","wed","generated","MCP","validation","deterministic","mode",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":149,"publishedAt":37},"01M6X5M5G6YJ96AMZGSCZJ1D13","proposition-management","Record claims, risks, beliefs, world facts, WSJF estimates, and assumptions through the Proposition interface.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fproposition-management\u002FSKILL.md",[],[150,108,151,152,112,153,154,155,35,115,156,157,117,158,118,159,160,161,162,163],"proposition management","proposition","interface","claims","record","world","creation","event","WSJF","index","updates","query","facts","log"]