integrate-resources
Skill8 starsChanged 27 days agoMITView on GitHub
Process new resources dropped into resources/unread/. Extracts Claude Code tips, tools, patterns and updates the setup guide, skills, hooks, and knowledge catalog.
- Installs packages
4 other projects use a version of this, 3 of them edited.
Adopted by
Most recently taken up by
- naman10parikh/pennyedited, first seen Nov 8, 2026
- naman10parikh/turboedited, first seen Oct 25, 2026
- naman10parikh/pixeledited, first seen Oct 25, 2026
- naman10parikh/agentgridword for word, first seen Oct 20, 2026
Other versions4 projects use a version of this.
Word for word · 1
- naman10parikh/agentgrid★ 9100% same
Edited · 3
- naman10parikh/penny★ 096% same
- naman10parikh/pixel★ 096% same
- naman10parikh/turbo★ 096% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository31 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- agent-runtimeSkill
- frontend-designSkill
- architectSkill
- deep-thinkSkill
- design-systemsSkill
- ecosystem-referenceSkill
- fractal-delegationSkill
- harness-reviewSkill
- heartbeatSkill
- llm-council-critiqueSkill
- loop-createSkill
- mcp-setupSkill
- memory-compressionSkill
- memorySkill
- model-routingSkill
- oss-project-scaffoldSkill
- playwright-cliSkill
- repo-scoutSkill
- self-improveSkill
- skill-creatorSkill
- skill-routingSkill
- sprintSkill
- test-visualSkill
- troubleshootSkill
- ux-auditSkill
- wikimem-ingest-pipelineSkill
- wikimem-observerSkill
- wikimemSkill
The file
We split this skill into the rules it gives an agent
12 rules. 10 are common, 0 are distinctive, and 2 are very specific to this project.
10
Common
Most of the 3 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 32
Add MCP servers to .mcp.json
- Common: line 36
Add wikilinks in existing vault notes to connect new knowledge
- Common: line 37
Update frontmatter tags on relevant notes
- Very specific: line 43
NO new random documents: Do not create resources/research/, content/intelligence/reports/, or any other new standalone files for daily …
- Common: line 44
Dedup before writing: Check if an insight is already present.
- Common: line 45
Only add high-value touchpoints not already covered.
- Common: line 46
Never remove existing content — only enhance
- Common: line 47
If a tip contradicts existing guidance, flag it for human review
- Common: line 48
Prefer concrete, actionable configurations over vague advice
- Common: line 49
Always include source attribution inline (not in a separate catalog)
- Common: line 50
Test any new hook or setting configurations for correctness
- Common: line 51
This pipeline builds the NEXT thing: Every run should make the harness smarter, the content engine sharper, the vault more connected.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Trigger
User says something like "new resources to integrate" or "process unread resources"
Process
- List all files in
resources/unread/ - Triage: batch-read all files, assign relevance 1-5 and category (HARNESS/AGENT/PRODUCT/CONTENT/CRYPTO/TECH/DESIGN/IRRELEVANT)
- For each file with relevance >= 3:
a. Read the full content
b. Check: is this insight ALREADY covered in our docs? If yes, skip or enhance existing text only.
c. Extract actionable items:
- Tools/packages to install (
npm install, MCP servers, CLI tools) - Skills/hooks patterns to adopt
- Strategic insights that shift our architecture or content
- Competitor moves that require response d. For mentioned projects/tools: WebSearch to get current state, repo URL, install instructions
- Tools/packages to install (
- WEAVE into EXISTING documents — route by CATEGORY per
.claude/rules/resource-integration.md:- Tier 1 (ALL categories): VISION.md, LEARNINGS.md, x-content-engine skill, vault notes
- Tier 2 (CONTENT): content/distribution/ playbooks (MASTER-PLAYBOOK.md, PUBLISHING-WORKFLOW.md, PLATFORM-SPECIFIC-HOOKS.md), vault Ops - Content Engine / Distribution Playbook
- Tier 3 (CRYPTO/EARNING): agents/earning/strategies/, vault Ops - Earning Strategy, MAINTAINER-CHECKLIST.md
- Tier 4 (HARNESS/AGENT): .claude/skills/, .claude/rules/, CLAUDE.md, .mcp.json, install tools
- Tier 5 (DESIGN): .claude/rules/design.md, .claude/skills/design-systems/knowledge/
- See
.claude/rules/resource-integration.mdfor the COMPLETE routing table with 5 tiers and quick-reference chart
- INSTALL actionable tools immediately:
npm install -g <tool>for CLI tools- Add MCP servers to
.mcp.json - Download skills/hooks from discovered repos
- Update Obsidian vault relationships:
- Trace through
vault/MOC - Energy Platform.mdfor where new knowledge connects - Add wikilinks in existing vault notes to connect new knowledge
- Update frontmatter tags on relevant notes
- Trace through
- Move processed files to
resources/read/with date prefix:YYYY-MM-DD_originalname - Summarize: what was integrated, WHERE it was integrated, what was installed
Rules (HARD — Maintainer Directive)
- NO new random documents. Do not create
resources/research/,content/intelligence/reports/, or any other new standalone files for daily intake. Weave into existing docs. - Dedup before writing. Check if an insight is already present. If yes, enhance the existing text — don't duplicate.
- Only add high-value touchpoints not already covered. Most articles will be "interesting but already addressed."
- Never remove existing content — only enhance
- If a tip contradicts existing guidance, flag it for human review
- Prefer concrete, actionable configurations over vague advice
- Always include source attribution inline (not in a separate catalog)
- Test any new hook or setting configurations for correctness
- This pipeline builds the NEXT thing. Every run should make the harness smarter, the content engine sharper, the vault more connected. It's a compounding intelligence loop sourced from the community and the digital AI town square.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

