القائمة
Render markdown tables as hand-drawn sketch images. Use when user wants a table rendered as an image, visual table, or diagram illustration.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | table-image |
| description | Render markdown tables as hand-drawn sketch images. Use when user wants a table rendered as an image, visual table, or diagram illustration. |
| allowed-tools | ["Bash","Read"] |
| compatibility | Requires GEMINI_API_KEY or GOOGLE_API_KEY in environment. Uses ~/.claude/skills/_generate_image.py |
Render markdown tables and diagrams as hand-drawn sketch images using Gemini's image generation.
Get the markdown table from the user. The table should be in standard markdown format.
Build a prompt using this structure:
Black and white hand-drawn sketch, loose ink strokes. A clean technical table drawn on
white paper. Minimalist, high contrast, editorial tech illustration. Compact layout,
minimal margins, cropped tightly to the table edges, the table fills the frame. --ar 24:9
[paste the full markdown table here]
uv run ~/.claude/skills/_generate_image.py "<constructed prompt>" --ar 24:9 -o table.png
Report the saved file path and suggest reviewing the image.
Input table:
| Feature | Go | Python | Ruby |
|---------|-----|--------|------|
| Concurrency | goroutines | asyncio | threads |
| Typing | static | dynamic | dynamic |
| Speed | fast | moderate | moderate |
Prompt:
Black and white hand-drawn sketch, loose ink strokes. A clean technical table drawn on
white paper. Minimalist, high contrast, editorial tech illustration. Compact layout,
minimal margins, cropped tightly to the table edges, the table fills the frame. --ar 24:9
| Feature | Go | Python | Ruby |
|---------|-----|--------|------|
| Concurrency | goroutines | asyncio | threads |
| Typing | static | dynamic | dynamic |
| Speed | fast | moderate | moderate |
GEMINI_API_KEY or GOOGLE_API_KEY in environmenttable.png in current directory~/.claude/skills/_generate_image.pyExecution trace capture and token baselining. Use when user says trace, extract trace, count tokens, token baseline, or /harness-trace. Not for harness optimization (use harness-mechanic).
Release prep and tagging with pre-flight verification. Use when user says release, tag, ship it, push to production, create release, or bump version. Not for editing a version string outside a release, a lockfile or a changelog entry by hand, and not for reading what changed in a past release: those are ordinary edits, just do them.
Mine LEARNING.md retrospectives across all repos for recurring failure-modes, then propose harness changes (hooks, rules, skills, checklist items) with falsifiable change-contracts. Also runs the doc-gardening pass over the governance docs (stale rules, dead cross-references, skill-table drift). Use when user says learning loop, mine learnings, recurring failures, what should I fix in my process, cross-repo retrospective, doc gardening, stale docs, or run learning-loop. Runs on human schedule, never autonomously. Not for single-project retrospectives (use learning-docs) or trace/token analysis (use harness-mechanic).
Full contractor-mode loop: sub-protocols (LOCALIZE, BENCH-BASELINE, REPRODUCE, DRIFT), review routing by file pattern, blast radius, UAT, parallelism and effort caps, escalation, just-do-it, goal-backed runs. Load it to RUN that loop, once you have an approved plan and are entering step 1, or when a step needs its detail. It is a protocol, not a way to do the work: it never replaces the language, review or planning skill the task itself calls for, and a task small enough to just edit (SKIP_SET) needs none of it. The always-on spine lives in rules/orchestrator-protocol.md. Not for trace capture (harness-trace) or harness optimization (harness-mechanic).
Ruby on Rails with service-oriented architecture, Dry-validation, Sidekiq/Solid Queue, Hotwire. Use for Rails API, Rails services, Rails forms, RSpec, ActiveRecord, Rails migrations. Not for standalone Ruby gems (use ruby skill), and not for judging whether a migration is safe to run in production (that is the database-reviewer agent).
Get three independent second opinions (isolated Claude + isolated Gemini + isolated DeepSeek) on a problem Claude is analyzing. Use when user says second opinion, another perspective, challenge this approach, or asks gemini/deepseek about a decision, approach, or diagnosis. Also invoke on your own initiative, without being asked: on a complex task before planning, after 2 failed root-cause attempts, on a 🔴 decision (rewrite, core logic, security), or when the review loop is stuck below 80 after 2 fix rounds. Gathers context, writes a focused prompt, calls all reviewers in isolated Docker containers, and synthesizes all viewpoints. Not for reviewing code or changes, even phrased as 'ask gemini to review' (use gemini-review).