> ## Documentation Index
> Fetch the complete documentation index at: https://learn.getodin.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Agent Skills Library

> Browse all pre-built skills available out of the box

The following pre-built skills are available out of the box, organized by category. Each skill includes an overview, instructions for when to trigger it, and a step-by-step workflow for the agent to follow. You can use these skills as-is or customize them to fit your specific needs.

### Development

<AccordionGroup>
  <Accordion title="code-review — Structured code review checklist covering quality, security, and best practices.">
    **Overview:** Gives your agent a consistent, structured approach to reviewing code. When triggered, the agent evaluates submissions across six dimensions — correctness, security, performance, readability, testing, and architecture — and outputs findings in a standardized format with severity ratings and actionable recommendations.

    **Allowed agent toolkits:** `knowledge base`

    **Trigger keywords:** `code review`, `review code`, `review this code`, `review my code`

    **Instructions:**

    When reviewing code:

    1. **Correctness** — Does the code do what it's supposed to? Edge cases handled?
    2. **Security** — Any injection risks, exposed secrets, or auth bypasses?
    3. **Performance** — Obvious N+1 queries, unnecessary loops, or memory leaks?
    4. **Readability** — Clear naming, appropriate comments, consistent style?
    5. **Testing** — Are there tests? Do they cover the happy path and edge cases?
    6. **Architecture** — Does this fit the existing patterns? Any unnecessary coupling?

    For each finding, provide:

    * **Severity**: Critical / Warning / Suggestion
    * **Location**: File and line reference
    * **Description**: What the issue is
    * **Recommendation**: How to fix it
  </Accordion>

  <Accordion title="github-ops — GitHub issue and pull request management.">
    **Overview:** Enables your agent to manage GitHub workflows end-to-end. From creating and labeling issues to reviewing pull requests and surfacing stale items, this skill keeps your repository organized and your team unblocked — without leaving the agent.

    **Allowed agent toolkits:** `github`

    **Trigger keywords:** `github`, `pull request`, `PR review`, `issue tracker`, `repository`

    **Instructions:**

    When the user asks about GitHub issues, pull requests, or repository management:

    1. **Issue management**
       * Search existing issues before creating duplicates
       * Apply appropriate labels and assignees
       * Link related issues when relevant
    2. **Pull request review**
       * Summarize the changes in the PR
       * Check for potential issues (missing tests, breaking changes)
       * Suggest improvements with specific line references
    3. **Repository insights**
       * Provide activity summaries when asked
       * Track open issues and PR counts
       * Highlight stale items that need attention
  </Accordion>
</AccordionGroup>

### Operations

<AccordionGroup>
  <Accordion title="daily-digest — Compile and send a daily morning briefing covering tracked topics.">
    **Overview:** Turns your agent into a personal briefing assistant. Every morning, it searches for the latest updates across your tracked topics and compiles them into a clean, structured digest — top stories, categorized updates, action items, and a calendar preview — delivered via your preferred channel.

    **Allowed agent toolkits:** `web search`

    **Trigger keywords:** `daily digest`, `morning briefing`, `send briefing`, `daily summary`

    **Instructions:**

    When asked to create a daily digest or morning briefing:

    1. Check the current date and identify key topics the user tracks
    2. Search for recent news, updates, and changes on each tracked topic
    3. Compile findings into a structured briefing format:
       * **Date and greeting**
       * **Top stories** (3–5 most important items)
       * **By category** — group remaining items by topic area
       * **Action items** — anything requiring the user's attention today
       * **Calendar preview** — upcoming events if calendar data is available
    4. Keep each item to 2–3 sentences maximum
    5. Send via the user's preferred channel if configured
  </Accordion>

  <Accordion title="meeting-notes — Summarize meeting transcripts into structured notes with action items.">
    **Overview:** Transforms raw meeting transcripts into concise, actionable notes. The agent extracts key decisions, organizes discussion highlights by topic, and produces a clean action item table with owners and deadlines — so nothing falls through the cracks after a call.

    **Allowed agent toolkits:** `knowledge base`

    **Trigger keywords:** `meeting notes`, `summarize meeting`, `meeting summary`, `meeting recap`

    **Instructions:**

    When summarizing a meeting transcript or recording:

    1. **Meeting metadata** — Date, attendees, duration, topic
    2. **Key decisions** — Bulleted list of decisions made
    3. **Discussion highlights** — Major points discussed, organized by topic
    4. **Action items** — Table format:

    | Action | Owner | Deadline |
    | ------ | ----- | -------- |

    Extract every commitment or task mentioned.

    5. **Open questions** — Unresolved items that need follow-up
    6. **Next meeting** — Date/time if mentioned

    Keep the summary concise — aim for 1/10th the length of the original transcript.
  </Accordion>

  <Accordion title="onboarding-guide — Create structured onboarding guides for new team members or users.">
    **Overview:** Helps your agent generate tailored onboarding experiences for new hires or users. It builds comprehensive guides covering week-one essentials, 30-day milestones, key contacts, FAQs, and success metrics — all adapted to the specific role and organization.

    **Allowed agent toolkits:** `knowledge base`

    **Trigger keywords:** `onboarding`, `new hire`, `getting started guide`, `orientation`

    **Instructions:**

    When creating an onboarding guide:

    1. **Identify the audience** — New employee? New user? Role-specific?
    2. **Week 1 essentials**:
       * Account setup and access provisioning
       * Key tools and where to find them
       * Team introductions and org chart
       * First-day checklist
    3. **First 30 days**:
       * Learning resources and documentation
       * Shadowing schedule
       * Key processes to understand
       * First small tasks or projects
    4. **Key contacts** — Who to ask for what
    5. **FAQ** — Common questions new people have
    6. **Success metrics** — What does a successful first 90 days look like?

    Tailor the guide based on available information about the organization and role.
  </Accordion>

  <Accordion title="report-builder — Generate structured reports with executive summaries, data sections, and recommendations.">
    **Overview:** Equips your agent to produce polished, publication-ready reports from scratch. It pulls data from your knowledge base, database, or the web, then structures it into a complete report with an executive summary, analysis, recommendations, and properly cited sources.

    **Allowed agent toolkits:** `knowledge base`, `database`, `web search`

    **Trigger keywords:** `build report`, `generate report`, `create report`, `write report`

    **Instructions:**

    When asked to create a report:

    1. **Clarify scope** — What is the report about? Who is the audience? What time period?
    2. **Gather data** — Pull from available sources (KB, database, web search)
    3. **Structure the report**:
       * **Title page** — Report name, date, author
       * **Executive summary** — 3–5 sentences covering the key takeaway
       * **Table of contents** — For reports with 3+ sections
       * **Data sections** — Each with a clear heading, narrative, and supporting data/charts
       * **Analysis** — What the data means, trends identified
       * **Recommendations** — Actionable next steps based on findings
       * **Appendix** — Raw data, methodology notes, or detailed tables
    4. **Format for readability** — Use headers, bullets, tables, and bold for key numbers
    5. **Cite sources** — Reference where data came from
  </Accordion>
</AccordionGroup>

### Analytics

<AccordionGroup>
  <Accordion title="data-analysis — Structured data analysis workflow: explore, clean, analyze, and visualize datasets.">
    **Overview:** Gives your agent a rigorous, end-to-end approach to working with data. From understanding the dataset and checking data quality to running exploratory analysis, building visualizations, and summarizing findings — this skill ensures every analysis is thorough, focused, and clearly communicated.

    **Allowed agent toolkits:** `database`, `python`

    **Trigger keywords:** `analyze data`, `data analysis`, `explore dataset`, `data insights`

    **Instructions:**

    When asked to analyze data:

    1. **Understand the data** — What tables/files are available? What do columns represent?
    2. **Data quality check** — Look for nulls, duplicates, outliers, and inconsistencies
    3. **Exploratory analysis**
       * Summary statistics (count, mean, median, min, max)
       * Distribution of key variables
       * Correlation between variables
    4. **Answer the question** — Focus analysis on what the user specifically wants to know
    5. **Visualize** — Create charts where they add clarity (bar, line, scatter, etc.)
    6. **Summarize findings** — Clear narrative with supporting numbers
    7. **Recommend next steps** — What additional analysis could be valuable?
  </Accordion>
</AccordionGroup>

### Communication

<AccordionGroup>
  <Accordion title="email-draft — Draft professional emails with appropriate tone, structure, and call-to-action.">
    **Overview:** Helps your agent write clear, professional emails every time. It adapts tone to the recipient and context, structures the message for maximum clarity, and ensures every email ends with a specific, actionable ask — keeping communication concise and effective.

    **Allowed agent toolkits:** none

    **Trigger keywords:** `draft email`, `write email`, `compose email`, `email draft`

    **Instructions:**

    When drafting an email:

    1. **Determine the context** — Who is the recipient? What is the relationship? What is the goal?
    2. **Choose the tone** — Formal, semi-formal, or casual based on context
    3. **Structure the email**:
       * **Subject line** — Clear and specific (not "Quick question" or "Follow up")
       * **Opening** — Brief greeting + context/purpose in 1–2 sentences
       * **Body** — Key information, organized with bullets or short paragraphs
       * **Call to action** — What you need from the recipient, with a specific deadline if applicable
       * **Closing** — Appropriate sign-off
    4. **Keep it concise** — Most emails should be under 200 words
    5. **Review** — Check for typos, unclear language, and missing information
  </Accordion>
</AccordionGroup>

### Support

<AccordionGroup>
  <Accordion title="ticket-triage — Categorize and prioritize incoming support tickets using consistent criteria.">
    **Overview:** Brings consistency and speed to your support queue. The agent reads each incoming ticket, categorizes it, assigns a priority level, extracts key details, and suggests the right team for routing — then drafts an acknowledgment response, all in one pass.

    **Allowed agent toolkits:** none

    **Trigger keywords:** `ticket triage`, `triage tickets`, `categorize ticket`, `support ticket`, `classify ticket`

    **Instructions:**

    When triaging a support ticket:

    1. **Read the ticket** thoroughly, including any attachments or context
    2. **Categorize** into one of: Bug, Feature Request, Question, Account Issue, Integration Issue, Other
    3. **Assess priority** using:
       * **Critical** — Service down, data loss, security breach
       * **High** — Major feature broken, many users affected
       * **Medium** — Feature partially working, workaround exists
       * **Low** — Cosmetic, nice-to-have, single user edge case
    4. **Extract key details**: affected component, reproduction steps, user impact
    5. **Suggest routing** to the appropriate team (Engineering, Support, Product, Billing)
    6. **Draft a response** acknowledging the issue with an estimated timeline
  </Accordion>
</AccordionGroup>

### Research

<AccordionGroup>
  <Accordion title="research-deep — Multi-source deep research compilation with structured output and source citations.">
    **Overview:** Turns your agent into a thorough research analyst. It defines the scope, queries multiple sources, cross-references findings for contradictions, and synthesizes everything into a structured report with an executive summary, subtopic breakdowns, and full source citations.

    **Allowed agent toolkits:** `web search`, `knowledge base`

    **Trigger keywords:** `research`, `deep dive`, `investigate`, `comprehensive analysis`

    **Instructions:**

    When asked to research a topic thoroughly:

    1. **Scope definition** — Clarify the research question and boundaries
    2. **Multi-source search** — Query at least 3 different sources or angles
    3. **Cross-reference** — Identify agreements and contradictions across sources
    4. **Synthesize** — Compile findings into a structured report:
       * Executive summary (3–5 key points)
       * Detailed findings organized by subtopic
       * Conflicting information flagged clearly
       * Source citations for all claims
    5. **Actionable takeaways** — End with recommended next steps
  </Accordion>
</AccordionGroup>