linear-multiworkspace
Linear Multiworkspace integration via Apideck's Issue Tracking unified API — same methods work across every connector in Issue Tracking, switch by changing `serviceId`. Use when the user wants to read, write, or comment on tickets and issues in Linear Multiworkspace. Routes through Apideck with serviceId "linear-multiworkspace".
71
66%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./connectors/linear-multiworkspace/SKILL.mdSecurity
1 medium severity finding. This skill can be installed but you should review these findings before use.
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
Third-party content exposure detected (high risk: 0.80). The skill's SKILL.md instructs the agent to call Apideck's Issue Tracking API (e.g., apideck.issueTracking.tickets.list with serviceId "linear-multiworkspace" and the Proxy API to Linear's own endpoints) to fetch and read/write tickets and comments from Linear Multiworkspace—these are user-generated, third‑party contents that the agent will ingest and could influence subsequent actions.
- Repository
- apideck-libraries/api-skills
- Commit
9e04d86
- 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.