academic-venue-research
Skill111 starsChanged 5 months agoMITView on GitHub
Research target venue requirements and writing style for CS/AI/ML papers. Produces venue-brief.md with submission requirements and detailed writing style analysis. Use when: researching target journal/conference requirements, analyzing writing style of target venue, generating venue brief for paper writing, checking submission guidelines. Triggers on: venue research, 期刊调研, 目标期刊, writing style analysis, 写作风格分析, venue requirements, submission guidelines, 投稿要求, journal style, conference format.
In this repository7 other files it gives its agents.
- academic-citationSkill
- academic-experimentsSkill
- academic-figureSkill
- academic-latex-layoutSkill
- academic-paper-writerSkill
- academic-polishingSkill
- academic-reviserSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
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 12
Read manifest.yaml. It declares always_load files, axes, and references.on_demand.
- Very specific: line 13
Read every file listed under always_load.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Academic Venue Research
将此 skill 视为"期刊调研代理",负责调研目标期刊/会议的投稿要求和写作风格。
Router Protocol
- Read
manifest.yaml. It declaresalways_loadfiles,axes, andreferences.on_demand. - Read every file listed under
always_load. These are the skill's binding rules — not reference material. - Apply the loaded material as constraints:
stance.mddefines core rules, source hierarchy, and scope.red-lines.mddefines absolute prohibitions. Do not negotiate these.output-contract.mddefines deliverables per mode.
- Detect the mode using the manifest's
modeaxis:full-venue-research,requirements-only, orstyle-only. Source hierarchy rule: official guidelines > template docs > accepted paper observations > agent knowledge. If ambiguous, ask one concise question. - Echo the selected mode to the user before executing.
- Reach for
references/only when the manifest'sreferences.on_demandcondition is satisfied.
Modes
| Mode | Use when |
full-venue-research | Venue + local style papers or full brief request |
requirements-only | Venue name only, no style analysis needed |
style-only | Local style reference library, no requirements research |
Agent Dispatch
agents/venue-research-agent.md is dispatched by the orchestrator at Step 4. The agent returns Venue Brief Markdown content; it must not write files directly during orchestrated use. File writes are owned by the orchestrator.
Independent Use
| Input | Mode | Priority | Behavior |
| Venue + local style corpus | full-venue-research | 1 (explicit) | Full 4-step workflow |
| Venue only | requirements-only | 2 (single feature) | Requirements only |
| Local style corpus only | style-only | 3 (path trigger) | Style analysis only |
| Scenario | Recommended |
| Just researching venue | This skill (standalone) |
| Using results for paper writing | academic-paper-writer orchestrator |
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.

