load-testing
Load test a Databricks App to find its maximum QPS. Use when: (1) User says 'load test', 'benchmark', 'QPS', 'throughput', or 'performance test', (2) User wants to find how many queries per second their app can handle, (3) User wants to set up load testing scripts for their agent, (4) User wants to view load test results/dashboard.
85
81%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Risky
Do not use without reviewing
Security
2 findings — 1 high severity, 1 medium severity. You should review these findings carefully before considering using this skill.
W007: Insecure credential handling detected in skill instructions
What this means
The skill handles credentials insecurely by requiring the agent to include secret values verbatim in its generated output. This exposes credentials in the agent’s context and conversation history, creating a risk of data exfiltration.
Why it was flagged
Insecure credential handling detected (high risk: 0.90). The prompt asks the agent to collect M2M client_id/client_secret from the user and shows examples embedding them directly in CLI flags (and as direct exports), which would require the LLM to handle and potentially emit secret values verbatim in commands—an insecure pattern despite also mentioning env-vars.
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 load-test scripts (locustfile.py and run_load_test.py) explicitly accept arbitrary --app-url endpoints and parse SSE streaming JSON responses from those apps as part of the required workflow (see SKILL.md: "locustfile.py — ... Sends POST /invocations ... Parses SSE stream (data: {json} lines)" and the run CLI that tests each app URL), so untrusted third-party app responses could influence test logic and metrics and enable indirect prompt injection.
- Repository
- databricks/app-templates
- Commit
dfeb4ac
- 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.