How do I install the Update Moc skill?

Run npx skillmds@latest add majiayu000/update-moc in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Update Moc skill do?

Manage research area hubs (MOCs) with lean, project-focused organization It is listed under Research & Search on SkillMD.

Is Update Moc safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: CAUTION, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Update Moc?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Update Moc free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Update Moc?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Update Moc by majiayu000 — Agent Skill

Name: Update Moc
Rating: 4.666666666666667 (3 reviews)
Author: majiayu000

File contents

🗺️ Update MOC Skill

Maintain research area MOCs (MOCs/) by adding/removing project links and canonical papers.

CRITICAL RULES

MOC notes live only in MOCs/
MOCs organize projects (primary content)
MOCs may link to canonical/survey papers ONLY
NO paper dumping - exhaustive lists forbidden
Papers appear in MOC only if:
- Foundational/canonical for the field
- Survey or taxonomy paper
- Motivated multiple projects
If paper is relevant through only ONE project → do not add to MOC

WORKFLOW

1. Get MOC details

Ask user for:

MOC name (research area to update)
Action: Add projects? Add canonical papers? Remove items?
Items to add/remove (project or paper names)

2. Identify target MOC file

Location: MOCs/[MOC Name].md Find by: Search vault index or grep for MOC name

3. Validate before changes

For projects to add:

Verify project exists in Projects/
Verify project is NOT already in MOC
Verify project links to this MOC (bidirectional)

For papers to add:

Verify paper is foundational/canonical/survey
Verify paper is NOT already in MOC
Verify paper motivated multiple projects (or is canonical)

4. Update MOC

Add project links in Projects section: [[Project Name]]
Add paper links in Papers section (if canonical): [[Paper Title]]
Maintain alphabetical or logical order
Remove deprecated projects/papers

5. Verify bidirectional links

For each added project:

Open project file in Projects/
Verify project links to this MOC
If missing → notify user to add MOC link to project

For each added paper:

Verify paper does NOT link directly to MOC (forbidden)
Paper links only to projects

OUTPUT RULES

Bullet points only
Fragments preferred
No prose
Clear structure
Each section ≤5 bullets

SELF-CHECK

✅ Did I verify all items exist before adding? ✅ Are project links properly formatted: [[Project Name]]? ✅ Are paper links in Title Case: [[Paper Title]]? ✅ Did I check bidirectional project linking? ✅ Did I verify no forbidden paper→MOC links? ✅ Did I verify no paper dumping (only canonical papers)? ✅ MOC structure remains lean?

---name: update-mocdescription: Manage research area hubs (MOCs) with lean, project-focused organization--- ## 🗺️ Update MOC Skill Maintain research area MOCs (`MOCs/`) by adding/removing project links and canonical papers. --- ## CRITICAL RULES - MOC notes live **only** in `MOCs/` - MOCs organize **projects** (primary content) - MOCs may link to **canonical/survey papers ONLY** - **NO paper dumping** - exhaustive lists forbidden - Papers appear in MOC only if: - Foundational/canonical for the field - Survey or taxonomy paper - Motivated multiple projects - If paper is relevant through only ONE project → do not add to MOC --- ## WORKFLOW ### 1. Get MOC details Ask user for: - **MOC name** (research area to update) - **Action:** Add projects? Add canonical papers? Remove items? - **Items to add/remove** (project or paper names) ### 2. Identify target MOC file **Location:** `MOCs/[MOC Name].md` **Find by:** Search vault index or grep for MOC name ### 3. Validate before changes For **projects to add:** - Verify project exists in `Projects/` - Verify project is NOT already in MOC - Verify project links to this MOC (bidirectional) For **papers to add:** - Verify paper is foundational/canonical/survey - Verify paper is NOT already in MOC - Verify paper motivated multiple projects (or is canonical) ### 4. Update MOC - Add project links in Projects section: `[[Project Name]]` - Add paper links in Papers section (if canonical): `[[Paper Title]]` - Maintain alphabetical or logical order - Remove deprecated projects/papers ### 5. Verify bidirectional links For **each added project:** - Open project file in `Projects/` - Verify project links to this MOC - If missing → notify user to add MOC link to project For **each added paper:** - Verify paper does NOT link directly to MOC (forbidden) - Paper links only to projects --- ## OUTPUT RULES - Bullet points only - Fragments preferred - No prose - Clear structure - Each section ≤5 bullets --- ## SELF-CHECK ✅ Did I verify all items exist before adding? ✅ Are project links properly formatted: `[[Project Name]]`? ✅ Are paper links in Title Case: `[[Paper Title]]`? ✅ Did I check bidirectional project linking? ✅ Did I verify no forbidden paper→MOC links? ✅ Did I verify no paper dumping (only canonical papers)? ✅ MOC structure remains lean?

Frequently asked questions

Update Moc