partnership-research-qa

Validate partnership research artifacts for existence, citations, and Connect mentions.

1|2|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/dimagi-internal/ace --skill partnership-research-qa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: partnership-research-qa
Source: https://github.com/dimagi-internal/ace/tree/main/skills/partnership-research-qa
Command: npx skills add https://github.com/dimagi-internal/ace --skill partnership-research-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of running downstream evaluation on incomplete or structurally invalid partnership research artifacts, preventing wasted effort on unqualified prospects and ensuring only high-quality research proceeds to assessment.

Core Features & Use Cases

  • Static Structural Checks: Runs 4 binary validation checks on partnership research outputs: existence in Google Drive, non-empty content, required citations in the deep research report, and explicit Connect capability mentions in the fit memo.
  • Gated Workflow Integration: Automatically blocks the downstream partnership-research-eval step if QA fails irrecoverably, enforcing quality guardrails for the ACE partnership opportunity pipeline.
  • Use Case: When completing an ACE partnership opportunity workflow, this Skill automatically validates the two research artifacts immediately after they are generated, so you never waste time evaluating prospects with missing or incomplete research.

Quick Start

Run the partnership-research-qa skill immediately after finishing the partnership-research step to validate all generated research artifacts for the current opportunity run before proceeding to evaluation.

Frequently Asked Questions about partnership-research-qa

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate partnership research artifacts before downstream evaluation?

You can validate partnership research artifacts by running static structural checks on deep-research.md and connect-fit.md files to verify existence, content completeness, required citations, and Connect capability mentions before proceeding to evaluation.

What static checks are applied to partnership research outputs during QA gating?

Partnership research QA applies four binary static checks: artifact existence in Google Drive, non-empty content validation, required citations in the deep research report, and explicit Connect capability mentions in the fit memo.

When do I need to run structural validation on partnership research files?

You need to run structural validation immediately after generating partnership research artifacts and before the evaluation step, ensuring only complete research with proper citations and capability mentions proceeds to downstream assessment.

Can I use static analysis without LLM invocation to gate partnership research evaluation?

Yes, partnership research QA uses only static analysis with no LLM invocation to produce a binary pass, fail, or incomplete verdict, providing auto-fix hints for failed checks to gate the downstream evaluation step.

What happens if structural validation fails on partnership research outputs?

When structural validation fails, the QA step blocks the downstream partnership-research-eval step and provides auto-fix hints for the failed checks, preventing wasted effort on incomplete or invalid research artifacts.

Does partnership research QA require any external dependencies or LLM calls?

No, partnership research QA operates with zero dependencies and uses only static analysis without any LLM invocation, performing binary validation checks entirely through structural inspection of the research artifacts.