Venue Evidence Audit logo

Venue Evidence Audit

Community
cpt13-g
venue-evidence-audit

Audit recent high-relevance papers from a target venue to identify claim-relevant experimental evidence gaps after core P0 results exist. Use for venue completeness and reviewer-risk analysis; not for redefining the research question or running experiments.

Overview

Publishercpt13-g
Repositorybuild-research-evidence
Skill namevenue-evidence-audit
Stars
50
Forks
2
Bundled files
1
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by cpt13-g on GitHub. Read the source before you install it.

Installation

Install the Venue Evidence Audit AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/cpt13-g/build-research-evidence/tree/main/.agents/skills/venue-evidence-audit
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/cpt13-g/build-research-evidence.git /tmp/build-research-evidence
mkdir -p .claude/skills
cp -r /tmp/build-research-evidence/.agents/skills/venue-evidence-audit .claude/skills/venue-evidence-audit
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Venue Evidence Audit in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Venue Evidence Audit on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Venue Evidence Audit is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Venue Evidence Audit

Run only when the Orchestrator authorizes the audit and P0 is substantially complete. Start with python tools/context_view.py show --role venue, then read referenced Claim-Evidence and gap artifacts. Read docs/PROTOCOLS.md, docs/ROLE_HANDOFFS.md, docs/CONTEXT_POLICY.md and docs/EVIDENCE_COMPLETION_PROTOCOL.md on a fresh context or changed hash. Reuse an existing dated source set only when its task, venue, freshness and coverage still fit; search further for changed expectations or unresolved gaps. Context savings never justify skipping relevant papers or negative evidence.

Analyze 5-10 recent, highly relevant papers, prioritizing same task, research question, method class, venue and recency. Record search date, sources, relevance, inclusion/exclusion reasons and uncertainty. Stop once core expectations, material gaps and high-ROI actions are stable; do not expand into a systematic review. Compare datasets, baselines, metrics, seed/statistical practice, ablations, sensitivity, robustness, generalization, efficiency, complexity, qualitative analysis and figure/table conventions.

Produce an Evidence Gap Matrix with current status, venue frequency, Claim relevance, reviewer risk, estimated cost, information gain and recommended priority. Recommendations do not enter the queue automatically. A common but Claim-irrelevant experiment is P3/SKIP. Do not alter the Research Spine, Primary Claims or Method, and report any positioning concern only as risk.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Venue Evidence Audit AI skill do?

Audit recent high-relevance papers from a target venue to identify claim-relevant experimental evidence gaps after core P0 results exist. Use for venue completeness and reviewer-risk analysis; not for redefining the research question or running experiments.

Why use Venue Evidence Audit on TypingMind?

Because you install it once and use it with any model. Venue Evidence Audit is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Venue Evidence Audit in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/cpt13-g/build-research-evidence/tree/main/.agents/skills/venue-evidence-audit. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Venue Evidence Audit?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Venue Evidence Audit?

As many as you like. As long as a model supports skills, you can use Venue Evidence Audit with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Venue Evidence Audit AI skill free?

Yes. It is published on GitHub by cpt13-g under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇