Citations

PDF-RAG API reference. REQUIRED after any failed curl/jq to localhost:8000 (404, null, jq error). Also use when uncertain about endpoint path or response shape.

Extract and maintain company-specific coding best practices from PR review comments. Use when the user requests to analyze PR comments from a repository to generate best practices documentation, or when implementing features and needs to reference established coding standards. Triggers include requests like "analyze PR comments and create best practices", "extract coding standards from repo X", or "check if this code follows our best practices".

Internal resource library for HeyReach integration. Contains shared API client, operation scripts, and reference documentation.

ARCHIVE REFERENCE ONLY. Superseded by modular skills (`mds-messaging-direction-summary`, `voice-and-tone`, `product-positioning-summary`). Use as inspiration; do not invoke in orchestrated flow.

Teaches how to use Bluera Knowledge for accessing library sources and reference material. Explains two approaches - vector search via MCP/slash commands for discovery, or direct Grep/Read access to cloned repos for precision. Shows when to use each method and example workflows for querying library internals.

Comprehensive guide for writing technical books in Markdown format. Use this skill when creating new chapters, managing code examples, reviewing content for technical accuracy and consistency, or organizing book structure (TOC, cross-references). Provides templates, validation scripts, and best practices for technical writing workflows.

Format citations and bibliographies in multiple academic styles (APA, IEEE, Chicago, Harvard, MLA, Nature, Science). Use when: (1) Converting between citation styles for different journals, (2) Cleaning and standardizing bibliography entries, (3) Validating citation formatting before submission, (4) Generating properly formatted reference lists, (5) Checking citation consistency across manuscripts.

Use when creating or editing agent definitions - ensures proper frontmatter, clear structure, validation of references, and no duplication with existing agents

Reference and maintain the project's technical stack documentation including frameworks, languages, databases, testing tools, and third-party services to ensure consistency across all development work. Use this skill when choosing technologies for new features, when documenting technology decisions, when working with framework-specific code patterns, or when ensuring consistency with existing technology choices. Use this skill when working with any code file to verify it follows the conventions of the project's chosen frameworks and tools. Use this skill when setting up new dependencies, configuring build tools, or making architectural decisions about which libraries or services to use. Use this skill when onboarding new team members or creating technical documentation about the project's architecture and technology choices.

Provides quick reference for BI Dashboard (Plotly Dash) commands and operations. Activates when user asks how to run, test, or verify the BI Dashboard. Includes startup, shutdown, verification, and troubleshooting procedures.

Orchestrate the complete LA-Bench experimental procedure generation workflow from JSONL input to validated output. This skill should be used when processing LA-Bench format experimental data to generate and validate detailed experimental procedures. It coordinates parsing, reference fetching, procedure generation, and quality validation with 10-point scoring.

Self-reference guide for Claude Code's own architecture, configuration, and extension points. Use when needing to know where Claude Code stores its configuration files, skills, plugins, hooks, MCP servers, settings, or any other internal structure. Triggers on questions like "where do skills go?", "how do I configure hooks?", "where is the settings file?", or when creating/modifying Claude Code extensions.

Execute project release workflows by locating and following project-specific RELEASE_GUIDE.md in the repository root or docs/. Use when asked to perform a release, publish a release, cut a tag, run release steps, or when a user references RELEASE_GUIDE.md.

Direct Preference Optimization (DPO) for aligning models with preference data without separate reward models. Triggers: dpo, preference optimization, rlhf, ref_model=none, patchdpotrainer, dpotrainer.

Advanced code search tool that finds definitions, usages, tests, and references across the entire codebase. Use when you need to understand how a symbol is used throughout the project.

Identifies dependencies between GitHub issues and creates appropriate cross-references. Use when you need to map issue relationships, find blockers, or organize work order based on dependencies.

Vitest + Storybook testing strategy with clear role separation.Reference for implementing unit tests and UI interaction tests.

Use when creating reusable process documentation. Apply TDD: baseline without skill → document failures → write skill → test → iterate. Four types: Discipline, Technique, Pattern, Reference. Iron Law: No skill without failing test first.

程式碼/報告生成。觸發詞：生成程式碼, Python 函數, LaTeX, 報告, export。

Quick reference for uv (fast Python package manager) operations to save tokens. Use when creating virtual environments, installing packages, managing dependencies, or when user asks about uv commands. Provides concise patterns for Python project setup and package management.