GitHub Deep Research
bytedance/deer-flow
Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.
Share your completed meta-analysis project to the htlin222/meta-pipe GitHub Discussions board.
Install Post To Discussion
$ npx skills add htlin222/meta-pipe --skill post-to-discussion -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install htlin222/meta-pipe post-to-discussion --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/htlin222/meta-pipe.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/post-to-discussion .claude/skills/post-to-discussion && 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 "post-to-discussion" agent skill from https://github.com/htlin222/meta-pipe/tree/main/.claude/skills/post-to-discussion into .claude/skills/post-to-discussion/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "post-to-discussion", 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/htlin222/meta-pipe/tree/main/.claude/skills/post-to-discussionType 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 htlin222/meta-pipe --skill post-to-discussion -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install htlin222/meta-pipe post-to-discussion --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/htlin222/meta-pipe.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/post-to-discussion .agents/skills/post-to-discussion && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "post-to-discussion" agent skill from https://github.com/htlin222/meta-pipe/tree/main/.claude/skills/post-to-discussion into .agents/skills/post-to-discussion/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "post-to-discussion", 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 htlin222/meta-pipe --skill post-to-discussion -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install htlin222/meta-pipe post-to-discussion --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/htlin222/meta-pipe.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/post-to-discussion .cursor/skills/post-to-discussion && 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 "post-to-discussion" agent skill from https://github.com/htlin222/meta-pipe/tree/main/.claude/skills/post-to-discussion into .cursor/skills/post-to-discussion/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "post-to-discussion", 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/htlin222/meta-pipe.git --path .claude/skills/post-to-discussion--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 htlin222/meta-pipe --skill post-to-discussion -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install htlin222/meta-pipe post-to-discussion --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/htlin222/meta-pipe.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/post-to-discussion .gemini/skills/post-to-discussion && 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 "post-to-discussion" agent skill from https://github.com/htlin222/meta-pipe/tree/main/.claude/skills/post-to-discussion into .gemini/skills/post-to-discussion/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "post-to-discussion", 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 htlin222/meta-pipe post-to-discussionInstalls 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 htlin222/meta-pipe --skill post-to-discussion -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/htlin222/meta-pipe.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/post-to-discussion .github/skills/post-to-discussion && 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 "post-to-discussion" agent skill from https://github.com/htlin222/meta-pipe/tree/main/.claude/skills/post-to-discussion into .github/skills/post-to-discussion/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "post-to-discussion", 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 htlin222/meta-pipe --skill post-to-discussion -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install htlin222/meta-pipe post-to-discussion --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/htlin222/meta-pipe.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/post-to-discussion .opencode/skills/post-to-discussion && 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 "post-to-discussion" agent skill from https://github.com/htlin222/meta-pipe/tree/main/.claude/skills/post-to-discussion into .opencode/skills/post-to-discussion/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "post-to-discussion", 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.
Facts
- Skill name
post-to-discussion- GitHub stars
- 139
- Token cost
- ~1.2k tokens
- SKILL.md length
- 302 words
- Files
- 1
- Skills in repo
- 15
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Share your completed meta-analysis project to the htlin222/meta-pipe GitHub Discussions board.
- Works in 5 steps: Ensure figures are committed and pushed → Get the image base URL → Get the Discussion category ID → …
- A project reaches a milestone (analysis complete
- SKILL.md covers Overview, When to Use, Prerequisites and Workflow, plus 4 more sections
- Calls git, gh and jq
What it does
Post To Discussion is an agent skill from htlin222/meta-pipe. Share your completed meta-analysis project to the htlin222/meta-pipe GitHub Discussions board. Use when a project reaches a milestone (analysis complete, manuscript drafted) and the user wants to showcase their work.
Its SKILL.md is about 1.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 Project management. It works with GitHub. The repository describes itself as: Claude Code-powered end-to-end meta-analysis automation: AI-assisted literature review, screening, extraction, analysis, and manuscript generation for systematic reviews and….
When your agent uses it
- A project reaches a milestone (analysis complete
- Manuscript drafted) and the user wants to showcase their work
Example prompts
- “/post-to-discussion”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
- Ensure figures are committed and pushed
- Get the image base URL
- Get the Discussion category ID
- Create the discussion via GraphQL
- Update the body (if needed)
What it can do on your machine
Read from SKILL.md and the folder at commit 5c5c3f0. 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
Shell commands in SKILL.md call:
gitghjq
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.
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
Post To Discussion loads about 1.2k tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 302 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.
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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 302 words (~1,210 tokens).
“Share your meta-analysis project as a GitHub Discussion on htlin222/meta-pipe. This lets other users see real examples of completed analyses, learn from different clinical questions, and reuse methodological approaches.”
- name
- post-to-discussion
Files
Just SKILL.md in .claude/skills/post-to-discussion of htlin222/meta-pipe.
Open the folder on GitHubat commit 5c5c3f0
Compare with similar skills
Post To Discussion 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 |
|---|---|---|---|---|---|---|
| Post To Discussion this skillhtlin222/meta-pipe | 139 | — | ~1.2k | Automated safety check: Pass | Custom licence | |
| GitHub Deep Researchbytedance/deer-flow | 84k | 4 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Last30daysmvanhorn/last30days-skill | 64k | — | ~7.9k | Automated safety check: Notes | MIT | |
| CCPM Project Managementautomazeio/ccpm | 8.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Read GitHubAgentTeam-TaichuAI/ScienceClaw | 671 | 2 repos | ~638 | Automated safety check: Pass | None | |
| Bump Aspire Versionmicrosoft/aspire | 6.4k | — | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
Last30days
mvanhorn/last30days-skill
Research what people actually say about any topic in the last 30 days.
CCPM Project Management
automazeio/ccpm
Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.
Read GitHub
AgentTeam-TaichuAI/ScienceClaw
Read and search GitHub repository documentation via gitmcp.io MCP service.
- Official
Bump Aspire Version
microsoft/aspire
Bumps the Aspire repository product version in eng/Versions.props using previous version-bump commits as guidance.
Ideer Daily Paper
AI45Lab/iDeer
Daily paper/repo digest where YOU are the reader. An agent skill from AI45Lab/iDeer.
More from htlin222/meta-pipe
All 15 skills in this repoMa Data Extraction
htlin222/meta-pipe
Define extraction schema, extract study data from full texts, and store it in a structured database for meta-analysis.
Ma End To End
htlin222/meta-pipe
End-to-end AI-assisted meta-analysis pipeline orchestration from TOPIC.txt to final manuscript and reviewer responses.
Ma Fulltext Management
htlin222/meta-pipe
Collect and manage full-text PDFs for included studies, track provenance, and prepare documents for extraction.
Ma Screening Quality
htlin222/meta-pipe
Perform title and abstract screening, apply inclusion and exclusion criteria, and assess study quality or risk of bias.
Ma Search Bibliography
htlin222/meta-pipe
Conduct literature searches for meta-analysis using Python with uv, query PubMed and other databases, deduplicate results, and store round-based bibliographies with notes.
Ma Manuscript Quarto
htlin222/meta-pipe
Draft and render a meta-analysis manuscript with Quarto using an IMRaD structure and embedded figures/tables.
Related
Works with
Categories
Questions about Post To Discussion
What does Post To Discussion do?
Share your completed meta-analysis project to the htlin222/meta-pipe GitHub Discussions board. Post To Discussion is an agent skill from htlin222/meta-pipe. Share your completed meta-analysis project to the htlin222/meta-pipe GitHub Discussions board.
When should I use Post To Discussion?
Post To Discussion fits situations like: A project reaches a milestone (analysis complete; manuscript drafted) and the user wants to showcase their work.
How do I install Post To Discussion in Claude Code?
Run `npx skills add htlin222/meta-pipe --skill post-to-discussion -a claude-code`. Or copy the skill folder (.claude/skills/post-to-discussion in htlin222/meta-pipe) into .claude/skills/post-to-discussion in your project. Claude Code loads it when a task matches its description.
How do I install Post To Discussion in Codex?
Run `npx skills add htlin222/meta-pipe --skill post-to-discussion -a codex`. Or copy the skill folder (.claude/skills/post-to-discussion in htlin222/meta-pipe) into .agents/skills/post-to-discussion in your project. Codex loads it when a task matches its description.
Can I use Post To Discussion 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 htlin222/meta-pipe --skill post-to-discussion -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/post-to-discussion, .gemini/skills/post-to-discussion, .github/skills/post-to-discussion and .opencode/skills/post-to-discussion in your project.
What does Post To Discussion need to run?
Going by SKILL.md and its folder, Post To Discussion needs the command-line tools its instructions call (git, gh and jq).
Does Post To Discussion access the network?
SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Post To Discussion 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 Post To Discussion use?
Post To Discussion has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Post To Discussion use?
About 1.2k tokens (SKILL.md is roughly 4.8k 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 Post To Discussion?
Skills that share tags, products or a category with Post To Discussion: GitHub Deep Research (bytedance/deer-flow, 84k stars), Last30days (mvanhorn/last30days-skill, 64k stars), CCPM Project Management (automazeio/ccpm, 8.4k stars) and Read GitHub (AgentTeam-TaichuAI/ScienceClaw, 671 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Post To Discussion?
htlin222 (a GitHub user) maintains it in htlin222/meta-pipe, which has 139 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on September 23, 2026.
Source: htlin222/meta-pipe on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.