[Flock Action] Evaluate Flock

[zircote]

Action

Evaluate Flock

LPN IDs

6401492020FLE249
6401492022FLE002
6401492023FLE078
6401492025FLE011
6401492025FLE024

Trait Weights

No response

Sort Trait

No response

Notes

Test with github network ecosystem added.

[zircote]

🎯 Agentic Issue Triage

This is an automated Flock Action request to evaluate sheep genetic performance for 5 animals from the NSIP database.

Summary

Action Type: Evaluate Flock
Animal Count: 5 LPN IDs provided
Note: "Test with github network ecosystem added"

The issue follows the standard flock-action template and requests a genetic evaluation of 5 sheep (LPNs: 6401492020FLE249, 6401492022FLE002, 6401492023FLE078, 6401492025FLE011, 6401492025FLE024).

📋 Workflow Details

What the Flock Action Workflow Will Do

According to .github/workflows/flock-action.md, the "Evaluate Flock" action will:

1. Call details for each LPN ID to retrieve the full EBV (Estimated Breeding Value) profile
2. Call trait_ranges for the animal's breed to establish benchmarks
3. Produce a summary table with all animals and their EBVs positioned against breed ranges

Expected Output Artifacts

The workflow will create files in reports/{YYYY-MM-DD}-evaluate-flock/:

• report.md - Formatted analysis with data tables, key findings, and methodology
• data.csv - Machine-readable CSV export

A pull request will be opened with:

• Branch: flock-action/61-evaluate-flock
• Title: [Flock Action] Evaluate Flock - 5 animals
• Auto-closes this issue when merged

🔍 Technical Context

NSIP MCP Server

This workflow leverages the nsip MCP (Model Context Protocol) server with 13 tools for sheep genetic analysis. The server is launched via the Docker container ghcr.io/zircote/nsip with the mcp entrypoint.

Key MCP Tools Used:

• details - Retrieve animal EBV profiles
• trait_ranges - Get breed-specific benchmarks
• flock_summary - Aggregate statistics

Documentation:

• MCP Server Reference
• Genetic Evaluation Guide
• LLM Usage Guides

LPN ID Format

The provided LPN IDs follow the standard format:

• 640 prefix = Breed group ID
• Year component (1492020, 1492022, 1492023, 1492025)
• FLE = Flock code
• Individual animal number

🧪 Testing Note

The user noted: "Test with github network ecosystem added"

This appears to be a test run to validate the recently added GitHub network access in the workflow configuration (.github/workflows/flock-action.md lines 14-19):

network:
  allowed:
    - defaults
    - github
    - containers
    - "nsip.org"

This network configuration enables the workflow to:

• Access GitHub APIs (issue/PR creation)
• Pull the nsip container from ghcr.io
• Query the NSIP Search API at nsip.org

📊 Similar Issues

Open flock-action issues:

• [Flock Action] Evaluate Flock #62, [Flock Action] Evaluate Flock #60, [Flock Action] Evaluate Flock #58 - Also "Evaluate Flock" requests

Closed flock-action issues:

• [Flock Action] Evaluate Flock #56, [Flock Action] Evaluate Flock #55, [Flock Action] Evaluate Flock #52, [Flock Action] Evaluate Flock #51, [Flock Action] Evaluate Flock - Test Run 2 #49, [Flock Action] Evaluate Flock - Test Run #48 - Previous successful evaluations

Related:

• Add GitHub automation documentation for flock-action workflow #50 - Documentation for flock-action workflow
• [agentics] Flock Action failed #40 - Flock Action workflow failure (debugging reference)

---

Status: Ready for automated processing by the flock-action workflow.
Priority: Normal - Appears to be a test/validation run.

Generated by Agentic Triage for issue #61

To install this workflow, run gh aw add githubnext/agentics/workflows/issue-triage.md@eb7950f37d350af6fa09d19827c4883e72947221. View source at https://github.com/githubnext/agentics/tree/eb7950f37d350af6fa09d19827c4883e72947221/workflows/issue-triage.md.