academic-venue-research

Name: academic-venue-research
Author: joshua-zyy

101stars1forks

How to install academic-venue-research?

joshua-zyy/academic-paper-writer/academic-venue-research

$npx -y skills add joshua-zyy/academic-paper-writer --skill academic-venue-research

Installs into the current project.

Summary

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 ve

Files · 1

View on GitHub

SKILL.md

1	# Academic Venue Research
2
3	将此 skill 视为"期刊调研代理"，负责调研目标期刊/会议的投稿要求和写作风格。
4
5	## Router Protocol
6
7	1. Read `manifest.yaml`. It declares `always_load` files, `axes`, and `references.on_demand`.
8	2. Read every file listed under `always_load`. These are the skill's binding rules — not reference material.
9	3. Apply the loaded material as constraints:
10	- `stance.md` defines core rules, source hierarchy, and scope.
11	- `red-lines.md` defines absolute prohibitions. Do not negotiate these.
12	- `output-contract.md` defines deliverables per mode.
13	4. Detect the mode using the manifest's `mode` axis: `full-venue-research`, `requirements-only`, or `style-only`. Source hierarchy rule: official guidelines > template docs > accepted paper observations > agent knowledge. If ambiguous, ask one concise question.
14	5. Echo the selected mode to the user before executing.
15	6. Reach for `references/` only when the manifest's `references.on_demand` condition is satisfied.
16
17	## Modes
18
19	\| Mode \| Use when \|
20	\|---\|---\|
21	\| `full-venue-research` \| Venue + local style papers or full brief request \|
22	\| `requirements-only` \| Venue name only, no style analysis needed \|
23	\| `style-only` \| Local style reference library, no requirements research \|
24
25	## Agent Dispatch
26
27	`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.
28
29	## Independent Use
30
31	\| Input \| Mode \| Priority \| Behavior \|
32	\|---\|---\|---\|---\|
33	\| Venue + local style corpus \| full-venue-research \| 1 (explicit) \| Full 4-step workflow \|
34	\| Venue only \| requirements-only \| 2 (single feature) \| Requirements only \|
35	\| Local style corpus only \| style-only \| 3 (path trigger) \| Style analysis only \|
36
37	\| Scenario \| Recommended \|
38	\|---\|---\|
39	\| Just researching venue \| This skill (standalone) \|
40	\| Using results for paper writing \| academic-paper-writer orchestrator \|

People who liked this also viewed

6 picks

Type

academic-venue-research

101stars1forks

View on GitHub

How to install academic-venue-research?

joshua-zyy/academic-paper-writer/academic-venue-research

$npx -y skills add joshua-zyy/academic-paper-writer --skill academic-venue-research

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Academic Venue Research
2
3	将此 skill 视为"期刊调研代理"，负责调研目标期刊/会议的投稿要求和写作风格。
4
5	## Router Protocol
6
7	1. Read `manifest.yaml`. It declares `always_load` files, `axes`, and `references.on_demand`.
8	2. Read every file listed under `always_load`. These are the skill's binding rules — not reference material.
9	3. Apply the loaded material as constraints:
10	- `stance.md` defines core rules, source hierarchy, and scope.
11	- `red-lines.md` defines absolute prohibitions. Do not negotiate these.
12	- `output-contract.md` defines deliverables per mode.
13	4. Detect the mode using the manifest's `mode` axis: `full-venue-research`, `requirements-only`, or `style-only`. Source hierarchy rule: official guidelines > template docs > accepted paper observations > agent knowledge. If ambiguous, ask one concise question.
14	5. Echo the selected mode to the user before executing.
15	6. Reach for `references/` only when the manifest's `references.on_demand` condition is satisfied.
16
17	## Modes
18
19	\| Mode \| Use when \|
20	\|---\|---\|
21	\| `full-venue-research` \| Venue + local style papers or full brief request \|
22	\| `requirements-only` \| Venue name only, no style analysis needed \|
23	\| `style-only` \| Local style reference library, no requirements research \|
24
25	## Agent Dispatch
26
27	`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.
28
29	## Independent Use
30
31	\| Input \| Mode \| Priority \| Behavior \|
32	\|---\|---\|---\|---\|
33	\| Venue + local style corpus \| full-venue-research \| 1 (explicit) \| Full 4-step workflow \|
34	\| Venue only \| requirements-only \| 2 (single feature) \| Requirements only \|
35	\| Local style corpus only \| style-only \| 3 (path trigger) \| Style analysis only \|
36
37	\| Scenario \| Recommended \|
38	\|---\|---\|
39	\| Just researching venue \| This skill (standalone) \|
40	\| Using results for paper writing \| academic-paper-writer orchestrator \|

People who liked this also viewed

6 picks

Type