when-to-use-long is agent-read markdown (skill) from korya/askl: dddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddd.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
mdr add korya/askl/when-to-use-long@git:20260902.6253de3mdr add korya/askl/when-to-use-long@sha256:2531c97f9eea9a2aPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_zbmkz3twu6qwspby)
0 badge views in 30 days
korya/askl · 2 stars · license MIT · pushed 2026-09-02 · branch master
GET https://markdownregistry.com/api/v1/artifacts/art_zbmkz3twu6qwspby GET https://markdownregistry.com/api/v1/resolve?ref=korya/askl/when-to-use-long GET https://markdownregistry.com/api/v1/blob/2531c97f9eea9a2a324f85f0ba84670965a1eab46a353ae4480bf7f3d5afb16b