New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Output

by HurricaHjz in HurricaHjz/second-yourself

Produce a user-facing DELIVERABLE (report, brief, literature review, slide deck, table, email, outline, …) into the output/ directory — grounded in the wiki and strictly following the user's…

MITAuto-check passedResearch & Science

Install Output

skills CLI
$ npx skills add HurricaHjz/second-yourself --skill output -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install HurricaHjz/second-yourself output --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/HurricaHjz/second-yourself.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/output .claude/skills/output && rm -rf skills-src

Use ~/.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/

Facts

Skill name
output
GitHub stars
123
Token cost
~2k tokens
SKILL.md length
1,015 words
Files
1
Skills in repo
12
Repo updated
First seen
Licence
MIT

At a glance

Produce a user-facing DELIVERABLE (report, brief, literature review, slide deck, table, email, outline, …) into the output/ directory — grounded in the wiki and strictly following the user's…

  • Works in 6 steps: Pin the instruction (no drift) → Ground in the wiki (read first, like… → Separate grounded · general · unknown… → …
  • The user runs /output
  • SKILL.md covers Goal, Triggers, Pipeline and Hard constraints, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Output is an agent skill from HurricaHjz/second-yourself. Produce a user-facing DELIVERABLE (report, brief, literature review, slide deck, table, email, outline, …) into the output/ directory — grounded in the wiki and strictly following the user's instruction. Use when the user runs /output, or says "write/draft/produce/generate me a <X about <Y", "make a <report/brief/deck/email/table from my notes/wiki", or "turn [[topic]] into <format in output/". Distinct from query (answers inline or files a cited synthesis INTO the wiki). The deliverable goes to output/, cites…

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Research & Science, covering Slides and decks, Literature review and Citation management. The repository describes itself as: Second yourself. One agent that remembers you, with many hands to act for you: a multi-agent harness (Claude Code, with Codex helpers), a self-maintaining local wiki as its… The licence is MIT.

When your agent uses it

  • The user runs /output
  • Says write/draft/produce/generate me a <X about <Y
  • Make a <report/brief/deck/email/table from my notes/wiki
  • Turn [[topic]] into <format in output/

Example prompts

  • “s instruction. Use when the user runs /output, or says”
  • “make a <report/brief/deck/email/table from my notes/wiki”
  • “turn [[topic]] into <format in output/”
  • “/output”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Pin the instruction (no drift)
  2. Ground in the wiki (read first, like query)
  3. Separate grounded · general · unknown (anti-hallucination core)
  4. Produce the deliverable, strictly to spec
  5. Write to output/. (never into wiki/)
  6. Report + grounding note

What it can do on your machine

Read from SKILL.md and the folder at commit 17c03f2. It shows what the files ask for, not the result of running them.

  • Tool permissions

    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.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Output loads about 2k tokens when it runs. Until then it costs about 165 tokens; SKILL.md has 1,015 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~165
When it runs · the whole SKILL.md, loaded when a task matches
~2k

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.

Safety

Auto-check passed

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); files beside SKILL.md are not scanned.

SKILL.md

The full file from HurricaHjz/second-yourself at commit 17c03f2, republished under its MIT licence (© HurricaHjz). 1,015 words, ~2,022 tokens.

Download SKILL.mdSave it as .claude/skills/output/SKILL.md (or your agent's skills folder).
name
output
description
Produce a user-facing DELIVERABLE (report, brief, literature review, slide deck, table, email, outline, …) into the output/ directory — grounded in the wiki and strictly following the user's instruction. Use when the user runs /output, or says "write/draft/produce/generate me a <X> about <Y>", "make a <report/brief/deck/email/table> from my notes/wiki", or "turn [[topic]] into <format> in output/". Distinct from `query` (answers inline or files a cited synthesis INTO the wiki). The deliverable goes to output/, cites the wiki pages it draws on, clearly labels any general-knowledge content, and NEVER fabricates facts, figures, quotes or citations.
user-invocable
true

output — generate a grounded deliverable into output/

Goal

Turn a user instruction + the compiled wiki into a deliverable file in output/ that (a) follows the instruction exactly (format, scope, length, audience, style), (b) is grounded in the wiki and cited, and (c) never hallucinates — abstain when unsure rather than confabulate.

Triggers

  • /output <instruction>
  • "write / draft / produce / generate me a <deliverable> about <X>", "make a <report / brief / deck / table / email> from my notes", "turn [[topic]] into <format>".

Pipeline

Step 1 — Pin the instruction (no drift)

Extract a small spec from the user's words: deliverable type · topic/scope · format · length/size · audience · tone · must-include / must-exclude · citation style · output filename. If a material detail is missing or genuinely ambiguous, ask 1–2 crisp questions; otherwise proceed with sensible defaults and state them. Never silently widen, narrow, or reinterpret the ask.

Customisation gap-fill: for spec fields the instruction leaves unstated, check CUSTOMISATION.md → ## Deliverable defaults (if the file and section exist): apply any standing defaults found there (citation style, deck format, length conventions) and note them in the grounding note. An explicit instruction always overrides; if the section is absent or empty, choose sensible defaults yourself (and state them). Conversational output styles never apply to deliverables (CLAUDE.md §1) — this gap-fill covers content-format defaults only. Single source of truth: deliverable defaults live only in that Customisation section — re-read it on every run and never copy its values into this skill, any config, or the deliverable itself (beyond applying them).

Step 2 — Ground in the wiki (read first, like query)

Read wiki/index.md whole (route mode, CLAUDE.md §5), then deep-read the relevant pages (follow ## Related one hop, which widens a shortlist route already produced and never replaces it). Collect the facts you will use together with the page each comes from (for citation). The deliverable is built from compiled knowledge — not guessed. Consult wiki/user/ for personal context when the deliverable is about, or for, the owner. Triage by confidence as query does: lean on authoritative/high pages for load-bearing claims; the field is already in frontmatter, so this is free. If the catalogue under-covers and qmd is active (the qmd-search skill, dormant unless installed), use it as the semantic fallback to locate relevant pages, then deep-read; otherwise grep. Freshness duty: apply query Step 3b to the pages you read — surface stale/contradicted pages in the report line and mark them on-page (flagged: frontmatter / §4.4 block); no extra reads for this.

Step 3 — Separate grounded · general · unknown (anti-hallucination core)

Classify every claim before you write it:

  • Grounded in the wiki → cite the page(s) inline as [[Page]] (or the requested citation style); weight by the page's confidence — state authoritative/high plainly, but attribute and hedge any claim resting only on low/very-low pages.
  • General knowledge the instruction needs but the wiki lacks → include only if clearly labelled (e.g. "(general knowledge — not from the wiki)"). Never present it as wiki-sourced.
  • Unknown / unverifiable → do not invent it. Omit and note the gap, or mark a factual claim unverified. Never fabricate facts, numbers, quotes, or citations. Prefer quoting the raw source over paraphrasing when precision matters.
  • If the instruction needs something neither the wiki nor safe general knowledge can support, say so in the deliverable / report rather than fill the gap with invention.
  • Load-bearing wiki gap → the Step-6 report MAY end with one propose-only gather brief (why · what · how · cost) under the query Step-4b bar and consent ledger (CLAUDE.md §6) — the owner's explicit yes runs it; never proposed in non-interactive runs.
Step 4 — Produce the deliverable, strictly to spec

Write exactly what was asked, in the requested format and length: a Markdown report/brief/review (default), a Marp deck (marp: true frontmatter), a table, an email, a Canvas via the json-canvas skill, etc. Use British/UK English; keep verbatim quotes exact; honour must-include/exclude. Default citations are inline [[wikilinks]] (clickable in Obsidian); use a footnote/bibliography style instead if the deliverable is external-facing or the user asks.

Show full SKILL.md (373 more words)Show less
Step 5 — Write to output/<slug>.<ext> (never into wiki/)

Save to output/ (the deliverables layer — not the knowledge graph). Filename = a clean kebab-case slug + correct extension. Do not modify wiki/ or raw/. (If the user wants the result compounded back into the knowledge base, that's a query synthesis, not an output.) Root vs subfolders (CLAUDE.md §2): the root holds one-off / temporary deliverables; a report (run, morning, audit, review) goes to reports/, the inbox the owner sorts later; standing artefacts live in the matching subfolder (user-notes/ owner quick-references · fundings/ funding applications) and are actively maintained — a run that updates one edits it in place. Create a new subfolder only on the user's instruction. When filing a standing artefact derived from wiki pages, add a "maintained derivative" line to each source page's ## Related so future edits propagate.

Step 6 — Report + grounding note

State the path written, then a concise grounding note: which wiki pages it draws on, what (if anything) is labelled general-knowledge, and any gaps flagged or questions still open — closing with the freshness line (query Step 3b's gate, style-invariant): Freshness: <N> pages read · oldest [[page]] (updated YYYY-MM-DD) · <k> flagged A completion gate: the report is not done without it. A run that read no wiki pages says so instead.

Hard constraints

  • Follow the instruction exactly — format, length, scope, inclusions/exclusions. Use defaults only when unstated, and state them when used.
  • No hallucination. Grounded → cite; general → label; unknown → omit / flag / abstain. Never invent facts, figures, quotes, or citations.
  • Weight by confidence. Prefer higher-confidence wiki pages for key claims; attribute and hedge anything resting only on low/very-low pages.
  • Write only to output/. Never edit wiki/ or raw/. Outputs are deliverables, not knowledge.
  • British/UK English and all other CLAUDE.md rules apply.
  • Not logged by default — a deliverable is not a brain-update (CLAUDE.md §5). Log only if the user asks, or if the run also files a wiki page.

Deliverable graphics (routing rule, moved here from CLAUDE.md §7 on 2026-09-05)

lieflat-charts for browser-viewed HTML and interactive charts, dashboards and full-page HTML reports (some templates need CDN network); scientific-figure-making (from figures4papers) for publication-grade matplotlib figures for papers, theses and slides (PDF or PNG for LaTeX). Rule of thumb: web-viewed → lieflat-charts; print or venue-bound → scientific-figure-making. Both are auto rows in wiki/developments/capability-register.md.

© HurricaHjz, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/output of HurricaHjz/second-yourself.

Open the folder on GitHubat commit 17c03f2

Compare with similar skills

Output 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.

Output compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Output this skillHurricaHjz/second-yourself123—~2kAutomated safety check: PassMIT
Academic Paper Writing PipelineImbad0202/academic-research-skills51k—~16kAutomated safety check: PassCustom licence
Academic Integrity Rewritelin1111-1/academic-integrity-rewrite102—~1.1kAutomated safety check: PassMIT
Live Researchbrightdata/skills264—~1.8kAutomated safety check: PassMIT
Zotero Obsidian BridgeGalaxy-Dawn/claude-scholar5.7k—~514Automated safety check: PassMIT
Scholar RAGjoshzyj/open-scholar-skill168—~7.4kAutomated safety check: NotesCustom licence

Similar skills

  • Academic Paper Writing Pipeline

    Imbad0202/academic-research-skills

    Runs a 12-agent pipeline that plans, drafts, cites, reviews and formats academic papers, with modes for revision, rebuttals, abstracts and citation checks.

    51k GitHub stars~16k tokensUpdated yesterday
    Research & ScienceAuto-check passed

  • Academic Integrity Rewrite

    lin1111-1/academic-integrity-rewrite

    Revise Chinese or English academic writing for lower unnecessary textual overlap while preserving meaning, evidence, numbers, equations, terminology, and citations.

    102 GitHub stars~1.1k tokensUpdated 29 days ago
    Research & ScienceAuto-check passed

  • Live Research

    brightdata/skills

    Produce a deep, multi-source, cited research brief on a topic from live web data using Bright Data's Discover API (intent-ranked web search + parsed page content).

    264 GitHub stars~1.8k tokensUpdated 3 days ago
    Research & ScienceAuto-check passed

  • Zotero Obsidian Bridge

    Galaxy-Dawn/claude-scholar

    Moves papers from Zotero into an Obsidian project knowledge base as source notes, literature synthesis and writing outputs, with evidence records behind every promoted claim.

    5.7k GitHub stars~514 tokensUpdated 17 days ago
    Research & ScienceAuto-check passed

  • Scholar RAG

    joshzyj/open-scholar-skill

    Build and query a local vector database + GraphRAG over your entire reference library (Zotero or a PDF folder) for literature review.

    168 GitHub stars~7.4k tokensUpdated 22 days ago
    Research & ScienceAuto-check: notes

  • Ieee Paper Reader

    CloudWave818/ieee-skills

    Read, decompose, and analyze IEEE-style papers using routed technical-reading workflows.

    359 GitHub stars~591 tokensUpdated 1 mo ago
    Research & ScienceAuto-check passed

More from HurricaHjz/second-yourself

All 12 skills in this repo

  • Qmd Search

    HurricaHjz/second-yourself

    OPTIONAL, DORMANT semantic-search layer over the wiki, powered by qmd (local hybrid BM25 + vector + rerank).

    123 GitHub stars~1.9k tokensUpdated 8 days ago
    Auto-check passed

  • Query

    HurricaHjz/second-yourself

    Answer questions against the local Obsidian wiki — not from model memory.

    123 GitHub stars~2.2k tokensUpdated 8 days ago
    Auto-check passed

  • Export Template

    HurricaHjz/second-yourself

    Sync THIS LLM-Wiki framework with its public GitHub repo, ONE direction per run: --push (vault → repo) publishes your framework; --pull (repo → vault) updates your framework from a newer repo version.

    123 GitHub stars~4.8k tokensUpdated 8 days ago
    Auto-check: warnings

  • Lint

    HurricaHjz/second-yourself

    Health-check the Obsidian wiki — the "static analysis" pass for a knowledge base.

    123 GitHub stars~6.3k tokensUpdated 8 days ago
    Auto-check passed

  • Compile Core

    HurricaHjz/second-yourself

    The compile lane's half of the ingest skill: choose a source's depth after reading it, write the source page from the depth's template, assign confidence, network the knowledge, and propose the…

    123 GitHub stars~4.4k tokensUpdated 8 days ago
    Auto-check passed

  • Lint Slice

    HurricaHjz/second-yourself

    The read-only half of the lint skill for a headless lane: index consistency, link and orphan health, the pending-flag count, the attic, qmd-registry, injection, customisation-pairing and…

    123 GitHub stars~3.5k tokensUpdated 8 days ago
    Auto-check passed

Categories

Questions about Output

What does Output do?

Produce a user-facing DELIVERABLE (report, brief, literature review, slide deck, table, email, outline, …) into the output/ directory — grounded in the wiki and strictly following the user's…. Output is an agent skill from HurricaHjz/second-yourself. Produce a user-facing DELIVERABLE (report, brief, literature review, slide deck, table, email, outline, …) into the output/ directory — grounded in the wiki and strictly following the user's instruction.

When should I use Output?

Output fits situations like: the user runs /output; says write/draft/produce/generate me a <X about <Y; make a <report/brief/deck/email/table from my notes/wiki; turn [[topic]] into <format in output/.

How do I install Output in Claude Code?

Run `npx skills add HurricaHjz/second-yourself --skill output -a claude-code`. Or copy the skill folder (.claude/skills/output in HurricaHjz/second-yourself) into .claude/skills/output in your project. Claude Code loads it when a task matches its description.

How do I install Output in Codex?

Run `npx skills add HurricaHjz/second-yourself --skill output -a codex`. Or copy the skill folder (.claude/skills/output in HurricaHjz/second-yourself) into .agents/skills/output in your project. Codex loads it when a task matches its description.

Can I use Output in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add HurricaHjz/second-yourself --skill output -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/output, .gemini/skills/output, .github/skills/output and .opencode/skills/output in your project.

What does Output need to run?

SKILL.md names no scripts, command-line tools or credentials: Output is instructions for the agent only.

Does Output access the network?

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.

Is Output safe to install?

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. Review the folder before installing.

What licence does Output use?

Output is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Output use?

About 2k tokens (SKILL.md is roughly 8.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Output?

Skills that share tags, products or a category with Output: Academic Paper Writing Pipeline (Imbad0202/academic-research-skills, 51k stars), Academic Integrity Rewrite (lin1111-1/academic-integrity-rewrite, 102 stars), Live Research (brightdata/skills, 264 stars) and Zotero Obsidian Bridge (Galaxy-Dawn/claude-scholar, 5.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Output?

HurricaHjz (a GitHub user) maintains it in HurricaHjz/second-yourself, which has 123 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 1, 2026.

Source: HurricaHjz/second-yourself on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.