By daymade
Co-creates a personal investment-research LLM Wiki (Karpathy pattern) by interviewing the user to extract their analysis framework into a structured markdown vault with wikilinks, no RAG or vector DB. Supports ingesting research reports, earnings calls, and expert notes into the wiki, plus post-earnings prediction-to-fulfillment reviews. Turns stock-picking, analyst-tracking, and earnings-watching workflows into a compounding knowledge base.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Professional Claude Code skills marketplace featuring production-ready skills for enhanced development workflows.
⭐ Start here if you want to create your own skills!
The skill-creator is the meta-skill that enables you to build, validate, and package your own Claude Code skills. It's the most important tool in this marketplace because it empowers you to extend Claude Code with your own specialized workflows.
This is a production-hardened fork of Anthropic's official skill-creator, born from building real skills and hitting every wall the official version doesn't warn you about.
The official skill-creator tells you what to build. Ours also tells you what not to try — and why.
| You're trying to... | Official | This Fork |
|---|---|---|
| Research before building | "Check available MCPs" (5 lines) | 8-channel search protocol with decision matrix: Adopt / Extend / Build |
| Create a skill interactively | Prose-based instructions | 9 structured AskUserQuestion checkpoints — user never loses context |
| Avoid common mistakes | No guidance | Cache edit warnings, prerequisite checks, security scan gate |
| Know the architecture options | Not mentioned | Inline vs Fork decision guide with examples (choosing wrong silently breaks your skill) |
| Validate before shipping | Basic YAML check | Expanded structural validator plus provenance-checked old-vs-new capability audit; packaging re-verifies the completed review instead of trusting a marker |
| Catch security issues | No tooling | security_scan.py with gitleaks integration — hard gate before packaging |
| Learn from real failures | No failure cases | Battle-tested methodology with documented failure patterns and gotchas |
| Distill past conversations safely | Not covered | Explicit local manifest, message-level time window, redaction, opaque source IDs, ignored .enrich/ staging, and manual promotion into references/scripts |
| Ground knowledge skills in evidence | General advice | Authority ladder from real calls and machine-readable specs through production code, plus executable-example smoke checks and evidence-boundary rules |
| Have both installed at once | Coin flip — the two descriptions are near-identical | Detects the clash on trigger and offers a one-command, reversible SessionStart routing hook (only ever installed when both coexist); the official plugin stays usable by explicit request |
| Your own skill collides with an installed plugin | Not covered | generate_supersede_kit.py stamps the same conditional routing kit into your skill, plus a measured precedence decision guide (rename → description tiebreaker → hook → disable) |
Quality comparison (independent audit, 8 dimensions):
| Dimension | Official | This Fork |
|---|---|---|
| Actionability | 7 | 9 |
| Error Prevention | 5 | 9 |
| Prior Art Research | 4 | 9 |
| Counter Review Process | 4 | 8 |
| Real-World Lessons | 3 | 8 |
| User Experience | 4 | 9 |
| Total (out of 80) | 42 | 65 |
Full methodology: skill-creator/references/skill-development-methodology.md
In Claude Code (in-app):
/plugin marketplace add daymade/claude-code-skills
Then:
npx claudepluginhub p/daymade-llm-wiki-setup-llm-wiki-setupScan and remove sensitive data (secrets, API keys, private domains/IPs, PII) from GitHub repository history. Use this skill whenever the user says scan sensitive data, clean git history, remove secrets from repo, sanitize GitHub history, 清理敏感数据, 历史重写, force push, 泄露, or needs to repair a public repo after accidental secret/private context leakage. Also use before any force push to a public repository to verify visibility, backup, and scan results.
Compare two videos and generate interactive HTML reports with quality metrics (PSNR, SSIM) and frame-by-frame visual comparisons. Use when analyzing compression results, evaluating codec performance, or assessing video quality differences
Generate format-controlled research reports with evidence tracking, source governance, and multi-pass synthesis. V6.1 adds: source accessibility (circular verification forbidden, exclusive advantage encouraged). Enterprise Research Mode: six-dimension data collection, SWOT/barrier/risk frameworks, and three-level quality control for company research
Investigate and resolve Cloudflare configuration issues using API-driven evidence gathering. Use when troubleshooting ERR_TOO_MANY_REDIRECTS, SSL errors, DNS issues, or any Cloudflare-related problems
Reviews rendered frontends, enterprise dashboards, HTML slides, design-system specimens/live artifacts, map/GIS canvases, generated UIs, and browser-integrated export/share/download/print/PDF flows for visual and UX defects that lint/build miss: awkward line breaks, overflow, wrong state, route drift, unusable drawers/maps/tables, unreadable standalone artifacts, blank print previews, generic AI slop, and Chrome/Computer Use verification gaps. Use after frontend-design or ui-designer work and alongside qa-expert release gates.
Build and maintain an LLM-curated personal knowledge base in your project — Andrej Karpathy's LLM Wiki pattern, designed to scale to thousands of pages without becoming a context bottleneck. Now with an optional compiled graph layer for typed, provenance-backed relationships.
A collection of Claude Code skills for knowledge management, wiki building, and more.
LLM-maintained knowledge base skill — structured wiki with Obsidian, milestone-based source clustering, proactive write-back, and autonomous lint
Personal LLM-managed wiki: ingest sources, cross-reference pages, query with citations, and lint your markdown knowledge base
Auto-maintained LLM wiki based on Andrej Karpathy's pattern.
Research skills for an Obsidian vault — build, query, lint, distill, and render a persistent LLM-maintained research wiki over your vault, Readwise, NotebookLM, GitHub repos, and the web. Bundles the source CLIs' usage skills.