paper-workspace
Skill4 starsChanged 2 months agoLicence not identifiedView on GitHub
Set up a diff-approval paper workspace: journal guidelines fixed in 01_requirements.md, 02_plan.md as the thick spec, one Markdown file per section, Pandoc + CSL to Word, Git required. AI edits only manuscript files; data is read-only. Ends with ai-use-disclosure. Use when starting a new paper or migrating a draft into a diff-approval workflow.
In this repository23 other files it gives its agents.
- ai-use-disclosureSkill
- cec-tableSkill
- citation-verificationSkill
- email-draftSkill
- exam-rubricSkill
- kakenhi-draftSkill
- kakenhi-reviewerSkill
- literature-reviewSkill
- paper-review-replySkill
- syllabus-genSkill
- gumroad-productSkill
- product-copySkill
- quick-mvpSkill
- ship-checkSkill
- stripe-setupSkill
- supabase-authSkill
- vercel-domainSkill
- dep-auditSkill
- explain-codeSkill
- session-handoffSkill
- humanizer_academicSkill
- note-draftSkill
- wp-rich-articleSkill
The file
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.