⏳ This skill is pending AI review.
Scores will appear once the review pipeline completes.
featspiration
Review outside codebases, libraries, docs, papers, competitors or a list of ideas against the project you are working in, and produce one designed HTML findings page - a short bullet read for the human, a build order, and one self-contained, copy-ready implementation prompt per feature. Use this whenever the user asks what their project can take, borrow, port or learn from another repo or source; asks to mine or audit a codebase for features worth having; wants a feature plan or roadmap split into prompts they can hand to a coding agent one session at a time; or says "feature findings", "findings page", "findings artifact" or "feature prompts". Use it even when they only say "check this project and tell me what is useful for mine".
Choose how to use this skill
You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.
1. Native installer
This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.
Do not guess an installer command or replace an existing version without reviewing the diff.
2. Complete package recommended
Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.
No complete ProSkills package is published for this listing yet.3. Prompt-only
Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.
Need only the instruction file?
Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.
No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.
// RATINGS
Not yet listed on ClawHub or SkillsMP
// README
featspiration
An agent skill that answers "here is another project, what can mine take from it?" with one page you can build from for weeks.
Point your coding agent at an outside codebase, library, paper or list of ideas. It reads the source and your project, checks what it is about to recommend, and produces a designed HTML page with:
- A short read for you: a verdict on each source, the few things to know before building, what is broken in the source, and what to skip.
- A build order: features in dependency order, sized in agent sessions.
- One prompt per feature: self-contained and copy-ready. Paste it into a fresh session and that session can build the feature without any of the original conversation.
It is made for people who build one feature per session because their sessions are time- or usage-limited.
Open examples/fieldnote.html in a browser to see a page (a made-up project, built from example.findings.json).
Install
With the skills CLI, which installs into Claude Code, Cursor, Antigravity, Codex, Gemini CLI and many other agents:
npx skills add KareemmSayed/featspiration
Pick agents explicitly, or install for your user account instead of the current project:
npx skills add KareemmSayed/featspiration -a claude-code -a cursor -a antigravity
npx skills add KareemmSayed/featspiration -g
Claude Code plugin. Add the repo as a marketplace, then install:
/plugin marketplace add KareemmSayed/featspiration
/plugin install featspiration@featspiration
By hand. Copy the skills/featspiration folder into your tool's skills directory. For Claude Code that is ~/.claude/skills/ (all projects) or .claude/skills/ (one project).
Claude desktop and claude.ai. Zip the skill folder and upload the zip where the app manages skills:
cd skills && zip -r ../featspiration.zip featspiration
Use
Invoke it by name, with what to review:
/featspiration ../some-other-repo
Or just ask:
Check ../some-other-repo and the paper in docs/method.pdf and tell me what is useful for this project.
Plan these six ideas as prompts I can build one session at a time. My sessions are 5 hours.
The agent saves findings.json and the built page in your project under docs/featspiration/, and shows or publishes the page if its environment can.
How it works
The agent writes content only, as a findings.json file. A bundled script validates it and renders it into a fixed template, so every page looks the same and nothing is hand-written HTML.
node skills/featspiration/scripts/build.mjs findings.json -o findings.html
| Option | Does |
|---|---|
-o <file> | Output path. Default: next to the JSON. |
--check | Validate only. |
--fragment | Omit the document shell, for hosts that add their own (such as Claude's Artifact tool). |
The script needs Node 18 or newer and has no dependencies. It refuses to build when the data would produce a bad page (a feature that needs one listed after it, a missing prompt, a table row of the wrong width) and warns about habits that weaken one (thin prompts, no file paths, an overlong summary).
What is in the skill:
skills/featspiration/
SKILL.md the process the agent follows
assets/template.html the page design and behaviour
assets/example.findings.json a complete example to copy from
scripts/build.mjs validate and build
references/data-format.md every field of findings.json
references/writing-prompts.md how to write prompts that stand alone
references/design.md fonts, colour tokens and the rules behind them
The page
- Works as a single self-contained file. The only network request is for two Google Fonts, with system fallbacks.
- Dark and light, following the system or the host's theme. Phone-width friendly. Right-to-left ready.
- A filter by tier, a copy button on every prompt, and a "Built" tick per feature that is remembered in your browser.
- Every fixed string can be replaced through
labels, so a page can be written in any language.
Design
The look is fixed on purpose and documented in references/design.md: monochrome ink on black or warm off-white, a faint dot field, the Doto dot-matrix face for headings and numbers, hairlines in place of shadows, and colour only where it means something.
Licence
MIT. See LICENSE. Fonts are loaded from Google Fonts under their own licences (Doto and Inter Tight are both SIL Open Font License).
// HOW IT'S BUILT
KEY FILES