Open Agent Skills · install in any compatible agent

Give your Agenta method.

Thirteen open-source skills turn experienced ways of researching, deciding, publishing, and maintaining systems into executable workflows: explicit steps, inspectable checkpoints, and defined outputs. Claude Code works; so does any client that supports the Agent Skills specification.

  • 13curated skills, each with a job
  • 91routing test cases
  • Spec ↗open Agent Skills standard
  • Access ↗capability list for every skill

Bring a real task.
Get a reviewable artifact.

Every flagship makes the path between request and result visible: what it reads, when it asks, what it checks, and where it stops.

01

Research

Deep Research

Scope the question, gather multiple sources, maintain a registry, check citations, and deliver a report with conclusions, trade-offs, and explicit limitations.

Use deep-research to compare three RAG architectures for our support team
Input

A decision, scope, constraints

Output

Cited memo or full report

Inspect skill ↗
02

Decision interview

Product Manager

grill-me-to-doc reads available evidence first, asks one decision per turn, explains its recommendation, resumes from saved state, and delivers PRODUCT-DOC before a hard approval stop.

Use product-manager in grill-me-to-doc mode for an AI hiring product
Input

An idea that needs hard decisions

Output

PRODUCT-DOC and decision log

Inspect skill ↗
03

Presentation

Deck Studio

Confirm the story before polishing slides, then move through page briefs, registered layouts, visual drafts, and explicit visual QA.

Use deck-studio to turn this quarterly review into a consulting deck
Input

Source material, audience, goal

Output

Deck content and visual delivery

Inspect skill ↗
04

Content pipeline

WeChat Article Writer

Run article, image-prompts, layout, or full-pipeline to produce an article, provider-neutral image manifest, and WeChat-safe inline HTML. Prompts are not generated images, and nothing is auto-published.

Use wechat-article-writer full-pipeline for these notes
Input

Notes, outline, or source material

Output

Article, prompt manifest, HTML

Inspect skill ↗

Install one.
Use it on real work.

Do not load all 13 by default. Pick one workflow you will use this week; the installer copies only that skill to the cross-client .agents/skills directory.

Read the install guide ↗
Terminal
git clone --depth 1 https://github.com/staruhub/ClaudeSkills.git
cd ClaudeSkills
python3 scripts/install_skill.py deep-research

Installed at ~/.agents/skills/deep-research

First run Use deep-research to compare three options and write a cited decision memo

Choose another workflow: replace deep-research with product-manager, deck-studio, or wechat-article-writer.

Project-only install: add --project. List every short name with python3 scripts/install_skill.py --list.

Claude Code native path: add --client claude-code. Invocation and discovery behavior otherwise depend on the host agent.

Inspect the work before you install.

Real repository artifacts make the promise concrete. Verification stays labeled by what it actually proves.

06

PRODUCT-DOC contract ↗

A real Product Manager deliverable that preserves decisions, open questions, and the approval boundary.

Structural gate ↗

Checked Directory and structure contracts for 13 curated skills.

Limit Not live business-task E2E for all 13.

Routing definitions ↗

Checked 91 schema and conflict cases across 10 skills.

Limit Not model-executed routing accuracy.

Deck artifacts ↗

Checked Generators, rendered pages, rubrics, scores, and known defects.

Limit Not independent external certification.

Capability matrix ↗

Checked Per-skill reads, writes, network, shell, credentials, and deletion.

Limit Not a substitute for your own policy review.

Reproduce the repository gates
python3 scripts/validate.py && python3 scripts/run_routing_evals.py && python3 scripts/validate_site.py

Thirteen skills.
Pick what earns a slot.

Four flagships plus focused workflows for coding, security, architecture, Three.js, PDF, sales, and AI-native product methods. Experimental work stays in the separate lab.

Inspect before installing

Know what a skill can do.

Skills can read files and run scripts. The security guide separates bundled script behavior from permissions the host agent may request, with a capability matrix for every curated skill.

  • deep-researchREAD · WRITE · NET · SHELL
  • security-auditREAD · WRITE · SHELL
  • c-drive-cleanerREAD · DELETE*

* Deletion is guarded: every destructive action requires explicit confirmation.

Before you install

How is this different from a prompt collection?

A prompt disappears into a conversation. Each curated skill is a versioned folder with a SKILL.md and, when needed, references, scripts, assets, schemas, and negative cases.

Do passing contract tests equal production performance?

No. The four flagships have deterministic contract tests, and Deck also uses real Chrome rendering plus PPTX assembly. Subjective future-model quality, live image providers, and WeChat publishing still require separate verification.

Why was the skill not discovered?

Confirm that the client scans .agents/skills, or use its native directory. The installer also strips the repository prefix so Geek-skills-deck-studio becomes the stable identity deck-studio.

How do I contribute?

Start with an issue. New skills incubate in lab/ and graduate after they meet the repository's quality gates and capability disclosure rules.

Build in public

Found a bug—or built something useful?

Open an issue with a redacted input, output, and reproduction steps. New skills start in lab/ and graduate after meeting the repository gates.