Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

playwright-explore-website

Étoiles0

Forks0

Mis à jour17 mars 2026 à 10:52

Use when a developer wants to understand what to test on a website before writing tests — when they say 'explore the website', 'what should I test?', 'check what flows exist on this URL', 'analyze the UI for test coverage', or when given a URL and asked to plan browser tests. Uses Playwright MCP to navigate and interact with 3–5 core features, documents UI locators, user interactions, and expected outcomes, then proposes concrete test cases. Auto-loads when website exploration, test planning, UI review, or discovering testable flows is mentioned.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

SriSatyaLokesh

SriSatyaLokesh/kt-parser

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Analystes en assurance qualité des logiciels et testeursProfessions informatiques et mathématiques·SOC 15-1253

SKILL.md

readonly

name

playwright-explore-website

description

Website Exploration for Testing

Your goal is to explore the website and identify key functionalities to test.

Specific Instructions

Navigate to the provided URL using the Playwright MCP Server. If no URL is provided, ask the user to provide one.
Identify and interact with 3-5 core features or user flows.
Document the user interactions, relevant UI elements (and their locators), and the expected outcomes.
Close the browser context upon completion.
Provide a concise summary of your findings.
Propose and generate test cases based on the exploration.

Source: github/awesome-copilot

Plus depuis ce dépôt

même dépôt

acquire-codebase-knowledge

SriSatyaLokesh/kt-parser

Systematically map codebase architecture, stack, and conventions by analyzing docs and code factually. Trigger when user says "acquire codebase knowledge" or "map codebase", "understand codebase", "document codebase". trigger when you dont have infomration about codebase as a primary step to understand codebase.

2026-03-170

agent-activity-logger

SriSatyaLokesh/kt-parser

Background reference skill defining the structured JSON log format written to logs/copilot/agent-activity.log by each phase agent on completion. Auto-loaded by Discuss, Research, Planner, TDD Implementer, and Verify agents when they append their completion log entry. Defines all required fields (timestamp, issueId, phase, agent, developer, status, summary, decisions, outputFile, nextPhase) and optional phase-specific fields (filesChanged for execute, testResults for verify). Also provides jq query examples for filtering logs by Issue, date, or status. Loads when log format, activity log, or agent logging is mentioned.

2026-03-170

doc-reviewer

SriSatyaLokesh/kt-parser

Use when a developer asks to review, audit, check, or critique any documentation file — when they say 'review this doc', 'is this README beginner-friendly?', 'check for markdown errors', 'audit the learn guide', or 'rate this doc'. Brutally reviews .md files for: beginner-friendliness (could a newcomer follow this?), markdown lint errors (broken links, bad code fences, heading hierarchy), missing references, and documentation quality. Outputs a structured report with Critical/Major/Minor issues, a Beginner-Friendliness Score out of 10, and a merge-ready verdict. Never softens feedback. Auto-loads when doc review, README audit, guide critique, markdown lint, or beginner-friendliness check is mentioned.

2026-03-170

documentation-writer

SriSatyaLokesh/kt-parser

Use when a developer needs to create or improve technical documentation — when they say 'write docs for', 'document this API', 'create a tutorial for', 'write a how-to guide', 'add a README', or 'explain this feature in docs'. Applies the Diátaxis framework to classify the document type (Tutorial / How-to / Reference / Explanation), asks clarifying questions about audience and goal, proposes an outline for approval before writing, then produces well-structured Markdown. Stores in the correct project folder (docs/issues/, docs/flows/, docs/apis/, docs/external-apis/). Matches existing project doc style. Auto-loads when documentation, README, API docs, tutorial, guide, or explanation writing is mentioned.

2026-03-170

playwright-automation-fill-in-form

SriSatyaLokesh/kt-parser

Use when a developer needs to automate filling in a web form without submitting it — when they say 'fill in the form at URL', 'automate this form', 'enter these values in the web form', or 'test form input'. Uses Playwright MCP with accessible locators (getByLabel, getByRole, getByPlaceholder). Fills text with fill(), selects dropdowns with selectOption(), handles file uploads with setInputFiles(). ALWAYS stops before submitting — shows a filled-values summary and waits for human review. Auto-loads when form filling, web automation, input testing, or Playwright form interaction is mentioned.

2026-03-170

playwright-generate-test

SriSatyaLokesh/kt-parser

Use when a developer wants to create a Playwright end-to-end or browser test for a specific feature, flow, or scenario — when they say 'write a Playwright test for', 'generate a test for the login flow', 'add e2e tests for', or 'test this UI with Playwright'. Uses Playwright MCP tools to first interact with the real browser (not just guess at selectors), then generates a TypeScript spec using @playwright/test. Saves to tests/ directory with <feature>.spec.ts naming. Iterates until the test passes. Auto-loads when Playwright, e2e, browser test, or UI test is mentioned.

2026-03-170

name

playwright-explore-website

description

Website Exploration for Testing

Your goal is to explore the website and identify key functionalities to test.

Specific Instructions

Navigate to the provided URL using the Playwright MCP Server. If no URL is provided, ask the user to provide one.
Identify and interact with 3-5 core features or user flows.
Document the user interactions, relevant UI elements (and their locators), and the expected outcomes.
Close the browser context upon completion.
Provide a concise summary of your findings.
Propose and generate test cases based on the exploration.

Source: github/awesome-copilot