scrutiny

Review executive content for vague claims and missing specifics.

3|2|Updated Jan 30, 2026

Search Tags:#content review #clarity #reporting #executive communication #precision #specificity

Ready to run

npx skills add https://github.com/jamesgiroux/daily-operating-system --skill scrutiny

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: scrutiny
Source: https://github.com/jamesgiroux/daily-operating-system/tree/main/plugins/dailyos-writer/skills/scrutiny
Command: npx skills add https://github.com/jamesgiroux/daily-operating-system --skill scrutiny

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the critical issue of vague or imprecise language in executive-facing content, ensuring clarity, credibility, and actionable communication.

Core Features & Use Cases

Identify Vagueness: Flags ambiguous capability claims, missing timelines, unquantified impacts, and hand-wavy resource statements.
Demand Specificity: Prompts for concrete details, data, and ownership to strengthen content.
Use Case: Reviewing a VP-level presentation, this skill would flag statements like "improved performance" and prompt for specific metrics (e.g., "By what percentage? Which metrics?").

Quick Start

Use the scrutiny skill to review the attached executive briefing document for vague statements and suggest specific improvements.

Frequently Asked Questions about scrutiny

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

FAQPage Schema

How do I review executive content to eliminate vague capability claims and missing timelines?▼

Review executive content by analyzing text against executive skepticism, flagging ambiguous capability claims, unquantified impacts, and missing timelines to demand specific data, named resources, and clear ownership for credible communication.

What is content precision review and when do I need it for executive communication?▼

Content precision review is the process of enforcing specificity in executive-facing content by eliminating hand-wavy resource statements and prompting for concrete metrics. You need it when preparing VP-level presentations or briefings requiring actionable communication.

How do I flag unquantified impact statements in an executive briefing document?▼

Flag unquantified impact statements by scanning executive briefing documents for vague phrases like improved performance, then prompting for concrete details such as specific percentages, named metrics, and clear resource allocation to strengthen credibility.

Can I integrate workspace data to suggest concrete metrics for executive reporting?▼

Yes, you can integrate with DailyOS workspace data to provide concrete metric suggestions during content review, ensuring executive-facing reporting contains specific data, named resources, and clear ownership instead of vague generalizations.

Does this approach work for reviewing resource allocation and ownership in VP-level presentations?▼

Yes, reviewing resource allocation and ownership in VP-level presentations is a core use case, demanding specific data and named resources to ensure credibility and actionable communication for executive audiences.

What is the best way to demand precision and specificity in executive-facing content?▼

The best way to demand precision is to analyze content against executive skepticism, automatically identifying vagueness in capability claims and timelines, then requiring specific data and clear ownership to ensure actionable communication.