CtrlK
BlogDocsLog inGet started
Tessl Logo

multi-agentic-threat-model

Comprehensive threat modeling for multi-agent systems using CSA MAESTRO 7-layer framework and OWASP Multi-Agentic System Threat Modeling Guide v1.0. Systematically analyzes threats across all architectural layers from foundation models to agent ecosystems.

72

1.61x
Quality

58%

Does it follow best practices?

Impact

97%

1.61x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/ai-security-skills/skills/multi-agentic-threat-model/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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.

The content is well-structured and concise for an instruction-only skill, but actionability and workflow clarity suffer from underspecified methodology, no validation checkpoints, and a missing referenced template.

Suggestions

Provide the `templates/finding.md` file (or inline its finding format) so the required output format is actually available.

Add concrete guidance on how to identify threats per layer (e.g., a per-layer threat checklist or example attack-chain walkthrough) rather than only naming categories.

Insert a validation/prioritization checkpoint in the workflow (e.g., confirm each layer was assessed, then score likelihood/impact before producing the prioritization matrix).

DimensionReasoningScore

Conciseness

The body is lean and structured (layer list, 6 steps, output, references) without explaining concepts Claude already knows; only minor padding in the extended-threats enumeration.

4 / 5

Actionability

Named threat categories and architecture patterns give some concrete guidance, but the 'how' of identifying threats is underspecified and the referenced `templates/finding.md` template is absent, leaving key details missing.

3 / 5

Workflow Clarity

A clear 6-step sequence is present, but there are no validation/checkpoint steps (e.g., completeness or prioritization verification), so checkpoints remain implicit.

3 / 5

Progressive Disclosure

Sections are reasonably organized (Steps / Output / References), but all content is inlined in SKILL.md and the one referenced path (`templates/finding.md`) does not exist in the bundle, so navigation is incomplete.

3 / 5

Total

13

/

20

Passed

Description

58%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.

The description clearly communicates a specialized niche (multi-agent threat modeling via MAESTRO/OWASP) with concrete framing, but lacks an explicit 'Use when...' trigger clause and has limited trigger-term variety.

Suggestions

Add an explicit 'Use when...' clause stating when Claude should invoke this skill (e.g., when the user asks to threat-model a multi-agent or agentic system).

Broaden trigger terms with natural synonyms users might say (e.g., 'agentic AI security', 'agent system risk assessment', 'MAESTRO analysis').

Tighten the action list to multiple distinct concrete actions (map layers, identify threats, prioritize risks) to push specificity toward 5.

DimensionReasoningScore

Specificity

Names the domain and concrete actions ('Systematically analyzes threats across all architectural layers from foundation models to agent ecosystems') plus a specific framework (CSA MAESTRO 7-layer, OWASP Guide v1.0), with only minor coverage gaps.

4 / 5

Completeness

The 'what' is clearly stated (comprehensive threat modeling using MAESTRO/OWASP), but there is no 'when'/'Use when' clause, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

'threat modeling' and 'multi-agent systems' are relevant natural terms, but common synonyms and phrasings users might say are missing and no explicit trigger phrase is provided.

3 / 5

Distinctiveness Conflict Risk

'Multi-agent threat modeling using CSA MAESTRO 7-layer' is a clearly defined niche with minimal overlap risk, though it could overlap slightly with general security-review skills.

4 / 5

Total

14

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
OWASP/secure-agent-playbook
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.