lit-review-council — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited lit-review-council (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
This skill guides you through framing, configuring, and executing a comprehensive literature review using the lit-review-council multi-agent orchestrator.
Whenever a user wants to conduct a literature review using this tool, follow these 3 phases:
Ask the user to describe their high-level research question or context. Help them sharpen it so the agents have a clear North Star.
Break the overarching question down into a logically distinct list of topics.
Each topic requires:
slug: A short, lowercase, hyphenated string (e.g., graph-topology).description: A 1-2 sentence explanation of what the topic explores.search_keywords: A list of 2-4 highly specific search queries (include acronyms, specific methodologies, etc.).rationale: (Optional) A brief explanation of why this topic was chosen.Present this taxonomy to the user for approval.
Once the topics are approved, you can execute the pipeline using one of two methods:
Method A: Using the MCP Tool (Recommended if connected) If the conduct_literature_review MCP tool is available to you, invoke it directly. Pass the research question and the JSON array of topics. Provide an output_dir (e.g., a specific folder in the workspace or an Obsidian vault path). The tool will run synchronously and return the path to the completed OKF bundle.
Method B: Using the CLI (Local script execution) If the MCP tool is not available:
topics.yaml) in the project root. The structure should be: topics:
- slug: "topic-slug"
description: "..."
search_keywords: ["key1", "key2"]
rationale: "..."uv: uv run python main.py --config topics.yaml --output <your-output-dir> --question "<Overarching Research Question>"Once the review completes, do not attempt to read the entire OKF bundle into your context, as it can be very large. Instead, point the user to the generated index.md and offer to explore specific topics if they need a summary.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.