agentsclimarketplace

Auto tinker review

Skill NolanCassidy/auto-tinker/skills/auto-tinker-review

Local-first, chat-operated developer experiments, learning history, and approval-gated publishing.

Install
npx -y skills add NolanCassidy/auto-tinker --skill auto-tinker-review

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

2 things to look at

  • 18 days oldThe repository was created 18 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 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

Summarize evidence-backed Auto-Tinker status and inspect the local graph, main-goal progress, queue health, and writing readiness. Use for daily, weekly, project, or capability reviews and questions about what was done, learned, blocked, scheduled, or connected; this skill does not execute code or mutate GitHub.

SKILL.md

2.8 KB, 529 tokens by cl100k_base, as published. Nobody here has run it

Auto-Tinker Review

Review canonical Markdown and exact evidence; do not turn missing repository links into missing knowledge.

Invoke the CLI as auto-tinker; from an unlinked source checkout use npm --prefix <auto-tinker-product-repo> run cli -- followed by the same arguments.

Workflow

  1. For a daily closeout, run auto-tinker history reconcile --workspace <path> --json before summarizing.
  2. Run auto-tinker index, then auto-tinker goal show, auto-tinker graph, auto-tinker queue list, and auto-tinker discover with --json.
  3. Trace claims to event, evidence snapshot, experiment, test, lesson, journal, changelog, or source record IDs.
  4. Classify repository locations as verified local, verified remote, both, missing, or unverified. Preserve and report knowledge nodes that have no repository.
  5. Assess each active/finished item against the one active main goal: contribution, distraction cost, success criteria, and exploration budget. Keep supporting goals separate.
  6. Separate observed facts from inference and unanswered questions. Do not use activity volume as capability growth.
  7. Review an individual writing artifact only on user direction with auto-tinker journal review <journal-id> --state <pending|approved>. This changes writing-review state only.
  8. Generate the requested next action with auto-tinker prompt <intent> [--target <id>] [--agent <name>]; present it as copyable text for a chat agent.

Read review-cadences.md for daily, weekly, and graph-query output contracts.

Boundaries

  • A review is read/reconcile/index work. It does not start coding or publish remotely.
  • Report private-journal, readme, changelog, and public-story as separate linked artifacts with separate readiness.
  • Report readme_review, public_story_review, and repository_publication_approval separately from one another and from actual remote visibility.
  • Never treat journal review, writing_approval, README review, or public-story review as consent to make a repository public.
  • Flag stale machine/profile data, weak evidence, unresolved duplicates, broken links, blocked work, main-goal drift, and privacy risks.
  • The viewer may display these results and edit safe local review/queue state, but it never invokes this skill itself.

Return exact record paths/IDs, evidence strength, changed reconciliation counts, main-goal progress, next decisions, and copyable prompts.

What ships with it: 2 files

2.4 KB alongside SKILL.md

agents/

references/

Keep looking

Skills are one crate of 326,984. 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.