Fetches e2e-tests-studio from mastra-ai/mastra and configures it for Cursor.
3
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/e2e-tests-studio
Restart Cursor to activate e2e-tests-studio. Access via /e2e-tests-studio in your agent's command palette.
⚠
Security Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
import{ test, expect, Page }from'@playwright/test';import{ resetStorage }from'../__utils__/reset-storage';import{ selectFixture }from'../__utils__/select-fixture';import{ nanoid }from'nanoid';/**
* FEATURE: [Name of feature]
* USER STORY: As a user, I want to [action] so that [outcome]
* BEHAVIOR UNDER TEST: [Specific behavior being validated]
*/test.describe('[Feature Name] - Behavior Tests',()=>{let page: Page; test.beforeEach(async({ browser })=>{const context =await browser.newContext(); page =await context.newPage();}); test.afterEach(async()=>{awaitresetStorage(page);});test('should [verb describing behavior] when [trigger condition]',async()=>{// ARRANGE: Set up preconditions// - Navigate to the feature// - Configure any required state// ACT: Perform the user action that triggers the behavior// ASSERT: Verify the OUTCOME, not the UI state// - Check data persistence// - Verify downstream effects// - Confirm API calls made correctly});});
Behavior Test Patterns
Pattern 1: Configuration Affects Behavior
test('selecting LLM provider should use that provider for agent responses',async()=>{// ARRANGEawait page.goto('/agents/my-agent/chat');// Intercept API to verify providerlet capturedProvider:string|null=null;await page.route('**/api/chat', route =>{const body =JSON.parse(route.request().postData()||'{}'); capturedProvider = body.provider; route.continue();});// ACT: Select a different providerawait page.getByTestId('provider-selector').click();await page.getByRole('option',{ name:'OpenAI'}).click();// Send a message to trigger the agentawait page.getByTestId('chat-input').fill('Hello');await page.getByTestId('send-button').click();// ASSERT: Verify the selected provider was usedawait expect.poll(()=> capturedProvider).toBe('openai');});
Pattern 2: Data Persistence
test('created agent should persist after page reload',async()=>{// ARRANGEawait page.goto('/agents');const agentName =`Test Agent ${nanoid()}`;// ACT: Create new agentawait page.getByTestId('create-agent-button').click();await page.getByTestId('agent-name-input').fill(agentName);await page.getByTestId('save-agent-button').click();// Wait for creation to completeawaitexpect(page.getByText(agentName)).toBeVisible();// ASSERT: Verify persistenceawait page.reload();awaitexpect(page.getByText(agentName)).toBeVisible({ timeout:10000});});
Pattern 3: Tool Execution Produces Correct Output
test('weather tool should return formatted weather data',async()=>{// ARRANGEawaitselectFixture(page,'weather-success');await page.goto('/tools/weather-tool');// ACT: Execute tool with parametersawait page.getByTestId('param-city'
Implementation Guide
Prerequisites
›Claude Desktop or compatible AI client with skill support
›Clear understanding of task or problem to solve
›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Steps
1Install skill using provided installation command
2Test with simple use case relevant to your work
3Evaluate output quality and relevance
4Iterate on prompts to improve results
5Integrate into regular workflow if valuable
Common Pitfalls
⚠Expecting perfect results without iteration
⚠Not providing enough context in prompts
⚠Using skill for tasks outside its intended scope
⚠Accepting outputs without review and validation
Best Practices
✓ Do
+Start with clear, specific prompts
+Provide relevant context and constraints
+Review and refine all outputs before using
+Iterate to improve output quality
+Document successful prompt patterns
✗ Don't
−Don't use without understanding skill limitations
−Don't skip validation of outputs
−Don't share sensitive information in prompts
−Don't expect skill to replace human judgment
💡 Pro Tips
★Be specific about desired format and style
★Ask for multiple options to choose from
★Request explanations to understand reasoning
★Combine AI efficiency with human expertise
When to Use This
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path
1Familiarize yourself with skill capabilities and limitations
2Start with low-risk, non-critical tasks
3Progress to more complex and valuable use cases
4Build expertise through regular use and experimentation
