CtrlK
BlogDocsLog inGet started
Tessl Logo

conflict-analyzer

Identifies and analyzes conflicts in software requirements including logical contradictions, technical incompatibilities, resource constraints, timeline issues, data conflicts, and stakeholder priority mismatches. Use when reviewing requirement sets, specifications, user stories, or project plans to detect conflicts that could block implementation or cause rework. Provides detailed conflict analysis with resolution strategies and impact assessment.

82

1.15x
Quality

73%

Does it follow best practices?

Impact

98%

1.15x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/conflict-analyzer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable analysis workflow with clear sequencing and good reference signaling. Its main weakness is conciseness: large blocks of inlined content duplicate the bundle's reference and asset files, inflating the body unnecessarily.

Suggestions

Conciseness: Replace the ~95-line Step 7 markdown report example with a short structural outline and point readers to assets/conflict_report_template.json, which already contains the full template.

Conciseness: Inline only a one-line summary of each of the 8 conflict types in Step 2 and defer the full enumeration (patterns, examples) to references/conflict_patterns.md instead of duplicating it.

Workflow clarity: Add an explicit validation checkpoint before report generation — e.g., verify each flagged conflict against the "Common Pitfalls to Avoid" list and re-scan transitive pairs before producing the report.

DimensionReasoningScore

Conciseness

Noticeably verbose: the ~95-line full markdown report example in Step 7 largely duplicates assets/conflict_report_template.json, and the 8 conflict types are enumerated inline despite references/conflict_patterns.md already cataloging them.

2 / 5

Actionability

Provides a concrete 7-step workflow, a strategy-selection table mapping conflict type to strategies, and worked resolution examples with pros/cons and effort ratings; minor gaps only (no explicit ID-assignment command).

4 / 5

Workflow Clarity

Steps are clearly sequenced (catalog → detect → matrix → severity → dependencies → resolution → report) with a "Common Pitfalls to Avoid" quality gate, but there is no explicit validation checkpoint confirming flagged conflicts before report generation.

4 / 5

Progressive Disclosure

References are one level deep and well-signaled ("Use references/conflict_patterns.md", a closing Resources section), but substantial content that belongs in those references (full conflict-type enumeration, complete report template) is inlined in SKILL.md.

4 / 5

Total

14

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that clearly states both capability and trigger conditions with concrete natural-language terms. It is comprehensive on completeness and distinctiveness, with only minor specificity gaps (unmentioned report generation) and a few missing synonyms.

DimensionReasoningScore

Specificity

Lists several concrete actions ("Identifies and analyzes conflicts", "Provides detailed conflict analysis with resolution strategies and impact assessment") plus an enumeration of six conflict types, but omits report generation which the body performs, leaving minor coverage gaps.

4 / 5

Completeness

Explicitly answers both what ("Identifies and analyzes conflicts in software requirements...") and when ("Use when reviewing requirement sets, specifications, user stories, or project plans to detect conflicts...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural-term coverage ("requirement sets, specifications, user stories, or project plans") plus concrete conflict keywords, but a few common synonyms (e.g. "requirements conflicts", "spec conflicts") are missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (requirement conflict analysis) with distinct, specific triggers (requirement sets, user stories, project plans) and minimal overlap risk with other skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
ArabelaTso/Skills-4-SE
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.