dolt-human-visuals

Convert human-facing knowledge entries into HTML visual artifacts for review.

4|5|Updated Nov 5, 2025
One-click install
npx skills add https://github.com/cogni-dao/cogni --skill dolt-human-visuals
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dolt-human-visuals
Source: https://github.com/cogni-dao/cogni/tree/main/.claude/skills/dolt-human-visuals
Command: npx skills add https://github.com/cogni-dao/cogni --skill dolt-human-visuals

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps authors convert text-heavy human-facing knowledge entries into concise, visual HTML artifacts suitable for quick review and approval.

Core Features & Use Cases

  • Converts content into HTML visual format using standardized .cogni-* tokens and components.
  • Encourages use of entryType: html for human review and ensures accessible, sandbox-safe visuals.
  • Use Case: create design diagrams, status scorecards, roadmaps, PR review summaries, and other visuals that are easier to scan than paragraphs.

Quick Start

Post a knowledge entry using HTML visual formatting for human review at the /knowledge/contributions endpoint.

Frequently Asked Questions about dolt-human-visuals

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert text-heavy knowledge entries into HTML visual artifacts for human review?

Convert text-heavy knowledge entries into HTML visual artifacts by applying standardized .cogni-* tokens and components to create concise, sandbox-safe visuals that are easier to scan than paragraphs.

What type of content works best as HTML visual knowledge entries?

HTML visual knowledge entries work best for design diagrams, status scorecards, roadmaps, and PR review summaries where visuals outperform text for quick human review and approval.

How do I post HTML visual knowledge entries via the knowledge contributions endpoint?

Post HTML visual knowledge entries via the knowledge contributions endpoint by submitting content formatted with entryType: html to the /api/v1/knowledge/contributions endpoint.

Does this HTML visual transformation approach enforce specific styling rules for knowledge entries?

The HTML visual transformation enforces knowledge-html-style rules and uses the operator app's .cogni-* classes to ensure accessible, sandbox-safe visuals for human review.

Can I use this approach to create design diagrams and roadmaps for quick approval workflows?

You can use this approach to create design diagrams and roadmaps by transforming human-facing content into concise HTML visual artifacts optimized for quick review and approval workflows.