Structured Gist

Render explanatory or process-recap prose as a nested lecture-note outline instead of paragraphs — fixed role ladder concept (-) → attribute (▸, a named property) → enumerator (I./A./i./a.) → explanation (↪, one prose sentence, usually a leaf). No plain bullets. Render modes — block (fenced, literal glyphs; default on every surface) and responsive (opt-in real GFM nested list for GitHub bodies and chat replies; glyph-free, role carried by typography). One granularity level (standard); skim and deep are archived. Independent of caveman (structure vs wording). Opt-in report preset (`/structured-

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add domattioli/structured-gist --skill structured-gist
Manual install
git clone --depth 1 https://github.com/domattioli/structured-gist.git /tmp/structured-gist
mkdir -p ~/.claude/skills
cp -r /tmp/structured-gist/skills/structured-gist ~/.claude/skills/structured-gist

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# structured-gist — hierarchical lecture-note output

Replace paragraph printouts (esp. "what I did + my reasoning" recaps) with a nested, easily skimmable outline. Concept, attribute, and enumerator nodes carry structure with terse content; the `↪` hook-arrow carries the prose explanation (usually a branch leaf). Marker type conveys meaning on a fixed depth-ladder — never random. Structure only — wording untouched (independent of caveman).

Full detail beyond this file lives in `reference/` — this file is the ~2-minute read; each `## ` section below links out where there's more.

## Activation

On-demand: `/structured-gist [block [width N|auto]|responsive]`. One granularity level, `standard` (see `## Granularity`). No mode → `block` (default, all surfaces) — override explicitly with `responsive` when a GitHub issue/PR/comment body or chat-app reply needs a real GFM nested list instead of a fenced block. `width` sets the block-mode R11 line budget. Resolution order, first match wins: (1) explicit `width N` or `width auto`; (2) the width the consumer repo's AGENTS.md pins for that surface; (3) for terminal replies only, the host's terminal-width hint (`term_cols=N`), resolved as `auto`; (4) 64. `auto` resolves to clamp(N−8, 32, 120), where N is the terminal width in columns. An explicit `width N` is used as given, with no cap. Files, committed fences, and tool-posted bodies (issue, PR, and comment bodies) skip the hint and use 64 unless a width is set explicitly or pinned. `ST
Read the full skill on GitHub

Details

Skill name
structured-gist
Path
skills/structured-gist/SKILL.md
License
Apache-2.0
Repo updated
23 October 2026

FAQ

What does the Structured Gist skill do?

Render explanatory or process-recap prose as a nested lecture-note outline instead of paragraphs — fixed role ladder concept (-) → attribute (▸, a named property) → enumerator (I./A./i./a.) → explanation (↪, one prose sentence, usually a leaf). No plain bullets. Render modes — block (fenced, literal glyphs; default on every surface) and responsive (opt-in real GFM nested list for GitHub bodies and chat replies; glyph-free, role carried by typography). One granularity level (standard); skim and deep are archived. Independent of caveman (structure vs wording). Opt-in report preset (`/structured-

How do I install the Structured Gist skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add domattioli/structured-gist --skill structured-gist. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Structured Gist popular?

It lives in domattioli/structured-gist, which has 2 GitHub stars and 0 forks, and is included in 1 curated skill list.

Related skills

Prospeak

giorgiozamboni/prospeak

Rewrites EXISTING text into the register of a professional world (board, deck, LinkedIn, postmortem, offerta tecnica, bando, CV), keeping it credible and not AI-sounding: it adds the jargon on purpose. Use whenever the user wants a text to sound more professional, executive, managerial, technical, formal, "da ufficio marketing", to raise or adjust the register, tune the tone for an audience (capo, CFO, cliente, management), calibrate how much English or itanglese to use, or "buzzword it up", even if they never say "corporate". Two dials: five intensity levels and thirteen sector branches (tech

Git & Code ReviewIn 1 list

Dialog Tree

3

ikotelkin/claude-skills

Maintain a visual "dialog tree" — a data file plus a self-contained HTML viewer in the project repo that map the branches of a long conversation (user questions → the steps/variants of the answers) as an interactive tree with resolve/delete marks and a "built up to" marker for incremental updates. Use whenever the user asks to "create/set up a dialog tree", "update the tree", "add this to the tree", "show open branches", or mentions dialog-tree.html — and proactively offer it when a deep-dive discussion branches enough that the user risks losing track of unexplored side-threads.

Git & Code ReviewIn 1 list

Changelog Generator

Automatically creates user-facing changelogs from git commits. Transform technical commit messages into customer-friendly release notes.

Git & Code Review

Shipreel

3

theBstar/shipreel

Turn a pull request into a short narrated walkthrough video (about two and a half minutes) with animated diagrams, code panels, optional screen recordings of the real app, captions, crossfade cuts and an ambient music bed. Runs locally with no paid services by default. Use when asked for a PR video, PR walkthrough, demo video of a change, or "make a shipreel".

Git & Code ReviewIn 1 list

Creating Github Issues From Web Research

jeremylongshore/claude-code-plugins-plus-skills

This skill enhances Claude's ability to conduct web research and translate findings into actionable GitHub issues. It automates the process of extracting key information from web search results and formatting it into a well-structured issue, ready for team action. Use this skill when you need to research a topic and create a corresponding GitHub issue for tracking, collaboration, and task management. Trigger this skill by requesting Claude to "research [topic] and create a ticket" or "find [information] and generate a GitHub issue".

Git & Code Review

Gitlab Skill

5

ekohe/gitlab-skill

GitLab integration for fetching issues/MRs, generating executive summaries, performing comprehensive code reviews, and automating issue resolution workflows. Use when working with GitLab issues, merge requests, or when asked to summarize, review, comment on, or resolve GitLab work items.

Git & Code Review

Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.