[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ECRSCTPZT8PY1HT421D1K4":3,"skill-same:01M7ECRSCTPZT8PY1HT421D1K4":89},{"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":29,"commitSha":30,"skillDirectory":31,"forksCount":32,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":6,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M7ECRSCTPZT8PY1HT421D1K4","relsa-severity-assessment",null,"Multivariate severity assessment and humane endpoint prediction for laboratory animal studies using the RELSA (RELative Severity Assessment) score and ARIMA-based foRcast forecasting. Use when combining welfare readouts — body weight or weight loss, body temperature, clinical or nesting scores, biomarkers, activity, heart rate, burrowing, wheel running — into one severity score per animal per day, when asking which animals are at risk of reaching a humane endpoint or when one will be reached, when defining attention\u002Fdanger zones or thresholds on a severity scale by kernel density estimation, or when reporting severity for a 3Rs, refinement, animal-welfare, or EU Directive 2010\u002F63\u002FEU severity-assessment context. Covers directionality (\"turned\" variables), baseline normalization, reference sets, RELSA weights, ARIMA prediction intervals, and RMSE\u002FPICP\u002FMPIW evaluation.","sanjeevafk\u002Fagent-skills","sanjeevafk","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F230678117?v=4","01M7C540EFY46ETG1NNWKS5X3Q","Sanjeev","01M7C540F366J5C1D587BMKH9Q",0,"MIT","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fscientific-skills\u002Frelsa-severity-assessment\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: relsa-severity-assessment\ndescription: Multivariate severity assessment and humane endpoint prediction for laboratory animal studies using the RELSA (RELative Severity Assessment) score and ARIMA-based foRcast forecasting. Use when combining welfare readouts — body weight or weight loss, body temperature, clinical or nesting scores, biomarkers, activity, heart rate, burrowing, wheel running — into one severity score per animal per day, when asking which animals are at risk of reaching a humane endpoint or when one will be reached, when defining attention\u002Fdanger zones or thresholds on a severity scale by kernel density estimation, or when reporting severity for a 3Rs, refinement, animal-welfare, or EU Directive 2010\u002F63\u002FEU severity-assessment context. Covers directionality (\"turned\" variables), baseline normalization, reference sets, RELSA weights, ARIMA prediction intervals, and RMSE\u002FPICP\u002FMPIW evaluation.\nlicense: MIT\nallowed-tools: Read Write Edit Bash\ncompatibility: Requires Python >=3.10 with numpy, pandas, and scipy; statsmodels >=0.14 for forecasting and matplotlib for figures. Tested with numpy 2.5, pandas 3.0, scipy 1.18, statsmodels 0.14.6. No network access needed.\nmetadata:\n  version: \"1.0\"\n  skill-author: K-Dense Inc.\n---\n\n# RELSA severity assessment and humane endpoint forecasting\n\n## Overview\n\nSeverity assessment in animal research is legally mandatory and scientifically load-bearing:\nit drives humane endpoint decisions, and poor welfare monitoring degrades reproducibility.\nThe usual practice evaluates each readout in isolation — weight loss here, a clinical score\nthere — which makes it hard to say how badly an individual animal is actually doing.\n\nThis skill implements two published procedures that address that:\n\n- **RELSA** (Talbot et al., 2022) combines several outcome measures into one score per animal\n  per time point, expressed *relative to a reference set of known burden*. RELSA = 0 is\n  baseline; RELSA = 1 means the animal has reached the reference set's maximum deviation.\n- **foRcast** (Lutscher et al., 2026) fits an ARIMA model to an individual animal's RELSA\n  trajectory and forecasts the next score with a 95% prediction interval, so animals heading\n  for a humane endpoint can be identified before they get there. Kernel density estimation on\n  the RELSA scale supplies candidate *attention* and *danger* zones for interpretation.\n\nThe point is **refinement**: give at-risk animals attention earlier, and avoid euthanising\nanimals that would have recovered. Both procedures are aids to severity assessment, not\ndecision rules — see [Boundaries](#boundaries-state-these-when-you-report).\n\n## When to use this skill\n\n- Combining weight loss, temperature, clinical scoring, biomarkers, or telemetry into a single\n  per-animal severity score\n- Asking which animals in a cohort are at risk of reaching a humane endpoint, or predicting\n  the severity score at a coming time point\n- Comparing severity between treatment groups, interventions, or animal models on a common\n  relative scale\n- Defining thresholds or zones on a severity scale from the data\n- Writing the severity-assessment section of an animal welfare report, a 3Rs\u002Frefinement\n  analysis, or an application under EU Directive 2010\u002F63\u002FEU\n\nFor general forecasting of a time series that is not a severity score, use\n**timesfm-forecasting** or **statsmodels**. For study design and sample size, use\n**experimental-design** and **statistical-power**.\n\n## Installation\n\n```bash\nuv pip install \"numpy>=1.26\" \"pandas>=2.0\" \"scipy>=1.11\" \"statsmodels>=0.14\" matplotlib\n```\n\n`relsa_score.py` and `kde_thresholds.py` need only numpy\u002Fpandas\u002Fscipy; statsmodels is required\nfor forecasting and matplotlib only for figures.\n\n## Data format\n\nOne row per animal per time point, in a CSV:\n\n| id | treatment | condition | day | temp | weight | score | il6 |\n| --- | --- | --- | --- | --- | --- | --- | --- |\n| M01 | treated | endpoint | -1 | 37.15 | 25.17 | 0 | 35.1 |\n| M01 | treated | endpoint | 0 | 37.26 | 25.25 | 0 | 39.5 |\n| M01 | treated | endpoint | 1 | 35.83 | 23.12 | 4 | 162.0 |\n\n- `id` and a time column (`day`, `time`, `hour`, …) are required; `treatment` and `condition`\n  are optional labels used for grouping and for selecting the reference set.\n- Time may be days, hours, or minutes — just keep it monotonic per animal. The RELSA\n  convention codes the baseline time point as `-1`.\n- **One row per animal per time point.** Average hourly telemetry to one value per interval\n  first (the published models average heart rate, HRV, and temperature, and sum activity).\n- Leave missing measurements empty. They are dropped from the score, never imputed — a\n  missing value treated as \"no deviation\" biases severity downward.\n\n`assets\u002Fexample_cohort.csv` is a small synthetic cohort (6 mice, 9 days, temperature, body\nweight, an 0–8 clinical score, and an IL-6-like biomarker) used by every command below, so\neach one is runnable as written.\n\n## The four decisions that determine the result\n\nMake these explicitly and write them into the methods. Nothing else about the procedure\nmatters as much.\n\n**1. Directionality — which variables rise under worsening?** Falling is the default (body\nweight, activity, food intake, burrowing, wheel running). Variables that *rise* must be\ndeclared as `--turned`: clinical scores, inflammatory biomarkers, fever, tachycardia. Get\nthis wrong and the variable contributes nothing at all, silently, because deviations in the\n\"wrong\" direction are floored at zero. Body temperature is model-dependent — it *falls* in\nsepsis and endotoxaemia, *rises* in fever models. Nothing in the data can settle this for you:\nin the published sepsis model activity legitimately swings further above baseline than below,\nso only a variable that *never once* moves the declared way is detectable, and\n`build_reference()` warns about exactly that case.\n\n**2. The reference set — relative to what?** RELSA scores mean nothing without it. Use the\ngroup assumed to carry the greatest burden in your model (the published studies use the\nhighest-dose or endpoint-reaching treatment group). Too mild a reference pushes every score\nabove 1; too severe compresses everything toward 0. Save it with `--save-reference` and reuse\nit with `--load-reference` so later cohorts stay on the same scale.\n\n**3. Scores with a zero baseline.** A clinical score of 0 in a healthy animal cannot be\nratio-normalized — `0\u002F0` is undefined. Use `--score-scale score=8` to map the score's scale\ninstead (healthy → 100%, worst possible → 200%), which also marks it as turned. This mapping\nis a modelling choice about how much one score point is worth relative to one percent of body\nweight; state it. The alternative is to keep the score out of RELSA and use it as an\nindependent endpoint criterion.\n\n**4. Which variables are measured throughout.** Because the score averages over whichever\nvariables are available, a variable that appears or disappears mid-trajectory moves the score\nby itself. In the published sepsis data, adding body weight — recorded only on the day of\neuthanasia — drops that animal's endpoint score from 0.93 to 0.83 for no biological reason.\n`relsa_scores()` warns when composition changes; score the variables present throughout.\n\n## Workflow\n\n### Step 1 — compute RELSA scores\n\n```bash\npython scripts\u002Frelsa_score.py assets\u002Fexample_cohort.csv \\\n    --variables weight,temp,score,il6 \\\n    --normalize weight,temp,il6 \\\n    --turned il6 \\\n    --score-scale score=8 \\\n    --baseline-time -1 \\\n    --reference-group condition=endpoint \\\n    --save-reference reference.json \\\n    --out relsa_scores.csv\n```\n\nThe reference model is echoed so the scale is auditable:\n\n```\nreference model: assets\u002Fexample_cohort.csv [condition=endpoint]\n  animals=2  rows=18  baseline_time=-1.0\n  variable      turned   max reached   max delta\n  weight            no         82.40       17.60\n  temp              no         92.79        7.21\n  score            yes        187.50       87.50\n  il6              yes        797.72      697.72\n```\n\n`relsa_scores.csv` holds each variable's weight alongside the score, which is what makes a\nscore explainable — here M01 deteriorating to its endpoint, M03 peaking on day 3 and\nrecovering:\n\n```\n id  time  weight  temp  score  il6  n_vars  relsa\nM01     1    0.46  0.49   0.57 0.52       4   0.51\nM01     3    0.84  0.76   1.00 0.89       4   0.88\nM01     5    1.00  1.00   1.00 1.00       4   1.00\nM03     3    0.56  0.44   0.57 0.54       4   0.53\nM03     5    0.35  0.26   0.43 0.32       4   0.35\nM03     7    0.12  0.06   0.14 0.11       4   0.11\n```\n\nA weight of 1.00 means that variable hit the reference maximum; `n_vars` is how many\nvariables entered the score at that time point.\n\nSame thing from Python, when you need the objects:\n\n```python\nimport sys; sys.path.insert(0, \"scripts\")\nfrom _common import read_relsa_table, score_to_percent\nfrom relsa_score import prepare, build_reference, relsa_scores\n\nframe = read_relsa_table(\"assets\u002Fexample_cohort.csv\")\nframe[\"score\"] = score_to_percent(frame[\"score\"], max_score=8)   # 0-8 clinical score\nVARS, TURNED = [\"weight\", \"temp\", \"score\", \"il6\"], [\"score\", \"il6\"]\n\nprepared  = prepare(frame, normalize=[\"weight\", \"temp\", \"il6\"], baseline_time=-1)\nreference = build_reference(prepared[prepared.condition == \"endpoint\"],\n                           variables=VARS, turned=TURNED, baseline_time=-1,\n                           label=\"endpoint-reaching animals\")\nscores    = relsa_scores(prepared, reference)\n```\n\n### Step 2 — forecast the endpoint\n\nTrain on everything up to the time point *before* the endpoint, predict the score at the\nendpoint, and score the prediction:\n\n```bash\npython scripts\u002Fforecast_relsa.py relsa_scores.csv \\\n    --animals M01,M02 --endpoints M01=5 --endpoints M02=6 \\\n    --group-col condition --plot-dir figs --endpoint-line 1.0\n```\n\n```\n id  time  predicted    lower    upper        model  actual\nM01   5.0   0.932585 0.670443 1.194728 ARIMA(1,1,0)    1.00\nM02   6.0   0.955696 0.748309 1.163084 ARIMA(1,1,0)    0.94\n\n   group             id        model  n   rmse  picp  mpiw\nendpoint            M01 ARIMA(1,1,0)  1 0.0674 100.0 0.524\nendpoint            M02 ARIMA(1,1,0)  1 0.0157 100.0 0.415\nendpoint -- endpoint --               2 0.0489 100.0 0.470\n                OVERALL               2 0.0489 100.0 0.470\n```\n\nReport all three metrics together. **RMSE** is point accuracy, **PICP** the percentage of\nactual values inside the interval, and **MPIW** the mean interval width in RELSA units — a\nmodel can reach PICP = 100% by making the interval so wide it says nothing, which is exactly\nwhat the paper's pancreatic cancer row (PICP 100%, MPIW 7.35, i.e. 735% of the RELSA range)\nshows.\n\nFor live monitoring, forecast one step ahead at every time point instead:\n\n```bash\npython scripts\u002Fforecast_relsa.py relsa_scores.csv --mode rolling --animals M03\n```\n\nTwo things to know before trusting a forecast:\n\n- **Interpolation is on by default** (`--interpolate-step 0.1`), because one measurement per\n  day is far too sparse for ARIMA. It buys usable model selection and narrower intervals at\n  the cost of honest uncertainty. Set `--interpolate-step 0` when measurement frequency\n  allows.\n- **ARIMA cannot predict a cliff.** It assumes stationarity and linearity, so an abrupt\n  collapse in the last hours before an endpoint will not be forecast from a smooth prior\n  trajectory — the paper's own failure case. Act on the *upper* bound of the interval, and\n  never let a low forecast override an animal that looks unwell.\n\n### Step 3 — put the score in context with severity zones\n\n```bash\npython scripts\u002Fkde_thresholds.py relsa_scores.csv \\\n    --group treatment=treated --n-thresholds 2 --plot zones.png --json zones.json\n```\n\n```\nKDE on 33 RELSA scores  (bandwidth = 0.1502)\n  candidate thresholds (density minima): 0.703\n  density modes: 0.264, 0.866\n  normal    [0.000, 0.703)  n=25 (75.8%)\n  danger    >= 0.703  n=8 (24.2%)\n```\n\nThresholds are the *minima* of the score density — the sparse valleys between clusters of\nscores. Include endpoint animals, survivors, and shams: the zones are meant to separate\nthose states, so all of them must be represented.\n\n**Check the bandwidth before believing a threshold.** On the published sepsis data this\nimplementation finds minima at 0.355 and 0.655 (published: 0.337 and 0.643) — but a 10%\nlarger bandwidth removes both minima entirely. Run the sweep in\n`references\u002Fthresholds-and-zones.md` and report the sweep, not a bare pair of numbers. An\nempty threshold list is a legitimate answer: the scores form one cluster and there is no\ndata-driven place to cut.\n\n## Boundaries: state these when you report\n\n- **RELSA is an aid to severity assessment, not a decisive parameter.** An animal with a low\n  RELSA score that shows other signs of distress must still be handled accordingly. Neither\n  procedure is a validated predictor of death.\n- **KDE zones are not regulatory severity gradings.** EU Directive 2010\u002F63\u002FEU's categories\n  (non-recovery, mild, moderate, severe) are assigned prospectively by a different process.\n  The paper is explicit that its thresholds \"should not be confused with regulatory severity\n  gradings\" and are not directly translatable to them.\n- **Scores are not comparable across reference sets or models.** RELSA is relative by\n  construction, and clinical scoring is not harmonized between laboratories. Always report\n  the reference set with the score.\n- **The published evidence is a proof of concept**: 13 animals across seven models, five of\n  those rows resting on one or two animals. The overall RMSE of 0.069 and PICP of 96% come\n  from 13 endpoint predictions.\n- **An underestimated score is the dangerous error**, because it discourages attention and can\n  delay a euthanasia decision, whereas an overestimate merely prompts extra care.\n\n## Reporting checklist\n\nA severity analysis is reproducible only if all of this is stated:\n\n1. Outcome measures, their units, and their **directionality** (which were turned, and why).\n2. The **baseline** time point or window, and which variables were normalized.\n3. Any **score mapping** applied to ordinal variables, with its scale.\n4. The **reference set**: which animals, which group, how many, and why they are assumed to\n   carry the greatest burden.\n5. Humane endpoint criteria actually applied in the study, separately from the RELSA score.\n6. For forecasts: interpolation step, the selected ARIMA order per animal, and RMSE, PICP,\n   *and* MPIW.\n7. For thresholds: the bandwidth, the number of scores, and a bandwidth sensitivity sweep.\n8. Software versions, and the statement that thresholds are model-specific and not regulatory\n   gradings.\n\n## Common pitfalls\n\n1. **Wrong directionality** — a rising variable not listed in `--turned` contributes exactly\n   zero, silently, and no warning is possible unless it never once falls. Check the reference\n   model table yourself: `max reached` should be below 100 for a falling variable and above 100\n   for a turned one, and `max delta` should be a plausible size for that measure.\n2. **Normalizing a percentage twice** — `bwc [%]` and mapped scores are already on the percent\n   scale; passing them to `--normalize` flattens them.\n3. **A zero baseline** — a clinical score of 0 makes the ratio undefined; the variable becomes\n   all-NaN with a warning. Use `--score-scale`.\n4. **A reference set that does not express the burden** — a variable that never deviates in it\n   raises an error rather than dividing by zero, and one that barely deviates inflates every\n   score.\n5. **Changing variable composition along a trajectory** — see decision 4 above.\n6. **Reading MPIW as a good thing** — a wide interval raises PICP while destroying the\n   forecast's usefulness.\n7. **Reporting a KDE threshold without its bandwidth** — thresholds can vanish under a 10%\n   bandwidth change.\n8. **Treating the forecast as permission to wait** — the model cannot see abrupt\n   deterioration, and the humane endpoint criteria of the protocol always take precedence.\n9. **Comparing RELSA scores between models** — only valid within one reference frame.\n\n## Resources\n\n### Scripts\n\n- `scripts\u002Frelsa_score.py` — the RELSA procedure: `prepare()`, `build_reference()`,\n  `relsa_scores()`, `relsa_weights()`, and a `ReferenceModel` that serialises to JSON.\n  Reproduces the R package's published worked example to two decimals.\n- `scripts\u002Fforecast_relsa.py` — the foRcast tool: `auto_arima()` (Hyndman–Khandakar stepwise\n  AICc selection), `forecast_animal()`, `predict_endpoint()`, `rolling_forecast()`,\n  `forecast_indirect()`, `summarize()`, and Figure-1-style plots.\n- `scripts\u002Fkde_thresholds.py` — severity zones: `bw_nrd0()` (R's bandwidth), `density_curve()`,\n  `find_thresholds()`, zone assignment, and Figure-3-style density plots.\n- `scripts\u002F_common.py` — RELSA-format I\u002FO, validation, `score_to_percent()`,\n  `percent_of_baseline()`, and `forecast_metrics()` (RMSE\u002FPICP\u002FMPIW).\n\n### References\n\n- `references\u002Frelsa-method.md` — the four steps in full, the score\u002Fzero-baseline problem, the\n  variable-composition trap, parity notes against the R package, and the outcome measures and\n  endpoint criteria of all seven published models.\n- `references\u002Fforecasting.md` — ARIMA selection, why interpolation is a distortion, direct vs\n  indirect prediction, the metrics, the published Table 1, and what this port reproduces.\n- `references\u002Fthresholds-and-zones.md` — KDE method, published thresholds, the bandwidth\n  sensitivity sweep, the regulatory boundary, and alternatives when KDE gives nothing.\n\n### Assets\n\n- `assets\u002Fexample_cohort.csv` — synthetic 6-mouse cohort with temperature, body weight, a\n  clinical score, and a biomarker; illustrative only, not real data.\n\n### Related skills\n\n- **experimental-design**, **statistical-power** — designing the study and sizing the groups.\n- **statsmodels**, **timesfm-forecasting** — general time-series modelling.\n- **statistical-analysis**, **scientific-visualization** — group comparisons and figures.\n\n### Key references\n\n- Talbot, S. R. et al. (2022). RELSA — a multidimensional procedure for the comparative\n  assessment of well-being and the quantitative determination of severity in experimental\n  procedures. *Front. Vet. Sci.* 9:937711. R package: \u003Chttps:\u002F\u002Fgithub.com\u002Fmytalbot\u002FRELSA>\n- Lutscher, S. et al. (2026). Refining humane endpoint detection by time-series forecasting\n  and threshold definition using a multivariate severity score. *Front. Physiol.* 17:1869563.\n- Hyndman, R. J. & Khandakar, Y. (2008). Automatic time series forecasting: the forecast\n  package for R. *J. Stat. Softw.* 27, 1–22.\n- EU Commission (2010). Directive 2010\u002F63\u002FEU on the protection of animals used for scientific\n  purposes.\n","# RELSA severity assessment and humane endpoint forecasting\n\n## Overview\n\nSeverity assessment in animal research is legally mandatory and scientifically load-bearing:\nit drives humane endpoint decisions, and poor welfare monitoring degrades reproducibility.\nThe usual practice evaluates each readout in isolation — weight loss here, a clinical score\nthere — which makes it hard to say how badly an individual animal is actually doing.\n\nThis skill implements two published procedures that address that:\n\n- **RELSA** (Talbot et al., 2022) combines several outcome measures into one score per animal\n  per time point, expressed *relative to a reference set of known burden*. RELSA = 0 is\n  baseline; RELSA = 1 means the animal has reached the reference set's maximum deviation.\n- **foRcast** (Lutscher et al., 2026) fits an ARIMA model to an individual animal's RELSA\n  trajectory and forecasts the next score with a 95% prediction interval, so animals heading\n  for a humane endpoint can be identified before they get there. Kernel density estimation on\n  the RELSA scale supplies candidate *attention* and *danger* zones for interpretation.\n\nThe point is **refinement**: give at-risk animals attention earlier, and avoid euthanising\nanimals that would have recovered. Both procedures are aids to severity assessment, not\ndecision rules — see [Boundaries](#boundaries-state-these-when-you-report).\n\n## When to use this skill\n\n- Combining weight loss, temperature, clinical scoring, biomarkers, or telemetry into a single\n  per-animal severity score\n- Asking which animals in a cohort are at risk of reaching a humane endpoint, or predicting\n  the severity score at a coming time point\n- Comparing severity between treatment groups, interventions, or animal models on a common\n  relative scale\n- Defining thresholds or zones on a severity scale from the data\n- Writing the severity-assessment section of an animal welfare report, a 3Rs\u002Frefinement\n  analysis, or an application under EU Directive 2010\u002F63\u002FEU\n\nFor general forecasting of a time series that is not a severity score, use\n**timesfm-forecasting** or **statsmodels**. For study design and sample size, use\n**experimental-design** and **statistical-power**.\n\n## Installation\n\n```bash\nuv pip install \"numpy>=1.26\" \"pandas>=2.0\" \"scipy>=1.11\" \"statsmodels>=0.14\" matplotlib\n```\n\n`relsa_score.py` and `kde_thresholds.py` need only numpy\u002Fpandas\u002Fscipy; statsmodels is required\nfor forecasting and matplotlib only for figures.\n\n## Data format\n\nOne row per animal per time point, in a CSV:\n\n| id | treatment | condition | day | temp | weight | score | il6 |\n| --- | --- | --- | --- | --- | --- | --- | --- |\n| M01 | treated | endpoint | -1 | 37.15 | 25.17 | 0 | 35.1 |\n| M01 | treated | endpoint | 0 | 37.26 | 25.25 | 0 | 39.5 |\n| M01 | treated | endpoint | 1 | 35.83 | 23.12 | 4 | 162.0 |\n\n- `id` and a time column (`day`, `time`, `hour`, …) are required; `treatment` and `condition`\n  are optional labels used for grouping and for selecting the reference set.\n- Time may be days, hours, or minutes — just keep it monotonic per animal. The RELSA\n  convention codes the baseline time point as `-1`.\n- **One row per animal per time point.** Average hourly telemetry to one value per interval\n  first (the published models average heart rate, HRV, and temperature, and sum activity).\n- Leave missing measurements empty. They are dropped from the score, never imputed — a\n  missing value treated as \"no deviation\" biases severity downward.\n\n`assets\u002Fexample_cohort.csv` is a small synthetic cohort (6 mice, 9 days, temperature, body\nweight, an 0–8 clinical score, and an IL-6-like biomarker) used by every command below, so\neach one is runnable as written.\n\n## The four decisions that determine the result\n\nMake these explicitly and write them into the methods. Nothing else about the procedure\nmatters as much.\n\n**1. Directionality — which variables rise under worsening?** Falling is the default (body\nweight, activity, food intake, burrowing, wheel running). Variables that *rise* must be\ndeclared as `--turned`: clinical scores, inflammatory biomarkers, fever, tachycardia. Get\nthis wrong and the variable contributes nothing at all, silently, because deviations in the\n\"wrong\" direction are floored at zero. Body temperature is model-dependent — it *falls* in\nsepsis and endotoxaemia, *rises* in fever models. Nothing in the data can settle this for you:\nin the published sepsis model activity legitimately swings further above baseline than below,\nso only a variable that *never once* moves the declared way is detectable, and\n`build_reference()` warns about exactly that case.\n\n**2. The reference set — relative to what?** RELSA scores mean nothing without it. Use the\ngroup assumed to carry the greatest burden in your model (the published studies use the\nhighest-dose or endpoint-reaching treatment group). Too mild a reference pushes every score\nabove 1; too severe compresses everything toward 0. Save it with `--save-reference` and reuse\nit with `--load-reference` so later cohorts stay on the same scale.\n\n**3. Scores with a zero baseline.** A clinical score of 0 in a healthy animal cannot be\nratio-normalized — `0\u002F0` is undefined. Use `--score-scale score=8` to map the score's scale\ninstead (healthy → 100%, worst possible → 200%), which also marks it as turned. This mapping\nis a modelling choice about how much one score point is worth relative to one percent of body\nweight; state it. The alternative is to keep the score out of RELSA and use it as an\nindependent endpoint criterion.\n\n**4. Which variables are measured throughout.** Because the score averages over whichever\nvariables are available, a variable that appears or disappears mid-trajectory moves the score\nby itself. In the published sepsis data, adding body weight — recorded only on the day of\neuthanasia — drops that animal's endpoint score from 0.93 to 0.83 for no biological reason.\n`relsa_scores()` warns when composition changes; score the variables present throughout.\n\n## Workflow\n\n### Step 1 — compute RELSA scores\n\n```bash\npython scripts\u002Frelsa_score.py assets\u002Fexample_cohort.csv \\\n    --variables weight,temp,score,il6 \\\n    --normalize weight,temp,il6 \\\n    --turned il6 \\\n    --score-scale score=8 \\\n    --baseline-time -1 \\\n    --reference-group condition=endpoint \\\n    --save-reference reference.json \\\n    --out relsa_scores.csv\n```\n\nThe reference model is echoed so the scale is auditable:\n\n```\nreference model: assets\u002Fexample_cohort.csv [condition=endpoint]\n  animals=2  rows=18  baseline_time=-1.0\n  variable      turned   max reached   max delta\n  weight            no         82.40       17.60\n  temp              no         92.79        7.21\n  score            yes        187.50       87.50\n  il6              yes        797.72      697.72\n```\n\n`relsa_scores.csv` holds each variable's weight alongside the score, which is what makes a\nscore explainable — here M01 deteriorating to its endpoint, M03 peaking on day 3 and\nrecovering:\n\n```\n id  time  weight  temp  score  il6  n_vars  relsa\nM01     1    0.46  0.49   0.57 0.52       4   0.51\nM01     3    0.84  0.76   1.00 0.89       4   0.88\nM01     5    1.00  1.00   1.00 1.00       4   1.00\nM03     3    0.56  0.44   0.57 0.54       4   0.53\nM03     5    0.35  0.26   0.43 0.32       4   0.35\nM03     7    0.12  0.06   0.14 0.11       4   0.11\n```\n\nA weight of 1.00 means that variable hit the reference maximum; `n_vars` is how many\nvariables entered the score at that time point.\n\nSame thing from Python, when you need the objects:\n\n```python\nimport sys; sys.path.insert(0, \"scripts\")\nfrom _common import read_relsa_table, score_to_percent\nfrom relsa_score import prepare, build_reference, relsa_scores\n\nframe = read_relsa_table(\"assets\u002Fexample_cohort.csv\")\nframe[\"score\"] = score_to_percent(frame[\"score\"], max_score=8)   # 0-8 clinical score\nVARS, TURNED = [\"weight\", \"temp\", \"score\", \"il6\"], [\"score\", \"il6\"]\n\nprepared  = prepare(frame, normalize=[\"weight\", \"temp\", \"il6\"], baseline_time=-1)\nreference = build_reference(prepared[prepared.condition == \"endpoint\"],\n                           variables=VARS, turned=TURNED, baseline_time=-1,\n                           label=\"endpoint-reaching animals\")\nscores    = relsa_scores(prepared, reference)\n```\n\n### Step 2 — forecast the endpoint\n\nTrain on everything up to the time point *before* the endpoint, predict the score at the\nendpoint, and score the prediction:\n\n```bash\npython scripts\u002Fforecast_relsa.py relsa_scores.csv \\\n    --animals M01,M02 --endpoints M01=5 --endpoints M02=6 \\\n    --group-col condition --plot-dir figs --endpoint-line 1.0\n```\n\n```\n id  time  predicted    lower    upper        model  actual\nM01   5.0   0.932585 0.670443 1.194728 ARIMA(1,1,0)    1.00\nM02   6.0   0.955696 0.748309 1.163084 ARIMA(1,1,0)    0.94\n\n   group             id        model  n   rmse  picp  mpiw\nendpoint            M01 ARIMA(1,1,0)  1 0.0674 100.0 0.524\nendpoint            M02 ARIMA(1,1,0)  1 0.0157 100.0 0.415\nendpoint -- endpoint --               2 0.0489 100.0 0.470\n                OVERALL               2 0.0489 100.0 0.470\n```\n\nReport all three metrics together. **RMSE** is point accuracy, **PICP** the percentage of\nactual values inside the interval, and **MPIW** the mean interval width in RELSA units — a\nmodel can reach PICP = 100% by making the interval so wide it says nothing, which is exactly\nwhat the paper's pancreatic cancer row (PICP 100%, MPIW 7.35, i.e. 735% of the RELSA range)\nshows.\n\nFor live monitoring, forecast one step ahead at every time point instead:\n\n```bash\npython scripts\u002Fforecast_relsa.py relsa_scores.csv --mode rolling --animals M03\n```\n\nTwo things to know before trusting a forecast:\n\n- **Interpolation is on by default** (`--interpolate-step 0.1`), because one measurement per\n  day is far too sparse for ARIMA. It buys usable model selection and narrower intervals at\n  the cost of honest uncertainty. Set `--interpolate-step 0` when measurement frequency\n  allows.\n- **ARIMA cannot predict a cliff.** It assumes stationarity and linearity, so an abrupt\n  collapse in the last hours before an endpoint will not be forecast from a smooth prior\n  trajectory — the paper's own failure case. Act on the *upper* bound of the interval, and\n  never let a low forecast override an animal that looks unwell.\n\n### Step 3 — put the score in context with severity zones\n\n```bash\npython scripts\u002Fkde_thresholds.py relsa_scores.csv \\\n    --group treatment=treated --n-thresholds 2 --plot zones.png --json zones.json\n```\n\n```\nKDE on 33 RELSA scores  (bandwidth = 0.1502)\n  candidate thresholds (density minima): 0.703\n  density modes: 0.264, 0.866\n  normal    [0.000, 0.703)  n=25 (75.8%)\n  danger    >= 0.703  n=8 (24.2%)\n```\n\nThresholds are the *minima* of the score density — the sparse valleys between clusters of\nscores. Include endpoint animals, survivors, and shams: the zones are meant to separate\nthose states, so all of them must be represented.\n\n**Check the bandwidth before believing a threshold.** On the published sepsis data this\nimplementation finds minima at 0.355 and 0.655 (published: 0.337 and 0.643) — but a 10%\nlarger bandwidth removes both minima entirely. Run the sweep in\n`references\u002Fthresholds-and-zones.md` and report the sweep, not a bare pair of numbers. An\nempty threshold list is a legitimate answer: the scores form one cluster and there is no\ndata-driven place to cut.\n\n## Boundaries: state these when you report\n\n- **RELSA is an aid to severity assessment, not a decisive parameter.** An animal with a low\n  RELSA score that shows other signs of distress must still be handled accordingly. Neither\n  procedure is a validated predictor of death.\n- **KDE zones are not regulatory severity gradings.** EU Directive 2010\u002F63\u002FEU's categories\n  (non-recovery, mild, moderate, severe) are assigned prospectively by a different process.\n  The paper is explicit that its thresholds \"should not be confused with regulatory severity\n  gradings\" and are not directly translatable to them.\n- **Scores are not comparable across reference sets or models.** RELSA is relative by\n  construction, and clinical scoring is not harmonized between laboratories. Always report\n  the reference set with the score.\n- **The published evidence is a proof of concept**: 13 animals across seven models, five of\n  those rows resting on one or two animals. The overall RMSE of 0.069 and PICP of 96% come\n  from 13 endpoint predictions.\n- **An underestimated score is the dangerous error**, because it discourages attention and can\n  delay a euthanasia decision, whereas an overestimate merely prompts extra care.\n\n## Reporting checklist\n\nA severity analysis is reproducible only if all of this is stated:\n\n1. Outcome measures, their units, and their **directionality** (which were turned, and why).\n2. The **baseline** time point or window, and which variables were normalized.\n3. Any **score mapping** applied to ordinal variables, with its scale.\n4. The **reference set**: which animals, which group, how many, and why they are assumed to\n   carry the greatest burden.\n5. Humane endpoint criteria actually applied in the study, separately from the RELSA score.\n6. For forecasts: interpolation step, the selected ARIMA order per animal, and RMSE, PICP,\n   *and* MPIW.\n7. For thresholds: the bandwidth, the number of scores, and a bandwidth sensitivity sweep.\n8. Software versions, and the statement that thresholds are model-specific and not regulatory\n   gradings.\n\n## Common pitfalls\n\n1. **Wrong directionality** — a rising variable not listed in `--turned` contributes exactly\n   zero, silently, and no warning is possible unless it never once falls. Check the reference\n   model table yourself: `max reached` should be below 100 for a falling variable and above 100\n   for a turned one, and `max delta` should be a plausible size for that measure.\n2. **Normalizing a percentage twice** — `bwc [%]` and mapped scores are already on the percent\n   scale; passing them to `--normalize` flattens them.\n3. **A zero baseline** — a clinical score of 0 makes the ratio undefined; the variable becomes\n   all-NaN with a warning. Use `--score-scale`.\n4. **A reference set that does not express the burden** — a variable that never deviates in it\n   raises an error rather than dividing by zero, and one that barely deviates inflates every\n   score.\n5. **Changing variable composition along a trajectory** — see decision 4 above.\n6. **Reading MPIW as a good thing** — a wide interval raises PICP while destroying the\n   forecast's usefulness.\n7. **Reporting a KDE threshold without its bandwidth** — thresholds can vanish under a 10%\n   bandwidth change.\n8. **Treating the forecast as permission to wait** — the model cannot see abrupt\n   deterioration, and the humane endpoint criteria of the protocol always take precedence.\n9. **Comparing RELSA scores between models** — only valid within one reference frame.\n\n## Resources\n\n### Scripts\n\n- `scripts\u002Frelsa_score.py` — the RELSA procedure: `prepare()`, `build_reference()`,\n  `relsa_scores()`, `relsa_weights()`, and a `ReferenceModel` that serialises to JSON.\n  Reproduces the R package's published worked example to two decimals.\n- `scripts\u002Fforecast_relsa.py` — the foRcast tool: `auto_arima()` (Hyndman–Khandakar stepwise\n  AICc selection), `forecast_animal()`, `predict_endpoint()`, `rolling_forecast()`,\n  `forecast_indirect()`, `summarize()`, and Figure-1-style plots.\n- `scripts\u002Fkde_thresholds.py` — severity zones: `bw_nrd0()` (R's bandwidth), `density_curve()`,\n  `find_thresholds()`, zone assignment, and Figure-3-style density plots.\n- `scripts\u002F_common.py` — RELSA-format I\u002FO, validation, `score_to_percent()`,\n  `percent_of_baseline()`, and `forecast_metrics()` (RMSE\u002FPICP\u002FMPIW).\n\n### References\n\n- `references\u002Frelsa-method.md` — the four steps in full, the score\u002Fzero-baseline problem, the\n  variable-composition trap, parity notes against the R package, and the outcome measures and\n  endpoint criteria of all seven published models.\n- `references\u002Fforecasting.md` — ARIMA selection, why interpolation is a distortion, direct vs\n  indirect prediction, the metrics, the published Table 1, and what this port reproduces.\n- `references\u002Fthresholds-and-zones.md` — KDE method, published thresholds, the bandwidth\n  sensitivity sweep, the regulatory boundary, and alternatives when KDE gives nothing.\n\n### Assets\n\n- `assets\u002Fexample_cohort.csv` — synthetic 6-mouse cohort with temperature, body weight, a\n  clinical score, and a biomarker; illustrative only, not real data.\n\n### Related skills\n\n- **experimental-design**, **statistical-power** — designing the study and sizing the groups.\n- **statsmodels**, **timesfm-forecasting** — general time-series modelling.\n- **statistical-analysis**, **scientific-visualization** — group comparisons and figures.\n\n### Key references\n\n- Talbot, S. R. et al. (2022). RELSA — a multidimensional procedure for the comparative\n  assessment of well-being and the quantitative determination of severity in experimental\n  procedures. *Front. Vet. Sci.* 9:937711. R package: \u003Chttps:\u002F\u002Fgithub.com\u002Fmytalbot\u002FRELSA>\n- Lutscher, S. et al. (2026). Refining humane endpoint detection by time-series forecasting\n  and threshold definition using a multivariate severity score. *Front. Physiol.* 17:1869563.\n- Hyndman, R. J. & Khandakar, Y. (2008). Automatic time series forecasting: the forecast\n  package for R. *J. Stat. Softw.* 27, 1–22.\n- EU Commission (2010). Directive 2010\u002F63\u002FEU on the protection of animals used for scientific\n  purposes.\n",{"name":5,"license":15,"metadata":24,"description":7,"allowed-tools":27,"compatibility":28},{"version":25,"skill-author":26},"1.0","K-Dense Inc.","Read Write Edit Bash","Requires Python >=3.10 with numpy, pandas, and scipy; statsmodels >=0.14 for forecasting and matplotlib for figures. Tested with numpy 2.5, pandas 3.0, scipy 1.18, statsmodels 0.14.6. No network access needed.","main","4e084e84eb42fc53e144c89c0f7f48b39c8a4b0f","collections\u002Fscientific-skills\u002Frelsa-severity-assessment",1,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills","https:\u002F\u002Fgithub.com\u002Fsanjeevafk","First make it work. Then make it right. Then make it fast.","2026-11-14 13:36:16",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add sanjeevafk\u002Fagent-skills --skill relsa-severity-assessment",{"tool":43,"command":44},"bunx","bunx skills add sanjeevafk\u002Fagent-skills --skill relsa-severity-assessment",{"tool":46,"command":47},"pnpm","pnpm dlx skills add sanjeevafk\u002Fagent-skills --skill relsa-severity-assessment","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fscientific-skills\u002Frelsa-severity-assessment\u002FSKILL.md",true,[51,57,63,67,71,77,81,85],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"assets\u002Fexample_cohort.csv","ASSET","资产文件",2166,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fscientific-skills\u002Frelsa-severity-assessment\u002Fassets\u002Fexample_cohort.csv",{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fforecasting.md","REFERENCE","参考文档",8824,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fscientific-skills\u002Frelsa-severity-assessment\u002Freferences\u002Fforecasting.md",{"path":64,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Frelsa-method.md",10008,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fscientific-skills\u002Frelsa-severity-assessment\u002Freferences\u002Frelsa-method.md",{"path":68,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fthresholds-and-zones.md",7820,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fscientific-skills\u002Frelsa-severity-assessment\u002Freferences\u002Fthresholds-and-zones.md",{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"scripts\u002F_common.py","SCRIPT","脚本",11359,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fscientific-skills\u002Frelsa-severity-assessment\u002Fscripts\u002F_common.py",{"path":78,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":79,"sourceHtmlUrl":80},"scripts\u002Fforecast_relsa.py",29431,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fscientific-skills\u002Frelsa-severity-assessment\u002Fscripts\u002Fforecast_relsa.py",{"path":82,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":83,"sourceHtmlUrl":84},"scripts\u002Fkde_thresholds.py",14420,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fscientific-skills\u002Frelsa-severity-assessment\u002Fscripts\u002Fkde_thresholds.py",{"path":86,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":87,"sourceHtmlUrl":88},"scripts\u002Frelsa_score.py",18887,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fscientific-skills\u002Frelsa-severity-assessment\u002Fscripts\u002Frelsa_score.py",[90,97,105,114,122,129],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M7EFHX67M3KKXT1BXVPA5ADT","zarr-python","Chunked N-D arrays for cloud storage (Zarr-Python 3). Compressed arrays, parallel I\u002FO, S3\u002FGCS via fsspec, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":101,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M7EFFQGM51TZBGRENXY50ZYM","whiteboard-diagrams","Create accurate, simple, hand-drawn whiteboard diagrams from a user's process, system, architecture, learning workflow, comparison, or causal explanation. Use when the user asks for a scribbly whiteboard visual, educational workflow graphic, hand-drawn explainer, or diagram like the bundled reference; ask one focused clarification question when the subject or relationships are missing, then generate and visually verify the final image.","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwhiteboard-diagrams\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwhiteboard-diagrams\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":109,"licenseFileUrl":110,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":19},"01M7EFF1CSQNTDMHFK4ZGY6NYK","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":109,"licenseFileUrl":118,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":19},"01M7EFE8106X6C28FT8PA74427","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-artifacts-builder\u002FSKILL.md",[],[],{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":19},"01M7EFCSNZM9G7ZHS6F127Q71X","verification-loop","A comprehensive verification system for Claude Code sessions.","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fverification-loop\u002FSKILL.md",[],[],{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":133,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":19},"01M7EFCE7EZMKPRYDDNKBQ9EEH","vercel-deploy","Deploy applications and websites to Vercel. Use when the user requests deployment actions like \"deploy my app\", \"deploy and give me the link\", \"push this live\", or \"create a preview deployment\".","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-deploy\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-deploy\u002FSKILL.md",[],[]]