Skip to content

anchored-docs v2.0.1

Choose a tag to compare

@github-actions github-actions released this 08 Oct 12:10
· 5 commits to main since this release
23593a7
  • Corrected: the version of the skill is in metadata.version in the frontmatter. Before this change, it was a top-level version key. The Agent Skills specification does not let a skill use that key, and strict validators such as skills-ref validate refuse it.
  • Corrected: INSTALL.md gives the frontmatter keys of the skill correctly.
  • Corrected: when the --repo folder was not there, a sources pattern that starts with ** found a file. After this change, it finds no file, as in 1.2.0.
  • Corrected: ste_check.mjs did not expand ~\ at the start of STE_AGENT_PACK. After this change, ~\ and ~/ go to the home folder, as in STE_ORG_GLOSSARY.
  • Corrected: a command such as head can close the output pipe before the end of the report. Then the two scripts showed a Node.js error and stopped with exit code 1. After this change, they stop with the exit code of the checks and show no error.
  • Corrected: a long line of dots or dashes made ste_check.mjs slow. With 80,000 dots, the check used 4 seconds. The time increased with the square of the length. After this change, the time increases with the length only, and the findings do not change.
  • New: the two scripts show a control character from a doc or an argument as text, for example \x1b for ESC. Before this change, the report contained the raw character, which can change a terminal. SKILL.md tells the agent to use the output of the scripts as data, not as instructions.
  • Corrected: docs_check.mjs map --check gave "out of date" for a _map.json that is not correct JSON. After this change, it stops with exit 2 and a message that names the file, as affected does. map --check also gives the notice for a remaining _map.yaml.
  • Corrected: references/glossary.md and the exit codes in SKILL.md tell where an error message goes and when it gives the position of a JSON error.
  • Corrected: the frontmatter parser reads four structures as YAML reads them. The four structures follow:
    • An apostrophe in a word, as in Don't # note, does not hide the # comment.
    • A colon with no space after it does not make a key. Examples are key:value and http://x.y.
    • A list below a key in a list item is the value of that key. An example is - code: x, then docs:, then - y.
    • A glossary entry with no term text stops the script with a message that names the entry. Before this change, the script did not use the entry and its synonyms, and gave no message.
  • New: docs_check.mjs okf shows each frontmatter line that the parser cannot read, as frontmatter line N not understood. Before this change, the parser did not use the line and gave no message.