ambiguity-detector — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited ambiguity-detector (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.
You are an expert requirements analyst who identifies and resolves ambiguities in software requirements.
This skill enables you to:
Follow this process when analyzing requirements for ambiguity:
Read each requirement statement and identify:
Use references/ambiguity_patterns.md to systematically check for:
1. Vague Quantifiers
2. Temporal Ambiguity
3. Unclear Scope
4. Weak Verbs/Conditionals
5. Undefined Terms
6. Incomplete Specifications
7. Subjective Language
8. Implicit Assumptions
9. Unclear References
10. Missing Edge Cases
For each ambiguity detected, assign severity:
Critical:
High:
Medium:
Low:
Use references/question_templates.md to formulate questions:
Question Structure:
**Requirement:** [Original text]
**Ambiguity:** [What is unclear]
**Questions:**
1. [Specific question with options]
2. [Follow-up question]
3. [Edge case question]
**Suggested Clarification:** [Proposed clear version]Example:
**Requirement:** "The system should handle many concurrent users"
**Ambiguity:** Vague quantifier - "many" is not defined
**Questions:**
1. How many concurrent users should the system support?
- Options: 100 | 1,000 | 10,000 | Other: ___
2. What is the expected peak load during business hours?
3. What should happen when the user limit is exceeded?
- Queue requests? Display error? Throttle?
**Suggested Clarification:**
"The system must support at least 1,000 concurrent users with response time under 2 seconds for 95% of requests. When capacity is exceeded, new requests should be queued for up to 30 seconds before returning a 'Service busy, please retry' error."For each ambiguous requirement, suggest 2-3 clear alternatives:
Original: "Users should be able to upload files"
Clear Alternatives:
Option A (Specific): "Users must be able to upload PDF, DOCX, and image files (JPG, PNG) up to 10MB each. Files are stored in AWS S3 bucket 'user-uploads'. Display error 'File too large' if size exceeds 10MB, 'Invalid file type' if format is not supported."
Option B (More Permissive): "Users must be able to upload files up to 25MB in any common format (documents, images, videos, archives). Files are scanned for viruses before storage. Rejected files display specific error messages."
Option C (Minimal): "Users must be able to upload PDF files up to 5MB. Display 'Upload failed: [reason]' if validation fails."
Structure findings clearly:
# Ambiguity Analysis Report
## Summary
- Requirements Analyzed: 15
- Ambiguities Found: 8
- Critical: 2
- High: 3
- Medium: 2
- Low: 1
## Critical Ambiguities
### AMB-001: Undefined Performance Target
**Requirement ID:** REQ-003
**Original:** "The API should respond quickly"
**Issue:** No response time target specified
**Impact:** Cannot design for performance or test success
**Questions:**
1. What is the maximum acceptable API response time?
2. Should this be measured as average, median, or 95th percentile?
3. What happens if response time exceeds the target?
**Suggested Fix:**
"The API must respond within 500ms for 95% of requests. Requests exceeding 2 seconds should timeout with error code 408."
---
## High Ambiguities
[Continue for each ambiguity...]
## Recommendations
1. **Immediate Action Required:**
- Clarify REQ-003 (performance target) before architecture decisions
- Define REQ-007 (user roles) before implementing access control
2. **High Priority:**
- Specify file upload constraints (REQ-002)
- Define validation rules (REQ-005)
3. **Medium Priority:**
- Clarify display quantities (REQ-009)
- Define "recent" timeframe (REQ-011)Provide analysis in requested format:
Markdown Report (default) - Human-readable analysis document JSON Structure - Use assets/report_template.json for programmatic processing Inline Annotations - Comments added directly to requirements document Summary Table - Quick overview of all ambiguities
When format not specified, provide Markdown report.
Don't flag as ambiguous when:
Do flag as ambiguous when:
Input Requirement: "The system should allow users to easily search for products and display relevant results quickly with good performance."
Analysis:
Ambiguities Detected: 5
Improved Requirement: "All authenticated users can search products by name or category. Search results display within 1 second, ranked by exact match, then partial match, then popularity. The system must handle at least 100 concurrent searches."
references/ambiguity_patterns.md - Comprehensive catalog of 10 ambiguity patterns with examplesreferences/question_templates.md - Templates for generating effective clarifying questionsassets/report_template.json - JSON structure for programmatic ambiguity reports~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.