promote
The `/promote` command generates platform-specific promotional content for accepted academic papers across Twitter/X, LinkedIn, blog posts, and news outlets. Use this tool approximately one week before a conference to create coordinated, tailored announcements that include relevant links and visuals for each distribution channel.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/Galaxy-Dawn/claude-scholar/HEAD/commands/promote.md -o ~/.claude/commands/promote.mdpromote.md
# Generate Promotion Content Use the `post-acceptance` skill to prepare accurate promotion content for an accepted paper. ## Workflow 1. Ask for the paper, acceptance venue, public links, key result, and target platforms. 2. Separate claims supported by the paper from broader promotional language. 3. Draft platform-specific content for X, LinkedIn, blogs, or news pages. 4. Check names, links, numbers, image rights, and accessibility text. 5. Return editable drafts before offering any publishing step. ## Optional Xquik workflow Use Xquik only when the user asks for live X context, draft analysis, or publishing. Load `references/xquik-promotion.md` from the `post-acceptance` skill before using it. - Keep public searches bounded by query, dates, and result count. - Treat posts as public context, not scholarly evidence. - Draft locally when Xquik MCP is unavailable. - Show the complete account, text, links, media, and public effect before a write. - Publish only after explicit approval for that exact payload. - Never retry a write automatically. ## Delivery Return each draft under its target platform. Include a short fact-check list and any unresolved placeholders. If an approved X post succeeds, return its action status and public URL when available.
Use when creating or configuring Claude Code agents and their frontmatter.
Run a blocker-first post-experiment workflow: validate evidence, produce strict statistical analysis when possible, and generate a decision-oriented results report only when the analysis bundle is sufficient. Uses results-analysis + results-report as a gated two-stage workflow.
Use only when creating new registrable ML components that require Factory or Registry patterns.
This skill should be used when the user asks to "debug this", "fix this error", "investigate this bug", "troubleshoot this issue", "find the problem", "something is broken", "this isn't working", "why is this failing", or reports errors/exceptions/bugs. Provides systematic debugging workflow and common error patterns.
This skill provides reference guidance for citation verification in academic writing. Use when the user asks about "citation verification best practices", "how to verify references", "preventing fake citations", or needs guidance on citation accuracy. This skill supports ml-paper-writing by providing detailed verification principles and common error patterns.
This skill should be used when the user asks to review a diff or pull request, write review comments, audit code quality, establish review standards, or improve how a team performs code review.
Expert code review specialist. Proactively reviews code for quality, security, and maintainability. Use immediately after writing or modifying code. MUST BE USED for all code changes.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.