Skip to content
Back to skills

Primr Qa

ASecurity

Review Primr outputs and diagnose integration issues. Use when the user wants report quality assessment, output review, or system health checks.

  • 3 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added May 26, 2026
testingrustapi

Works with

  • api
  • mcp

Security analysis

A100/100

Scanned May 27, 2026

npx -y skills add blisspixel/primr --skill primr-qa --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Primr Qa?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Primr Qa
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/blisspixel-primr-qa/badge)](https://www.skillsdirectory.com/skills/blisspixel-primr-qa)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---

name: primr-qa

version: "1.1.0"

description: "Review Primr outputs and diagnose integration issues. Use when the user wants report quality assessment, output review, or system health checks."

metadata:

  openclaw:

    requires:

      bins:

        - primr-mcp

      env:

        - XAI_API_KEY

        - GEMINI_API_KEY

      os:

        - linux

        - darwin

        - win32

mcp_server: primr

tools:

  - run_qa

  - doctor

resources:

  - primr://output/latest

  - primr://config

---



# Primr QA Skill



## Conceptual Framework



Use QA to judge research usefulness and trustworthiness, not just formatting. Use diagnostics when the failure is operational rather than editorial.



This skill should stay close to MCP outputs. Avoid embedding fixed provider assumptions in the skill body.



## Operational Capabilities



### 1. Run quality assessment



Read `primr://output/latest` when no path is specified, then call `run_qa` on the concrete report file.



```text

run_qa(report_path="output/exampleco/report.md")

```



### 2. Run diagnostics



Call `doctor` when the issue looks like environment, API, or runtime configuration rather than report quality.



### 3. Interpret results



Focus on factual gaps, weak evidence, and thin strategic interpretation before cosmetic issues.



## Error Handling



- QA failures: run `doctor` and confirm the report path.

- Low scores: identify the weakest sections and recommend one next action.

- Config issues: use `primr://config` and `doctor` to explain what is missing.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.