Verified repository guide · 2026 edition

10 GitHub repos that turn Claude into a productivity beast.

The original graphic is useful, but it mixes complete AI platforms, coding configurations and reusable skill packs. This guide separates them clearly, explains what each repository actually does, and shows where each one fits.

Important distinction: these are not ten interchangeable “Claude plugins.” Some package code for an LLM, some are full self-hosted AI platforms, and others teach Claude repeatable workflows through Agent Skills.
Repository directory

What each project does

Search by name or filter by role. Every card includes the real use case, expected impact and the person it best serves.

01
Code context

Repomix

yamadashy/repomix

Packages an entire local or remote repository into one AI-friendly document so Claude can reason about the project as a whole instead of seeing isolated files.

How it worksScans a repo, respects ignore rules, estimates tokens and exports XML, Markdown, JSON or plain text.
Why it mattersExcellent for architecture reviews, migrations, onboarding, refactors and “understand this codebase” prompts.
Watch outReview the output for secrets and avoid sending sensitive proprietary code to an unapproved model.
Best for: full-codebase contextOpen GitHub ↗
02
Claude Code

Everything Claude Code

affaan-m/ECC

A broad Claude Code configuration framework containing specialized agents, skills, commands, hooks and opinionated workflow patterns.

How it worksInstalled as a Claude Code plugin or copied selectively into your own project and user-level configuration.
Why it mattersTurns a blank Claude Code setup into a structured operating environment for planning, testing, reviewing and shipping software.
Watch outDo not install everything blindly; adopt only the rules and automations that match your stack.
Best for: power usersOpen GitHub ↗
03
AI app builder

Dify

langgenius/dify

A production-oriented platform for building LLM applications, agents and RAG workflows through a visual canvas, APIs and an operations layer.

How it worksConnects to many model providers, knowledge bases, tools and workflow nodes, then exposes finished apps through a UI or API.
Why it mattersUseful when a prototype must become a managed product with prompts, datasets, logs, evaluation and deployment controls.
Watch outIt is a full platform, not a small Claude add-on; self-hosting introduces infrastructure and security responsibilities.
Best for: production AI applicationsOpen GitHub ↗
04
Visual workflows

Flowise

FlowiseAI/Flowise

A visual, node-based environment for assembling AI agents, RAG pipelines and multi-step flows with less custom glue code.

How it worksDrag nodes onto a canvas, connect models, prompts, memory, vector stores, tools and APIs, then expose the flow as an endpoint.
Why it mattersGreat for quickly validating an agent architecture before committing to a fully coded implementation.
Watch outVisual simplicity can hide operational complexity; test authentication, tool permissions and input validation carefully.
Best for: fast prototypesOpen GitHub ↗
05
Private knowledge

Onyx

onyx-dot-app/onyx

A self-hostable AI workspace for chat, enterprise search, RAG, agents and actions connected to internal company knowledge.

How it worksIndexes connected sources such as workplace documents and apps while preserving a centralized conversational interface.
Why it mattersDesigned for organizations that want an internal AI assistant grounded in their own information and deployable in controlled environments.
Watch outPermission syncing, connector scope and data retention need enterprise-grade governance.
Best for: company knowledge AIOpen GitHub ↗
06
Official skills

Claude Skills by Anthropic

anthropics/skills

Anthropic’s public collection of Agent Skills: folders containing instructions, scripts and resources that Claude loads for specialized, repeatable tasks.

How it worksEach skill describes when it should trigger and gives Claude a structured workflow, supporting material and optional executable helpers.
Why it mattersProvides both practical examples and the clearest reference architecture for building your own reliable skills.
Watch outSkills can contain scripts; inspect every file and understand what permissions the agent will receive.
Best for: learning the skill standardOpen GitHub ↗
07
Skill discovery

Awesome Claude Skills

ComposioHQ/awesome-claude-skills

A curated directory of community-created Claude skills and examples across development, content, research, automation and business workflows.

How it worksActs as a discovery index rather than one monolithic plugin; you browse the list and install or adapt individual skills.
Why it mattersSaves time when exploring what the community has already built and reveals useful patterns for your own skill library.
Watch out“Curated” does not mean audited. Check maintainers, code, license, recent activity and requested permissions.
Best for: finding skillsOpen GitHub ↗
08
Obsidian

Obsidian Skills

kepano/obsidian-skills

Agent skills that teach Claude how to work effectively with Obsidian vaults, including Markdown, Bases, JSON Canvas and command-line workflows.

How it worksProvides conventions and task procedures so an agent can create, reorganize and connect notes without destroying vault structure.
Why it mattersBridges a personal knowledge system and an AI agent, enabling repeatable research, synthesis and content workflows.
Watch outUse version control or backups before allowing bulk edits across a valuable vault.
Best for: Obsidian usersOpen GitHub ↗
09
Research

NotebookLM Skill

PleasePrompto/notebooklm-skill

Connects Claude Code with Google NotebookLM so the agent can query notebooks and return answers grounded in the documents loaded there.

How it worksUses a browser-assisted integration and persistent session state to interact with NotebookLM libraries and notebooks.
Why it mattersCombines Claude’s workflow automation with NotebookLM’s source-grounded research behavior and citations.
Watch outBrowser automation and stored authentication are sensitive; isolate credentials and review the implementation before use.
Best for: document-grounded researchOpen GitHub ↗
10
Marketing

Marketing Skills

coreyhaines31/marketingskills

A focused collection of marketing skills for Claude Code and other compatible agents, covering CRO, copywriting, SEO, analytics and growth engineering.

How it worksEncodes repeatable marketing frameworks and task-specific instructions into installable skill folders.
Why it mattersReduces generic output by giving the agent a structured process for audits, campaigns, positioning and conversion work.
Watch outFrameworks improve consistency but do not replace first-party customer data, legal review or human brand judgment.
Best for: growth and marketing teamsOpen GitHub ↗
Decision matrix

Choose by outcome

The best repository is determined by your intended outcome—not by the biggest star count or longest feature list.

RepositoryPrimary jobSetup effortTechnical levelSelf-hostableBest first use
RepomixPackage code contextLowIntermediateLocal CLIExplain or audit a repository
Everything Claude CodeUpgrade coding workflowsMediumAdvancedLocal configAdd agents, skills and hooks
DifyBuild production AI appsHighIntermediate–advancedYesShip a managed RAG app
FlowisePrototype visual AI flowsMediumBeginner–intermediateYesValidate an agent flow
OnyxCompany knowledge assistantHighAdvancedYesSearch internal documents
Anthropic SkillsLearn/use official skillsLowBeginner–intermediateLocal filesStudy reliable skill design
Awesome Claude SkillsDiscover community skillsLowBeginnerN/A directoryBrowse possible capabilities
Obsidian SkillsOperate an Obsidian vaultLow–mediumIntermediateLocal filesOrganize a knowledge base
NotebookLM SkillGrounded notebook researchMediumIntermediateLocal integrationQuery document collections
Marketing SkillsStructured growth workflowsLowBeginner–intermediateLocal filesRun a marketing audit
Recommended stack

A sensible way to combine them

Installing all ten is unnecessary. A focused stack gives more value with less maintenance and risk.

STEP 01

Start with context

Use Repomix when Claude needs a coherent view of an existing codebase. Add Anthropic’s official skills to understand the skill format.

STEP 02

Add specialization

Choose only the skill packs relevant to your work: Obsidian, NotebookLM or Marketing Skills. Use a curated list for discovery, not blind installation.

STEP 03

Build a platform only when needed

Select Flowise for fast visual prototyping, Dify for application operations, or Onyx for a private organization-wide knowledge assistant.

# A lightweight developer starting point
npm install -g repomix
repomix . --style markdown

# Then review official skill examples
# https://github.com/anthropics/skills

# Add a specialized skill only after inspecting its files
# and testing it in a disposable project.
Treat every repository and skill as executable third-party software.

Verify the owner and exact URL, inspect scripts and hooks, check recent commits and security advisories, pin versions for production, use least-privilege credentials, keep secrets outside prompts and test new agent capabilities in a sandbox before granting access to production data or systems.