{
  "schema_version": 2,
  "kind": "shortening-method",
  "format": "agent-skill",
  "id": "configuration-guide",
  "name": "Configuration guide",
  "category": "Technical",
  "summary": "Trim configuration instructions while preserving values, precedence, and effects.",
  "use_cases": [
    "Service configuration docs",
    "Environment-variable guides"
  ],
  "word_count": 150,
  "url": "https://sho.rten.it/methods/configuration-guide/",
  "instructions_url": "https://sho.rten.it/methods/configuration-guide/SKILL.md",
  "skill_url": "https://sho.rten.it/methods/configuration-guide/SKILL.md",
  "json_url": "https://sho.rten.it/methods/configuration-guide/llms.txt",
  "plain_text_url": "https://sho.rten.it/methods/configuration-guide/prompt.txt",
  "license": "MIT",
  "sources_url": "https://sho.rten.it/sources/#configuration-guide",
  "skill_name": "configuration-guide",
  "skill_description": "Trim configuration instructions while preserving values, precedence, and effects. Use for Service configuration docs, Environment-variable guides.",
  "agents_md_url": "https://sho.rten.it/methods/configuration-guide/AGENTS.md",
  "sources": [],
  "instructions": "Condense supplied configuration documentation for someone choosing or changing settings. Keep the decision rules that prevent a valid-looking but incorrect configuration.\n\nGroup settings by purpose. For each relevant setting, keep its exact name, type, allowed values, unit, default, and scope when supplied. Explain precedence, dependencies, restart or reload requirements, and meaningful side effects. Distinguish an unset value from an empty value or zero; these are not interchangeable.\n\nRemove repeated explanations and examples that demonstrate the same rule. Retain one supplied configuration example if it makes a dependency or precedence rule clearer. Keep warnings next to the affected setting. Do not copy secrets into a new example or invent unsupported values.\n\nOutput a compact setting list or table and short application instructions. Include only documented facts, and flag an actual conflict rather than choosing a value. Do not edit configuration, restart a service, or imply that the supplied settings were tested.",
  "example": {
    "context": "Background worker timeouts",
    "before": "The worker uses JOB_TIMEOUT_SECONDS to control the maximum running time of a job. This setting accepts an integer from 1 to 3600, measured in seconds. If the setting is absent, the default is 120. A value of 0 is invalid; it does not disable the timeout. You can also set job_timeout_seconds in worker.toml, but JOB_TIMEOUT_SECONDS takes precedence when both are present. Changes to either setting require a worker restart. Jobs that reach the timeout are marked failed and are not retried unless RETRY_FAILED_JOBS is true. RETRY_FAILED_JOBS defaults to false.",
    "after": "JOB_TIMEOUT_SECONDS: integer 1–3600 seconds; default 120 when absent. Zero is invalid.\nPrecedence: JOB_TIMEOUT_SECONDS overrides worker.toml's job_timeout_seconds.\nApply: Restart workers after changing either setting.\nEffect: Timed-out jobs fail. They retry only when RETRY_FAILED_JOBS=true; default false.",
    "must_preserve": [
      "JOB_TIMEOUT_SECONDS integer 1–3600 seconds; absent default 120",
      "Zero invalid, not timeout disable",
      "Environment setting overrides job_timeout_seconds in worker.toml",
      "Changes require restart",
      "Timed-out jobs fail; retry only if RETRY_FAILED_JOBS true; default false"
    ],
    "kind": "illustrative",
    "omitted": [
      "Repeated setting introductions and the redundant clarification that an invalid zero does not disable the timeout."
    ]
  }
}