MCP Server Builder
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
Progressive disclosure for what AI agents produce. An agent skill from magnus919/hermes-profiles.
$ npx skills add magnus919/hermes-profiles --skill artifact-pyramids -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install magnus919/hermes-profiles artifact-pyramids --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/magnus919/hermes-profiles.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/artifact-pyramids .claude/skills/artifact-pyramids && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "artifact-pyramids" agent skill from https://github.com/magnus919/hermes-profiles/tree/main/skills/artifact-pyramids into .claude/skills/artifact-pyramids/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "artifact-pyramids", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/magnus919/hermes-profiles/tree/main/skills/artifact-pyramidsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add magnus919/hermes-profiles --skill artifact-pyramids -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install magnus919/hermes-profiles artifact-pyramids --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/hermes-profiles.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/artifact-pyramids .agents/skills/artifact-pyramids && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "artifact-pyramids" agent skill from https://github.com/magnus919/hermes-profiles/tree/main/skills/artifact-pyramids into .agents/skills/artifact-pyramids/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "artifact-pyramids", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add magnus919/hermes-profiles --skill artifact-pyramids -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install magnus919/hermes-profiles artifact-pyramids --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/hermes-profiles.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/artifact-pyramids .cursor/skills/artifact-pyramids && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "artifact-pyramids" agent skill from https://github.com/magnus919/hermes-profiles/tree/main/skills/artifact-pyramids into .cursor/skills/artifact-pyramids/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "artifact-pyramids", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/magnus919/hermes-profiles.git --path skills/artifact-pyramids--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add magnus919/hermes-profiles --skill artifact-pyramids -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install magnus919/hermes-profiles artifact-pyramids --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/hermes-profiles.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/artifact-pyramids .gemini/skills/artifact-pyramids && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "artifact-pyramids" agent skill from https://github.com/magnus919/hermes-profiles/tree/main/skills/artifact-pyramids into .gemini/skills/artifact-pyramids/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "artifact-pyramids", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install magnus919/hermes-profiles artifact-pyramidsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add magnus919/hermes-profiles --skill artifact-pyramids -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/magnus919/hermes-profiles.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/artifact-pyramids .github/skills/artifact-pyramids && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "artifact-pyramids" agent skill from https://github.com/magnus919/hermes-profiles/tree/main/skills/artifact-pyramids into .github/skills/artifact-pyramids/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "artifact-pyramids", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add magnus919/hermes-profiles --skill artifact-pyramids -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install magnus919/hermes-profiles artifact-pyramids --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/hermes-profiles.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/artifact-pyramids .opencode/skills/artifact-pyramids && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "artifact-pyramids" agent skill from https://github.com/magnus919/hermes-profiles/tree/main/skills/artifact-pyramids into .opencode/skills/artifact-pyramids/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "artifact-pyramids", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
artifact-pyramidsProgressive disclosure for what AI agents produce. An agent skill from magnus919/hermes-profiles.
Artifact Pyramids is an agent skill from magnus919/hermes-profiles. Progressive disclosure for what AI agents produce. Structure research outputs across three layers of increasing depth — Summary (key findings), Analysis Collection (per-dimension files), and Detailed Dossiers (source excerpts, raw data, transcripts) — so downstream agents and humans consume only as deeply as they need. Load this skill when organizing research outputs, building multi-agent research pipelines, or designing agent collaboration protocols.
Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 26 other files, including scripts, reference files and assets (for example `README.md`, `assets/artifact-inventory.md` and `assets/pyramid-template.md`). Compatibility notes: Agent-agnostic — concepts apply to any AI agent workflow. Scripts require Python 3.9+ and a POSIX shell.
It sits in Agent Workflows. The repository describes itself as: Curated Hermes Agent profiles for specialist swarms — opinionated, Hermes-optimized, artifact-pyramid native. The licence is MIT.
7 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 867a555. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Ships 1 file in scripts/, which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Agent-agnostic — concepts apply to any AI agent workflow. Scripts require Python 3.9+ and a POSIX shell.
From compatibility in the SKILL.md frontmatter.
Artifact Pyramids loads about 2.5k tokens when it runs, and up to ~20k if it reads all its reference files. Until then it costs about 118 tokens; SKILL.md has 921 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
The full file from magnus919/hermes-profiles at commit 867a555, republished under its MIT licence (© magnus919). 921 words, ~2,545 tokens.
.claude/skills/artifact-pyramids/SKILL.md (or your agent's skills folder). This skill also uses 24 other files; get the full folder from GitHub.Progressive disclosure governs how we feed agents context: metadata at startup, instructions on activation, resources on demand. The Artifact Pyramid applies the same principle to what agents produce. Three layers of increasing depth, each independently consumable, each linking down to the next.
When producing an artifact pyramid, load these references as a required set (not piecemeal):
| Reference | File |
|---|---|
| Pipeline Stages — layer definitions, navigation format, production flow | references/pipeline-stages.md |
| Output Classification Framework — role-agnostic content contracts, 00-index/L1 boundary | references/output-classification-framework.md |
| Quality Gates — verification checklists per layer | references/quality-gates.md |
| Delegation Context Template — exact text for subagent output mandates | references/delegation-context-template.md |
These four define complementary aspects of the spec that the others assume. Loading only a subset risks violating content contracts (e.g., putting findings in 00-index) or skipping required navigation affordances. Load the full set before writing any pyramid files.
The reference table below describes when to load each file; the four above are always required for pyramid production. The remaining references (framework, worked example, canonical article, intellectual lineage, provenance, composite synthesis) are supplementary — load when the task calls for conceptual depth or a worked pattern.
┌──────────────┐
│ L1 SUMMARY │ One file: research question, key findings,
│ 🎯 │ most important implications. Links to L2 files.
└──────┬───────┘
┌──────┴───────┐
│ L2 ANALYSIS │ Per-dimension files: market, competitive,
│ COLLECTION │ technical feasibility, risk. Self-contained,
│ 🧩 │ each links to L3 dossiers.
└──────┬───────┘
┌──────┴───────┐
│ L3 DOSSIERS │ Source excerpts, raw data tables, interview
│ 📦 │ transcripts, methodology notes. Reference
└──────────────┘ library, pulled on demand.The pyramid is consumed top-down but produced via recursive gap analysis: start with the summary, embed links to analysis files, write analysis files that link to dossiers, and evaluate after each round whether gaps remain.
Layer numbering is top-down — L1 is the most distilled layer (the entry point), L3 is the most detailed (pulled on demand). This mirrors the Agent Skills input model: metadata (L1) → instructions (L2) → resources (L3).
Every file at every layer carries, at the bottom, an explicit SOURCES section with absolute path references and descriptions:
SOURCES (LAYER 2 NAVIGATION)
research/analysis/market-position.md
-> Competitor mapping and market share analysis supporting Section 2
research/analysis/technical-feasibility.md
-> Architecture evaluation supporting Section 3
research/dossiers/competitor-profiles.md
-> Raw competitor data dossiersThese aren't footnotes. They are navigation affordances for agent consumers. Each description answers the question the consuming agent asks before loading: what will I find if I go deeper?
| Reference | Load when | File |
|---|---|---|
| Framework & Symmetry | You need the full conceptual foundation — the asymmetry problem, multi-agent routing, DIKW relationship | references/artifact-pyramid-framework.md |
| Pipeline Stages | You're building or auditing a pyramid — detailed definitions per layer, navigation format, production flow | references/pipeline-stages.md |
| Quality Gates | You need to verify an artifact meets the standard for its layer | references/quality-gates.md |
| Worked Example | You want to see a complete synthetic walkthrough of all three layers | references/synthetic-example.md |
| Canonical Article | Read the published groktop.us piece — the Layer 3 artifact that defines the concept | references/canonical-article.md |
| Intellectual Lineage | How software architecture documentation (4+1 Views, C4, arc42, ADRs) independently discovered progressive disclosure under different names — and what the Artifact Pyramid generalizes beyond them | references/intellectual-lineage.md |
| Methodology-to-Pyramid Mapping | How specialist profiles map domain-specific methodologies into the universal pyramid structure, with dimension boundary rules | references/methodology-to-pyramid-mapping.md |
| Output Classification Framework | Role-agnostic — three questions any specialist can ask to map their outputs into the correct layer: who consumes it, how often, what question it answers. Includes per-layer content contracts to eliminate duplication between 00-index and L1 files. | references/output-classification-framework.md |
| Composite Pyramid Synthesis | How to merge multiple subagent pyramids into a root-level composite pyramid — orchestrator flow, SOURCES convention, worked example from jobs-finder pipeline | references/composite-pyramid-synthesis.md |
| Delegation Context Template | You're delegating research to subagents and need the exact text to include in context strings to ensure artifact-pyramid output | references/delegation-context-template.md |
| Flat-to-Pyramid Migration | You're converting existing flat JSON outputs to artifact-pyramid format — the pattern for L1/L2/L3 structure, 00-index rules, and downstream consumer fallback reads | references/flat-to-pyramid-migration.md |
| Nested Pyramid Pattern | You're designing a single system that produces multiple artifact streams over time (multi-phase, multi-epoch) — avoid scatter, nest epochs under a single root pyramid | references/nested-pyramid-pattern.md |
| Script | Load when | File |
|---|---|---|
| pyramid-status | You want to audit an existing research directory for structural coverage | scripts/pyramid-status.sh |
| extract-atoms | You have raw source text and need candidate atomic claims | scripts/extract-atoms.py |
| Template | Load when | File |
|---|---|---|
| Project Scaffold | You're starting a new research project and need the index skeleton | assets/pyramid-template.md |
| Artifact Inventory | You need to track what exists at each layer across a project | assets/artifact-inventory.md |
# Scaffold a new research project with all three layer directories
mkdir -p my-project/{01-summary,02-analysis,03-dossiers}
cp assets/pyramid-template.md ./my-project/00-index.md
# Check structural coverage of an existing project
scripts/pyramid-status.sh ./my-project
# Extract candidate atoms from source text
scripts/extract-atoms.py ./my-project/03-dossiers/source-1.txtmy-project/
├── 00-index.md # Project scaffold (from template)
├── 01-summary/ # L1: one file — key findings, implications, links to L2
├── 02-analysis/ # L2: per-dimension files (market, competitive, technical)
├── 03-dossiers/ # L3: source excerpts, transcripts, raw data, methodology
└── artifact-inventory.md # Cross-layer tracking (from template)The numbered prefixes mirror the pyramid's top-to-bottom orientation: 01 is most consumed, 03 is pulled on demand.
SOURCES section with absolute paths and descriptions — not footnotes, but agent navigation affordances answering what will I find if I go deeper?epoch-1-validation-edit-3.json), not nested directories. Subdirectories inside 03-dossiers/ violate the flat-file contract and break the SOURCES navigation path.00-index.md, 01-summary/findings.md, and 02-analysis/ trajectory files grow as new data arrives. They are rewritten to reflect the current state. Files in 03-dossiers/ and per-category analysis files below 02-analysis/ are created once and never modified — they represent a fixed point in time.© magnus919, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 24 other files (scripts, references, assets) in skills/artifact-pyramids of magnus919/hermes-profiles.
Open the folder on GitHubat commit 867a555
Artifact Pyramids next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Artifact Pyramids this skillmagnus919/hermes-profiles | 289 | — | ~2.5k | Automated safety check: Pass | MIT | |
| MCP Server Builderanthropics/skills | 180k | 63 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Hook Development for Claude Code Pluginsanthropics/claude-plugins-official | 38k | 10 repos | ~4.1k | Automated safety check: Notes | Apache-2.0 | |
| Using Superpowersfarm-fe/farm | 5.6k | 36 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Executing Plans Inlineobra/superpowers | 297k | 2 repos | ~5.1k | Automated safety check: Pass | MIT | |
| Skill CreatorAzure/azqr | 796 | 89 repos | ~8.2k | Automated safety check: Pass | Apache-2.0 |
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
anthropics/claude-plugins-official
Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.
farm-fe/farm
A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
obra/superpowers
Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.
Azure/azqr
Create new skills, modify and improve existing skills, and measure skill performance.
anthropics/claude-plugins-official
Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.
magnus919/hermes-profiles
PhD-level expertise in data science, statistics, and machine learning.
magnus919/hermes-profiles
Create comprehensive brand identity documentation for any brand.
magnus919/hermes-profiles
Specification authoring for AI-native SDD — writes formal specifications in structured formats (Gherkin, user stories, acceptance criteria), enforces spec quality gates, and produces…
magnus919/hermes-profiles
SDD acceptance criteria verification — maps specification acceptance criteria to tests, validates implementation output against spec requirements, and produces artifact-pyramid-compliant…
magnus919/hermes-profiles
SDD work decomposition — translates formal specifications into dependency-aware task plans with per-task acceptance criteria.
magnus919/hermes-profiles
Full-spectrum SEO + AEO audit skill — technical crawl analysis, on-page content optimization, structured data (JSON-LD/Schema.org) validation, Ghost CMS metadata completion, answer engine…
Categories
Progressive disclosure for what AI agents produce. An agent skill from magnus919/hermes-profiles. Artifact Pyramids is an agent skill from magnus919/hermes-profiles. Progressive disclosure for what AI agents produce.
Artifact Pyramids fits situations like: agent Workflows work in your project.
Run `npx skills add magnus919/hermes-profiles --skill artifact-pyramids -a claude-code`. Or copy the skill folder (skills/artifact-pyramids in magnus919/hermes-profiles) into .claude/skills/artifact-pyramids in your project. Claude Code loads it when a task matches its description.
Run `npx skills add magnus919/hermes-profiles --skill artifact-pyramids -a codex`. Or copy the skill folder (skills/artifact-pyramids in magnus919/hermes-profiles) into .agents/skills/artifact-pyramids in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add magnus919/hermes-profiles --skill artifact-pyramids -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/artifact-pyramids, .gemini/skills/artifact-pyramids, .github/skills/artifact-pyramids and .opencode/skills/artifact-pyramids in your project.
SKILL.md names no scripts, command-line tools or credentials: Artifact Pyramids is instructions for the agent only. Our summary lists: Python 3. Compatibility (from SKILL.md): Agent-agnostic — concepts apply to any AI agent workflow. Scripts require Python 3.9+ and a POSIX shell..
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
Artifact Pyramids is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.5k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 18k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Artifact Pyramids: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 297k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
magnus919 (a GitHub user) maintains it in magnus919/hermes-profiles, which has 289 GitHub stars. The repository holds 31 skills in this directory. The repository was last updated on June 27, 2026.
Source: magnus919/hermes-profiles on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.