airship
Airship integration. Manage data, records, and automate workflows. Use when the user wants to interact with Airship data.
53
60%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./skills/airship/SKILL.mdLow
Low-risk findings.
2 low severity findings. Worth noting, but not necessarily harmful.
W011: Third-party content exposure detected (indirect prompt injection risk).
What this means
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Why it was flagged
The skill instructs the agent to poll Membrane/Airship connections and act on returned clientAction objects (including clientAction.agentInstructions) and permits proxying arbitrary Airship API responses via membrane request, meaning it ingests third-party content that the agent is expected to read and that can change its actions (see the "Wait for the connection to be ready" and "Proxy requests" sections).
W012: Unverifiable external dependency detected (runtime URL that controls agent).
What this means
The skill fetches instructions or code from an external URL at runtime, and the fetched content directly controls the agent’s prompts or executes code. This dynamic dependency allows the external source to modify the agent’s behavior without any changes to the skill itself.
Why it was flagged
The skill calls Membrane at runtime (e.g., `membrane connection ensure "https://www.airship.com/"`) and the returned JSON may include `clientAction.agentInstructions`, meaning remote content fetched during runtime can supply instructions that directly control the agent.
- Repository
- membranedev/application-skills
- Commit
f484c82
- Audited
- Security analysis
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.