Agent skill

Open Source Project Article

Analyze an open-source project from a repository URL and write a deeply sourced Chinese Markdown article.

GPL-2.0Auto-check passedDevelopment

Install Open Source Project Article

skills CLI

$ npx skills add digoal/blog --skill open-source-project-article -a claude-code

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

GitHub CLI

$ gh skill install digoal/blog open-source-project-article --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/digoal/blog.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/open-source-project-article .claude/skills/open-source-project-article && 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/

Paste into Claude Code

Install the "open-source-project-article" agent skill from https://github.com/digoal/blog/tree/master/skills/open-source-project-article into .claude/skills/open-source-project-article/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "open-source-project-article", 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

$skill-installer install https://github.com/digoal/blog/tree/master/skills/open-source-project-article

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

skills CLI

$ npx skills add digoal/blog --skill open-source-project-article -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install digoal/blog open-source-project-article --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/digoal/blog.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/open-source-project-article .agents/skills/open-source-project-article && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "open-source-project-article" agent skill from https://github.com/digoal/blog/tree/master/skills/open-source-project-article into .agents/skills/open-source-project-article/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "open-source-project-article", 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.

skills CLI

$ npx skills add digoal/blog --skill open-source-project-article -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install digoal/blog open-source-project-article --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/digoal/blog.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/open-source-project-article .cursor/skills/open-source-project-article && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "open-source-project-article" agent skill from https://github.com/digoal/blog/tree/master/skills/open-source-project-article into .cursor/skills/open-source-project-article/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "open-source-project-article", 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

$ gemini skills install https://github.com/digoal/blog.git --path skills/open-source-project-article

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add digoal/blog --skill open-source-project-article -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install digoal/blog open-source-project-article --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/digoal/blog.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/open-source-project-article .gemini/skills/open-source-project-article && rm -rf skills-src

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

Paste into Gemini CLI

Install the "open-source-project-article" agent skill from https://github.com/digoal/blog/tree/master/skills/open-source-project-article into .gemini/skills/open-source-project-article/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "open-source-project-article", 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.

GitHub CLI

$ gh skill install digoal/blog open-source-project-article

Installs 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).

skills CLI

$ npx skills add digoal/blog --skill open-source-project-article -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/digoal/blog.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/open-source-project-article .github/skills/open-source-project-article && rm -rf skills-src

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

Paste into GitHub Copilot

Install the "open-source-project-article" agent skill from https://github.com/digoal/blog/tree/master/skills/open-source-project-article into .github/skills/open-source-project-article/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "open-source-project-article", 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.

skills CLI

$ npx skills add digoal/blog --skill open-source-project-article -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install digoal/blog open-source-project-article --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/digoal/blog.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/open-source-project-article .opencode/skills/open-source-project-article && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "open-source-project-article" agent skill from https://github.com/digoal/blog/tree/master/skills/open-source-project-article into .opencode/skills/open-source-project-article/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "open-source-project-article", 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: open-source-project-article
GitHub stars: 8.6k
Token cost: ~1.3k tokens
SKILL.md length: 574 words
Files: 4 (incl. references)
Skills in repo: 98
Repo updated: Sep 28, 2026
First seen: Oct 7, 2026
Licence: GPL-2.0

At a glance

Analyze an open-source project from a repository URL and write a deeply sourced Chinese Markdown article.

Works in 5 steps: Fetch and read the project README.md or… → Use DeepWiki MCP to analyze the… → Identify and ask necessary clarification… → …
The user asks to research a GitHub/open-source project
SKILL.md covers Non-Negotiable Source Order, Inputs, Evidence Workflow and Article Requirements, plus 2 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Open Source Project Article is an agent skill from digoal/blog. Analyze an open-source project from a repository URL and write a deeply sourced Chinese Markdown article. Use when the user asks to research a GitHub/open-source project, read its README, use DeepWiki MCP for architecture analysis, search related articles, compare competitors, validate claims, and save the final article under the current project's markdown directory.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `agents/openai.yaml`, `references/article-structure.md` and `references/validation-checklist.md`).

It sits in Development, covering Technical documentation and Markdown. It works with Model Context Protocol and GitHub. The repository describes itself as: AI,Opensource,Database,Business,Finance,Minds. git clone --depth 1 https://github.com/digoal/blog. The licence is GPL-2.0.

When your agent uses it

The user asks to research a GitHub/open-source project
Read its README
Use DeepWiki MCP for architecture analysis
Search related articles

Example prompts

“/open-source-project-article”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

Fetch and read the project README.md or readme.md.
Use DeepWiki MCP to analyze the repository architecture.
Identify and ask necessary clarification questions, only when they materially affect article direction, audience, or output location. If…
Search the web for related articles, docs, benchmarks, releases, comparisons, and case studies.
Only then draft the article.

What it can do on your machine

Read from SKILL.md and the folder at commit 69fb793. 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

Open Source Project Article loads about 1.3k tokens when it runs, and up to ~3.1k if it reads all its reference files. Until then it costs about 99 tokens; SKILL.md has 574 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~99
When it runs · the whole SKILL.md, loaded when a task matches: ~1.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~3.1k

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 digoal/blog at commit 69fb793, republished under its GPL-2.0 licence (© digoal). 574 words, ~1,253 tokens.

Download SKILL.mdSave it as .claude/skills/open-source-project-article/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.

name: open-source-project-article
description: Analyze an open-source project from a repository URL and write a deeply sourced Chinese Markdown article. Use when the user asks to research a GitHub/open-source project, read its README, use DeepWiki MCP for architecture analysis, search related articles, compare competitors, validate claims, and save the final article under the current project's markdown directory.

Open Source Project Article

Use this skill to turn an open-source project URL into an evidence-grounded, article-ready Chinese Markdown file.

Non-Negotiable Source Order

Always gather evidence in this exact order:

Fetch and read the project README.md or readme.md.
Use DeepWiki MCP to analyze the repository architecture.
Identify and ask necessary clarification questions, only when they materially affect article direction, audience, or output location. If not blocked, state assumptions and continue.
Search the web for related articles, docs, benchmarks, releases, comparisons, and case studies.
Only then draft the article.

Do not start with web search. Do not write from memory. Do not skip DeepWiki when the repository is supported by DeepWiki MCP.

Inputs

Require a repository URL or owner/repo. If the user omits it, ask for it.

Infer defaults unless risky:

Article language: Chinese.
Output location: markdown/ under the current project directory.
File name: repository name normalized to lowercase hyphen-case, e.g. pg-wait-tracer.md.
Article audience: DBA, architect, developer, technical decision maker.

Create markdown/ if missing.

Evidence Workflow

Normalize the repository:
- Convert GitHub URL to owner/repo.
- Preserve the original URL for citations.
Fetch README:
- Prefer repository files or GitHub raw content.
- Read README.md; if absent, try readme.md.
- If README cannot be fetched, stop and report what was attempted.
Ask DeepWiki:
- Use mcp__deepwiki__read_wiki_structure first when available.
- Use mcp__deepwiki__ask_question for architecture, core modules, data flow, extension points, tradeoffs, tests, and limitations.
- Treat DeepWiki as architecture evidence, not as a substitute for README or code.
Ask necessary questions:
- Ask only if the answer changes the article materially, such as target audience, article style, competitor set, or whether to emphasize hands-on deployment vs strategic evaluation.
- In default mode, avoid blocking on preferences; state reasonable assumptions and proceed.
Search web:
- Use primary sources first: official docs, repository docs, release notes, papers, benchmark reports, vendor docs.
- Use secondary articles only to understand ecosystem interpretation or adoption cases.
- For current project status, releases, stars, or ecosystem facts, verify live.
Build an evidence pack:
- README facts.
- DeepWiki architecture findings.
- Official or primary-source facts.
- Benchmarks/data/cases with source links.
- Competitor facts with source links.
- Uncertainties and assumptions.

Show full SKILL.md (219 more words)Show less

Article Requirements

Read references/article-structure.md before drafting. Use it as the mandatory content checklist.

The article must include:

Clear thesis, not neutral feature listing.
Preconditions for the thesis to hold.
Alternative thesis or recommendation when those preconditions collapse.
Authoritative data or cases supporting the assumptions.
Authoritative data or cases supporting the thesis.
Background.
Scenario introduction.
Pain point analysis.
Sharp critique of traditional solutions.
Product solution.
Product principles and architecture.
Before/after effect comparison.
Competitor comparison.
Usage scenarios.
Best practices.
Hands-on steps.
Risks, limitations, and failure conditions.

For every major thesis, include this logic explicitly:

text

观点：...
成立前提：...
支撑证据：...
如果前提崩塌：应转向的其他观点/方案是...

Insert Mermaid or SVG diagrams at every core argument section. Prefer Mermaid unless SVG is clearly better. Diagrams must explain, not decorate.

Validation

Read references/validation-checklist.md before finalizing.

Validate:

Source order was followed.
Claims map to sources or are clearly marked as inference.
Data, cases, and benchmarks are quoted with context and limitations.
Competitor comparison is fair and sourced.
The article states what alternative viewpoint or product recommendation follows if core assumptions fail.
Hands-on commands match README/docs.
Mermaid syntax is plausible.
Output path is markdown/<slug>.md.

If validation finds weak evidence, revise the article before saving. If evidence remains unavailable, state the gap inside the article instead of inventing support.

Output

Save the article to:

text

<current-project>/markdown/<repo-slug>.md

After saving, report:

File path.
Evidence sources used.
Any unresolved evidence gaps.
Validation summary.

Files

SKILL.md and 3 other files (references) in skills/open-source-project-article of digoal/blog.

SKILL.md
agents/openai.yaml
references/article-structure.md
references/validation-checklist.md

Open the folder on GitHubat commit 69fb793

Compare with similar skills

Open Source Project Article 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.

Open Source Project Article compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Open Source Project Article this skilldigoal/blog	8.6k	—	~1.3k	Automated safety check: Pass	GPL-2.0	9 days ago
Markdown Without Hard Wrapsprisma/orm	48k	—	~472	Automated safety check: Pass	Apache-2.0	today
Library Documentation Seekerwithkynam/vibecode-pro-max-kit	1.1k	2 repos	~1k	Automated safety check: Notes	MIT	3 mo ago
Update .NET Supported OS Matrixdotnet/core	22k	—	~4.1k	Automated safety check: Pass	MIT	yesterday
README Badges and Headersjal-co/shieldcn	916	—	~4.3k	Automated safety check: Pass	MIT	yesterday
Githits MCPgithits-com/githits-cli	114	—	~2k	Automated safety check: Pass	Apache-2.0	yesterday

Similar skills

Markdown Without Hard Wraps
prisma/orm
Official
Keeps Markdown prose on one line per paragraph instead of wrapping at a fixed column, so renderers can reflow it and diffs stay clean.
48k GitHub stars~472 tokensUpdated today
DevelopmentAuto-check passed
Library Documentation Seeker
withkynam/vibecode-pro-max-kit
Looks up library and framework documentation through Context7 first, with bundled Node scripts as a fallback that fetch and analyze llms.txt files.
1.1k GitHub starsUsed in 2 repos~1k tokens
DevelopmentAuto-check: notes
Update .NET Supported OS Matrix
dotnet/core
Official
Audits and updates the supported-os.json files for .NET releases, checking them against upstream lifecycle data and regenerating the markdown with the release-notes tool.
22k GitHub stars~4.1k tokensUpdated yesterday
DevelopmentAuto-check passed
README Badges and Headers
jal-co/shieldcn
Adds shadcn/ui-styled README badges, badge groups, download charts, header banners and sponsor or contributor grids using the shieldcn service.
916 GitHub stars~4.3k tokensUpdated yesterday
DevelopmentAuto-check passed
Githits MCP
githits-com/githits-cli
Route public OSS code, documentation, examples, and package questions to GitHits tools.
114 GitHub stars~2k tokensUpdated yesterday
DevelopmentAuto-check passed
Firecrawl Developer Index
firecrawl/skills
Search an index of public repositories, GitHub issues, merged pull requests, repository READMEs, and curated documentation sites.
115 GitHub stars~2k tokensUpdated today
DevelopmentAuto-check passed

More from digoal/blog

All 98 skills in this repo

Article Fact Checker
digoal/blog
三层审查模型,逐段逐句验证文章真伪、证据链与逻辑结构。Use when the user asks to fact-check, verify, audit, or evaluate the credibility of an article, essay, report, opinion piece, social-media post, or any written claim —…
8.6k GitHub stars~939 tokensUpdated 9 days ago
Auto-check passed
Find Postgres Bug
digoal/blog
Find latent bugs in a local PostgreSQL source tree (RELxxSTABLE branch or HEAD) the way a core hacker does: build a heavily-poisoned debug instance (cassert + cache-discard + -O0/-ggdb3 + core…
8.6k GitHub stars~4k tokensUpdated 9 days ago
Auto-check passed
Digoal
digoal/blog
Portable digital employee distilled from digoal's personal blog for PostgreSQL, PolarDB, DuckDB, AI+database, vector/RAG, database operations, source-code reading, technical content creation…
8.6k GitHub stars~2.2k tokensUpdated 9 days ago
Auto-check passed
Paper Interpretation
digoal/blog
从论文 PDF 文件或论文 PDF URL 生成通俗易懂、图文并茂、带批判性评估的中文 Markdown 解读，并保存到当前项目的 markdown 目录。Use when the user asks to interpret,精读,解读,summarize,explain,analyze, or write an article from an academic paper PDF…
8.6k GitHub stars~1.5k tokensUpdated 9 days ago
Auto-check passed
Product Multi Role Analysis
digoal/blog
Analyze a product from documentation, websites, PDFs, articles, release notes, pricing pages, app listings, reviews, filings, or related links; save separate intermediate analyses from seven roles…
8.6k GitHub stars~1.8k tokensUpdated 9 days ago
Auto-check passed
Blog Cover Poster
digoal/blog
Turn a blog post, article, notes, or any source material into a set of vertical poster images — one cover plus several coherent content slides that explain the core points.
8.6k GitHub stars~1.4k tokensUpdated 9 days ago
Auto-check passed

Works with

Questions about Open Source Project Article

What does Open Source Project Article do?

Analyze an open-source project from a repository URL and write a deeply sourced Chinese Markdown article. Open Source Project Article is an agent skill from digoal/blog. Analyze an open-source project from a repository URL and write a deeply sourced Chinese Markdown article.

When should I use Open Source Project Article?

Open Source Project Article fits situations like: the user asks to research a GitHub/open-source project; read its README; use DeepWiki MCP for architecture analysis; search related articles.

How do I install Open Source Project Article in Claude Code?

Run `npx skills add digoal/blog --skill open-source-project-article -a claude-code`. Or copy the skill folder (skills/open-source-project-article in digoal/blog) into .claude/skills/open-source-project-article in your project. Claude Code loads it when a task matches its description.

How do I install Open Source Project Article in Codex?

Run `npx skills add digoal/blog --skill open-source-project-article -a codex`. Or copy the skill folder (skills/open-source-project-article in digoal/blog) into .agents/skills/open-source-project-article in your project. Codex loads it when a task matches its description.

Can I use Open Source Project Article 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 digoal/blog --skill open-source-project-article -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/open-source-project-article, .gemini/skills/open-source-project-article, .github/skills/open-source-project-article and .opencode/skills/open-source-project-article in your project.

What does Open Source Project Article need to run?

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

Does Open Source Project Article 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 Open Source Project Article 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 Open Source Project Article use?

Open Source Project Article is published under the GPL-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Open Source Project Article use?

About 1.3k tokens (SKILL.md is roughly 5k 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 1.9k tokens, read only when the agent opens those files.

What are the alternatives to Open Source Project Article?

Skills that share tags, products or a category with Open Source Project Article: Markdown Without Hard Wraps (prisma/orm, 48k stars), Library Documentation Seeker (withkynam/vibecode-pro-max-kit, 1.1k stars), Update .NET Supported OS Matrix (dotnet/core, 22k stars) and README Badges and Headers (jal-co/shieldcn, 916 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Open Source Project Article?

digoal (a GitHub user) maintains it in digoal/blog, which has 8,587 GitHub stars. The repository holds 98 skills in this directory. The repository was last updated on September 28, 2026.

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

Install Open Source Project Article

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Open Source Project Article

Non-Negotiable Source Order

Inputs

Evidence Workflow

Article Requirements

Validation

Output

Files

Compare with similar skills

Similar skills

More from digoal/blog

Related

Questions about Open Source Project Article