ncklrs/claude-chrome-user-testing/critical-paths
Claude Code and agent skill by ncklrs/claude-chrome-user-testing
Trust tier 3
- community
Source check pending
Checking that the SKILL.md file is still in the repository.
Install
npx vskill@latest install ncklrs/claude-chrome-user-testing/critical-pathsSKILL.md
Critical Paths Skill
Test must-work user journeys defined in project configuration. Critical paths are essential flows that must always function correctly.
What is a Critical Path?
A critical path is a user journey that:
- Must work for the site/app to be usable
- Represents core business functionality
- Would cause significant harm if broken
- Should be tested before every deployment
Examples of Critical Paths
| Site Type | Critical Paths | |
|---|---|---|
| E-commerce | Purchase flow, Account creation, Cart | |
| SaaS | Signup, Login, Core feature usage | |
| Content | Navigation, Search, Article viewing | |
| Banking | Login, Transfer, Balance check |
Path Definition Schema
Full Schema
Step Actions
navigate
Navigate to a URL path.
task
Perform a task using the persona's behavior.
verify
Verify something exists or is true.
wait
Wait for a condition.
input
Enter specific data into a field.
Execution Logic
Path Execution
Step Execution
Priority Handling
Execution Order
- Critical paths first
- High priority second
- Medium priority third
- Low priority last
Failure Impact
| Priority | On Failure | Report Level | |
|---|---|---|---|
| critical | Major alert | CRITICAL | |
| high | Alert | ERROR | |
| medium | Warning | WARNING | |
| low | Note | INFO |
Report Generation
Data Structure
Report Sections
- Summary: Pass/fail counts
- Results: Each path's outcome
- Failures: Detailed failure information
- Action Required: Prioritized fix list
- Screenshots: Evidence of failures
Integration with CI/CD
Fail-Fast Mode
When --fail-fast is enabled:
- Stop testing after first failure
- Report what was tested so far
- Mark remaining paths as skipped
- Useful for quick validation
Exit Status Interpretation
Template Path Definitions
E-commerce
SaaS Application
Best Practices
- Start small: Define 2-3 critical paths first
- Be specific: Clear step descriptions help the agent
- Match personas: Use personas that would actually do this journey
- Update regularly: Keep paths in sync with features
- Test the tests: Run paths manually to verify they make sense
- Prioritize correctly: Reserve "critical" for truly essential flows
Security
- Security scanPassed, 95 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/critical-paths/SKILL.md
Popularity
- Repository stars
- 20
- Repository forks
- 2
- 7-day trend score
- 15
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/ncklrs/claude-chrome-user-testing/critical-paths)