Back to skill

Security audit

Work Productivity Ontology Typed Workflow Helper

Security checks for vulnerabilities and agentic risk

Overview

The scanners rated this skill benign with high confidence; they reported no security findings, while noting that broad activation keywords may trigger it for unrelated requests.

The scan covered all six listed components and reported complete analysis. Consider whether broad activation terms fit your needs; the verdict is benign, but that does not mean risk-free.

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (5)

Generic trigger keywords allow activation for requests unrelated to ontology workflows.

Medium
Category
Trigger Abuse
Confidence
99% confidence
Finding

The trigger list includes everyday terms such as creating, memory, structured, and bug fix without requiring an ontology-related context. The broad activation description on line 4 reinforces this scope, and no exclusion conditions prevent unintended invocation for unrelated writing, debugging, or memory questions.

Content

No source excerpt is available for this finding.

Generic trigger keywords can activate the skill for unrelated requests.

Medium
Category
Trigger Abuse
Confidence
99% confidence
Finding

The trigger list includes broad terms such as creating, memory, typed, and bug fix without requiring an ontology-workflow context. These terms occur in many unrelated requests, and the skill provides no exclusion conditions to prevent unintended activation.

Content

No source excerpt is available for this finding.

Activation keywords include broad terms without ontology-specific scope constraints.

Low
Category
Trigger Abuse
Confidence
93% confidence
Finding

The usage keywords include generic terms such as creating, memory, and bug fix, which overlap with many unrelated requests. The file does not specify that these keywords must occur in an ontology-workflow context or provide exclusion conditions, leaving activation scope ambiguous despite the more specific trigger sentences.

Content

No source excerpt is available for this finding.

The usage keywords include broad terms without limiting activation to ontology workflows.

Low
Category
Trigger Abuse
Confidence
90% confidence
Finding

Keywords such as creating, memory, structured, and bug fix occur in many requests unrelated to ontology-based workflows. Although specific example trigger sentences follow, the file does not clarify whether these broad keywords independently activate the skill or require an ontology-specific context.

Content

No source excerpt is available for this finding.

Implicit invocation is enabled, but the description does not define a clear activation scope.

Low
Category
Trigger Abuse
Confidence
88% confidence
Finding

The short description is a truncated statement about user demand rather than a description of supported tasks. Although the default prompt mentions ontology-style workflows on Clawhub, its generic references to fixing bugs and hardening leave unclear which requests should implicitly activate this skill.

Content

No source excerpt is available for this finding.