agentsclimarketplace

Implementation notes

Skill to4iki/skills/engineering/implementation-notes

A collection of agent skills.

Install
npx -y skills add to4iki/skills --skill implementation-notes

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Implement a spec while keeping a running implementation-notes.html with decisions, deviations, tradeoffs, and open questions. Use for /implementation-notes, @implementation-notes, implementation-notes.html, or when the user wants a spec implemented with a work log.

SKILL.md

1.9 KB, 341 tokens by cl100k_base, as published. Nobody here has run it

Implementation Notes

Implement the spec and keep implementation-notes.html updated as you go so the user can follow how the implementation interprets, decides on, and diverges from the spec without reading every diff.

Invocation

/implementation-notes <SPEC>

<SPEC> is what to implement — a file path, URL, issue/PR reference, or inline requirements in the same message.

If the user invokes the skill without <SPEC>, ask what to implement before coding.

Notes file

  • Default: implementation-notes.html at the project root (self-contained; no external assets).
  • Purpose: leave a human-readable HTML file that lets the user review spec interpretation, implementation differences, and open questions.
  • Capture anything the implementation diverges from, interprets, or adds to the spec as notes the user should know about.

Capture as you work — not only at the end — especially:

  • Design decisions: choices you made where the spec was ambiguous
  • Deviations: places where you intentionally departed from the spec, and why
  • Tradeoffs: alternatives you considered and why you picked what you did
  • Open questions: anything you'd want the user to confirm or revise
  • Verification results (commands run and results)

Link to files; don't paste large code blocks.

HTML usage

Do not make implementation-notes.html a plain text document wrapped in HTML. Use HTML, CSS, SVG, and JavaScript when they make the notes easier to review.

Read references/html-output.md when detailed representation patterns are useful.

When done

Point the user to the notes file and call out open questions and verification results first.

Gives 0 of the 12 instructions most note taking skills give in 341 tokens

Counted across 686 of the 876 authors here whose files we hold, read 2026-08-06

  • include a visual element on every slidein 44 of 686, across 13 files
  • use wikilinks for internal vault linksin 35 of 686, across 11 files
  • commit to a single visual motif across every slidein 34 of 686, across 9 files
  • read pptxgenjs guide before creating presentations from scratchin 30 of 686, across 6 files
  • keep 0.5 inch minimum marginsin 30 of 686, across 7 files
  • use subagents to visually inspect rendered slidesin 30 of 686, across 6 files
  • re-verify affected slides after every fixin 27 of 686, across 5 files
  • run content QA checks before declaring successin 26 of 686, across 3 files
  • Use Markdown links for external URLs onlyin 26 of 686, across 10 files
  • pick a bold topic specific color palettein 24 of 686, across 2 files
  • read editing guide before editing existing presentationsin 23 of 686, across 1 file
  • use one dominant color across all slidesin 23 of 686, across 1 file

Said here and by no other author read

  • implement the requested spec
  • update implementation-notes.html continuously during work
  • ask what to implement if no spec is provided
  • capture design decisions where the spec was ambiguous
  • record verification commands and results
  • link to files instead of pasting large code blocks

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.