awesome-repo-builder
Create a topic-specific GitHub awesome-list repository scaffold with a polished README, concise contribution rules, AI-agent instructions, URL verification, license, and reusable templates. Use when the user wants to generate a new awesome repo, awesome list, curated repository, or topic resource catalog from a topic plus optional taxonomy, inclusion criteria, and researched entries.
What this skill does
# Awesome Repo Builder
Build a new awesome-list repository with a polished `README.md`, concise contribution rules, AI-agent instructions, URL verification script, license, `.gitignore`, and optional reusable templates.
## Required Inputs
Ask only for missing essentials.
- Topic: required. Example: "future event prediction", "AI coding harnesses", "LLM time-series forecasting".
- Taxonomy: recommended. If absent, propose one before generating.
- Inclusion criteria: recommended. If absent, draft concise criteria and exclusions.
- Initial entries: optional. The user may provide an already researched awesome list; otherwise research enough seed entries before generating.
- Output directory: optional. If absent, create a local folder named from the repo slug.
## Workflow
1. Inspect the user's requested topic and decide whether enough taxonomy and criteria exist.
2. If initial entries are absent, research the topic first. Prefer official project pages, papers, docs, GitHub repositories, and existing awesome lists. Keep the first generated repo useful but not exhaustive.
3. Create a JSON spec with `title`, `slug`, `topic`, `tagline`, `description`, `taxonomy`, `criteria`, `initial_entries`, and `related_lists`.
4. Run `scripts/create_awesome_repo.py` with the spec and output directory.
5. Read the generated files and make small manual edits if the topic requires wording changes.
6. Report the output path and any assumptions, especially taxonomy or criteria that were inferred.
## Scaffold Command
Use the bundled script from the skill directory:
```bash
python scripts/create_awesome_repo.py --spec /path/to/spec.json --output /path/to/awesome-topic
```
If the current project uses a Python virtual environment, activate it first. The script only uses the Python standard library.
## Spec Format
Minimum:
```json
{
"title": "Awesome Future Event Prediction",
"slug": "awesome-future-event-prediction",
"topic": "future event prediction",
"tagline": "Curated resources for future event prediction.",
"description": "A curated list of papers, benchmarks, tools, and systems for forecasting discrete future events.",
"taxonomy": [
{
"name": "Foundations",
"description": "Conceptual and survey resources.",
"entries": [
{
"title": "A Survey on Event Prediction Methods from a Systems Perspective",
"url": "https://arxiv.org/abs/2302.04018",
"note": "A systems view of event prediction that helps define scope and common failure modes."
}
]
}
],
"criteria": {
"belongs": [
"Addresses prediction of discrete future events.",
"Provides a reusable method, benchmark, dataset, tool, or system insight."
],
"excludes": [
"General AI papers without an event-forecasting angle.",
"Pure time-series forecasting resources with no event-level relevance."
]
},
"related_lists": []
}
```
Notes:
- `taxonomy[].entries` may be empty; the script will create a placeholder.
- `taxonomy[].subsections` is supported for nested sections.
- `initial_entries` is also supported as a mapping from section name to entries when entries are collected separately.
- Entry format uses title, URL, and a short note explaining why the resource is worth including.
## Generated Structure
The script creates:
```text
awesome-topic/
├── .gitignore
├── AGENTS.md
├── CONTRIBUTING.md
├── LICENSE
├── README.md
├── verify_urls.py
└── templates/
├── AGENTS.md
├── CHECKLIST.md
├── IMPLEMENT.md
└── PLAN.md
```
Keep the generated repository focused on initial structure and seed content. Do not add PR automation, batch review workflows, entry sorting policy, scheduled cleanup, or long maintenance process unless the user explicitly asks for it.
## Reference
Read `references/awesome-repo-structure.md` when you need the detailed structural pattern for generated repositories.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.