TypingMindTypingMindThe best frontend for AI
Review Artifact Comments logo

Review Artifact Comments

Community
yonatangross
review-artifact-comments

Works through the review comments written into a task artifact (plan or research under .ork/tasks/TASK/): lists the open ones, asks how to proceed, then replies, resolves or hands off to iterate-plan or iterate-research, and approves the artifact once nothing is open. Use when a reviewer has commented on an artifact file or asks to address, resolve or approve its comments.

Overview

Publisheryonatangross
Repositoryorchestkit
Skill namereview-artifact-comments
Stars
299
Forks
38
Bundled files
1
LicenseMIT
Links
Skill sourceRepositoryHomepage
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by yonatangross on GitHub. Read the source before you install it.

Installation

Install the Review Artifact Comments AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/yonatangross/orchestkit/tree/main/plugins/ork/skills/review-artifact-comments
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/yonatangross/orchestkit.git /tmp/orchestkit
mkdir -p .claude/skills
cp -r /tmp/orchestkit/plugins/ork/skills/review-artifact-comments .claude/skills/review-artifact-comments
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Review Artifact Comments in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Review Artifact Comments on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Review Artifact Comments is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

review-artifact-comments

Comments live inside the artifact, in the block at its end (format: the create-plan skill's references/artifact-layout.md). A reviewer adds one with the script or types it into the block by hand; both are read the same way. Nothing here deletes a comment.

Steps

  1. Pick the artifact. Use the file given. Otherwise list the task directory and ask which one:

    bash
    node "${CLAUDE_SKILL_DIR}/scripts/artifact.mjs" status --task-dir .ork/tasks/<task>

  2. Read the artifact in full, then its open comments:

    bash
    node "${CLAUDE_SKILL_DIR}/scripts/artifact.mjs" list --file <artifact> --open

  3. Ask how to proceed unless the user already said (AskUserQuestion), for example:

    • revise the artifact from the comments (hand off to /ork:iterate-plan or /ork:iterate-research)
    • revise and resolve the comments it settles
    • investigate the comments and reply with findings, no revision

  4. Work one comment at a time. Check the claim in the code before answering. Reply with what you found or changed:

    bash
    node "${CLAUDE_SKILL_DIR}/scripts/artifact.mjs" reply   --file <artifact> --id c1 --author Claude --text "..."
node "${CLAUDE_SKILL_DIR}/scripts/artifact.mjs" resolve --file <artifact> --id c1 --author Claude --text "..."

    Resolve only when told to, or when the reply records a fix already made.

  5. Approve only for the reviewer, never for the author. The approver is the reviewing seat, and --ref names the LAND message or comment id the approval rests on. The script refuses while a comment is open or when --by is the artifact's author (exit 1), and without --by or --ref (exit 2):

    bash
    node "${CLAUDE_SKILL_DIR}/scripts/artifact.mjs" approve --file <artifact> --by <reviewer seat> --ref <LAND or comment id>

    An approved artifact with no open comment is the "phase done" signal other tools read.

Adding a comment as a reviewer

bash
node "${CLAUDE_SKILL_DIR}/scripts/artifact.mjs" comment --file <artifact> \
  --author "<name>" --quote "<the line it is about>" --text "<the comment>"

Rules

  • Never resolve or approve on your own initiative; those are the reviewer's calls.
  • Never edit the comment block with Write or Edit.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Review Artifact Comments AI skill do?

Works through the review comments written into a task artifact (plan or research under .ork/tasks/TASK/): lists the open ones, asks how to proceed, then replies, resolves or hands off to iterate-plan or iterate-research, and approves the artifact once nothing is open. Use when a reviewer has commented on an artifact file or asks to address, resolve or approve its comments.

Why use Review Artifact Comments on TypingMind?

Because you install it once and use it with any model. Review Artifact Comments is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Review Artifact Comments in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/yonatangross/orchestkit/tree/main/plugins/ork/skills/review-artifact-comments. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Review Artifact Comments?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Review Artifact Comments?

As many as you like. As long as a model supports skills, you can use Review Artifact Comments with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Review Artifact Comments AI skill free?

Yes. It is published on GitHub by yonatangross under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Related AI Skills

View all
nexu-io logo

Html Ppt Zhangzara Vellum

nexu-io
OrganizationPopular

A humanities lecture: how Renaissance linear perspective reshaped early cartography — sources, argument, and evidence. Built as a decision-grade academic research deck for faculty, graduate seminar.

11.5K
98.9K
2 files
View
nexu-io logo

Kami Deck

nexu-io
OrganizationPopular

A lab-meeting deck on gut-microbiome links to sleep quality — the design, the results, the caveats, and the next experiment. Built as a decision-grade academic research deck for lab group, PI.

11.5K
98.9K
1 files
View
nexu-io logo

Last30days

nexu-io
OrganizationPopular

Recent community and social trend research over the last 30 days. Use when the brief asks what people are saying now, recent sentiment, community reactions, social proof, launch reaction, trend scan,…

11.5K
98.9K
58 files
View
ruvnet logo

Swarm Advanced

ruvnet
CommunityPopular

Advanced swarm orchestration patterns for research, development, testing, and complex distributed workflows

12.8K
97.4K
Instructions
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇