@fprad0/skill-master-mcp 0.0.9 → 0.0.11

package/docs/skill-candidates/v0.0.10/skill-master-orchestrator/references/activation-policy.md

@@ -0,0 +1,77 @@
+# Politica de Ativacao
+
+Use esta referencia quando houver duvida se o Skill Master deve participar do prompt.
+
+## Modos
+
+### Manual
+
+Ativar apenas quando o usuario mencionar:
+
+- `skill-master`
+- `skill_master`
+- `skill-master-mcp`
+- "use o skill master"
+- "use o skill_master"
+
+### Balanced
+
+Modo recomendado. Ativar por mencao direta e por tarefas tecnicas onde uma skill aprovada provavelmente reduz risco ou aumenta qualidade.
+
+Ativar em pedidos como:
+
+- criar, revisar, instalar ou aprovar skill;
+- melhorar o MCP;
+- pesquisar na web e implementar;
+- atualizar Notion com continuidade tecnica;
+- validar pacote npm, launcher, menu ou release;
+- gerar prompt task executavel;
+- aprender com implementacao que funcionou;
+- organizar skills para estudo;
+- preparar aprovacao humana;
+- revisar seguranca ou governanca de IA.
+
+Nao ativar em tarefas triviais:
+
+- traducao curta;
+- pergunta casual;
+- resumo pequeno sem contexto tecnico;
+- horario/data simples;
+- ajuste de uma frase;
+- resposta que nao exige repo, ferramenta ou skill.
+
+### Always-on-assisted
+
+Avaliar quase todo prompt tecnico, mas retornar `no-op` quando nao houver ganho claro.
+
+Regras:
+
+- Recomendar skill quando houver beneficio concreto.
+- Nao acionar fluxo pesado para tarefa simples.
+- Bloquear publicacao sem autorizacao.
+- Sugerir aprendizado quando houver evidencia de sucesso.
+- Pedir avaliacao se a decisao for ambigua ou arriscada.
+
+## Heuristica de decisao
+
+Perguntar internamente:
+
+1. Existe skill local/global aprovada que ajudaria?
+2. O pedido envolve continuidade, validacao, Notion, release ou aprendizado?
+3. Ha risco que exige politica de aprovacao?
+4. A tarefa e complexa o bastante para justificar orquestracao?
+5. Se nao acionar, aumenta a chance de erro ou retrabalho?
+
+Se duas ou mais respostas forem "sim", ativar no modo `balanced`.
+
+## Saida esperada do roteamento
+
+Quando usar `skill_master_activation_check` ou futura `skill_master_prompt_router`, buscar uma resposta com:
+
+- deve ativar ou nao;
+- motivo;
+- skills recomendadas;
+- riscos;
+- proxima acao;
+- se Notion precisa ser atualizado;
+- se ha oportunidade de aprendizado.

package/docs/skill-candidates/v0.0.10/skill-master-orchestrator/references/human-approval-policy.md

@@ -0,0 +1,83 @@
+# Politica de Aprovacao Humana
+
+Use esta referencia quando uma implementacao, fonte externa ou aprendizado puder virar skill ativa.
+
+## Estados
+
+- `study`: material util para estudar, mas ainda nao e skill.
+- `candidate`: skill candidata gerada a partir de evidencia.
+- `pending_approval`: aguardando revisao humana.
+- `approved_local`: aprovada para o projeto atual.
+- `approved_global`: aprovada para o computador do usuario.
+- `rejected`: rejeitada, mas mantida em historico.
+- `blocked`: bloqueada por risco, segredo, licenca, duplicidade ou falta de evidencia.
+
+## Evidencia minima
+
+Uma skill candidata precisa ter:
+
+- problema resolvido;
+- contexto de uso;
+- evidencias de sucesso;
+- comandos ou validacoes executadas;
+- arquivos ou artefatos relevantes;
+- limites de uso;
+- riscos conhecidos;
+- exemplos de prompts;
+- origem e link quando vier de fonte externa.
+
+## Bloqueios automaticos
+
+Bloquear se:
+
+- contiver token, senha, cookie, chave, `.env` ou segredo;
+- vier da web sem revisao local;
+- nao tiver evidencia de funcionamento;
+- tiver comandos destrutivos sem protecao;
+- duplicar skill existente sem justificativa;
+- tiver licenca/proveniencia incerta para redistribuicao;
+- tentar publicar release ou pacote sem autorizacao.
+
+## Aprovacao local
+
+Usar quando a skill e especifica do repositorio ou projeto.
+
+Destino preferencial:
+
+```text
+.codex/skills/<nome-da-skill>/
+```
+
+Requisitos:
+
+- validacao da skill passa;
+- usuario aprova a ativacao local;
+- registrar no Notion se fizer parte da continuidade do Skill Master.
+
+## Aprovacao global
+
+Usar somente quando a skill e reutilizavel em varios projetos do usuario.
+
+Destino:
+
+```text
+${CODEX_HOME:-~/.codex}/skills/<nome-da-skill>/
+```
+
+Requisitos:
+
+- usuario pedir ou aprovar explicitamente skill global;
+- validar formato;
+- checar duplicidade;
+- registrar origem e decisao.
+
+## Decisao final
+
+Antes de ativar, responder:
+
+- o que a skill faz;
+- por que merece aprovacao;
+- onde sera instalada;
+- quais riscos foram revisados;
+- quais testes passaram;
+- se sera local ou global.

package/docs/skill-candidates/v0.0.10/skill-master-orchestrator/references/persona-dev-senior-master.md

@@ -0,0 +1,46 @@
+# Persona - Dev Senior Master
+
+Use esta referencia quando o pedido envolver programacao, arquitetura, MCP, CLI, Notion, testes, release, automacao, seguranca, pesquisa tecnica ou engenharia de IA.
+
+## Identidade
+
+Atuar como `Dev Senior Master`: desenvolvedor senior master, engenheiro senior master e arquiteto pragmatico.
+
+## Postura
+
+- Ler o contexto real antes de concluir.
+- Preferir solucao simples, segura, validavel e mantivel.
+- Explicar decisoes tecnicas por causa e efeito.
+- Separar hipotese de evidencia.
+- Nao confundir plano com entrega.
+- Nao publicar nada para todos sem autorizacao direta.
+- Proteger o trabalho do usuario e preservar alteracoes existentes.
+- Usar Notion como ledger quando a tarefa fizer parte da continuidade do Skill Master.
+
+## Processo
+
+1. Entender o objetivo operacional.
+2. Verificar o estado real do repositorio, ferramenta, autenticacao ou documento.
+3. Usar `skill_master` para recomendar skills quando estiver disponivel.
+4. Planejar somente o suficiente para executar com seguranca.
+5. Implementar com mudancas pequenas e rastreaveis.
+6. Validar com comandos reais.
+7. Registrar o resultado e os proximos passos.
+
+## Padrao de qualidade
+
+- Codigo deve ter testes ou validacao equivalente.
+- Documentacao deve ajudar execucao futura, nao apenas descrever historia.
+- Prompts devem ser contratos executaveis, com objetivo, escopo, restricoes, comandos e Definition of Done.
+- Skills devem ser concisas, com metadados fortes e referencias sob demanda.
+- Releases devem ter autorizacao, changelog e smoke de instalacao.
+
+## Limites
+
+Pedir aprovacao ou bloquear quando:
+
+- a acao publica pacote, cria tag, altera workflow ou afeta todos os usuarios;
+- ha risco de apagar dados, sobrescrever skill ou expor segredo;
+- a fonte e web/externa e ainda nao foi revisada;
+- a execucao depende de credencial que nao pode ser inferida;
+- a validacao necessaria nao pode ser feita no ambiente atual.

package/docs/skill-candidates/v0.0.10/terminal-menu-operations/SKILL.md

@@ -0,0 +1,30 @@
+---
+name: terminal-menu-operations
+description: "Design, test and harden terminal menus and CLI operator workflows. Use when improving menu actions, TTY/non-TTY behavior, prompts, confirmations, disabled actions, help text, status panels, dry-runs, diagnostics, and user-facing command reliability."
+---
+
+# Terminal Menu Operations
+
+Use this skill when a task is about making a terminal menu reliable for humans and automation.
+
+## Workflow
+
+- Separate interactive TTY flows from non-interactive `--run` flows.
+- Show the selected action, expected result and risk before execution.
+- Disable actions that cannot work in the current installation context.
+- Provide a safe diagnostic action that does not mutate configuration.
+- Ensure every mutating action has either confirmation or a documented `--yes` path.
+- Test help, status, direct action mode and at least one failure path.
+
+## Menu Quality Bar
+
+- A user must understand what will happen before pressing Enter.
+- A failed action must explain whether the problem is missing files, missing auth, missing PATH or unsupported context.
+- Repo-only development actions must not appear as runnable in a global npm package.
+- Bootstrap actions must be idempotent.
+
+## Guardrails
+
+- Do not run package publication from a menu unless the user explicitly authorizes release.
+- Do not execute destructive shell commands from menu shortcuts.
+- Do not hide external requirements like client restart, OTP, npm auth or GitHub auth.

package/docs/skill-candidates/v0.0.10/terminal-pixel-art-tui/SKILL.md

@@ -0,0 +1,43 @@
+---
+name: terminal-pixel-art-tui
+description: "Design and harden terminal UIs with low-flicker rendering, alternate-screen lifecycle, raw keyboard input, ANSI frame control, pixel-art panels, and visual smoke tests. Use when improving CLI menus, dashboards, animated terminal graphics, or TTY user experience."
+---
+
+# Terminal Pixel Art TUI
+
+Use this skill when a terminal interface needs to feel graphical, stable and operator-safe.
+
+## Workflow
+
+- Keep TTY and non-TTY paths separate; do not break `--run`, `--status` or automation.
+- Avoid clearing the full screen on every animation frame.
+- Prefer alternate screen for visual menus, then restore the normal screen before command output.
+- Hide the cursor only while the visual frame is active, and always restore it in `finally`.
+- Write frames from a stable cursor origin and clear only the unused tail.
+- Use synchronized-output escape sequences when safe; unsupported terminals should ignore them.
+- Slow animation enough to feel intentional, usually 200ms to 300ms per frame for menus.
+- Build pixel art from deterministic cells, not random noise.
+- Show selected action, expected result and risk before execution.
+- Validate with focused unit tests, full check, non-interactive commands and one real TTY open/exit smoke.
+
+## Pixel Art Guidelines
+
+- Use dense block characters only when the user or product goal requires a graphical terminal look.
+- Keep contrast subtle; prefer two or three accent colors over a rainbow.
+- Make shapes recognizable at small widths before adding animation.
+- Keep animations predictable so they do not distract from the selected action.
+- Test short terminals; the selected item must stay visible.
+
+## Guardrails
+
+- Do not add heavy TUI dependencies unless the current renderer cannot meet the requirement.
+- Do not print raw escape sequences in non-TTY mode.
+- Do not leave the terminal in raw mode, hidden cursor mode or alternate screen after exit.
+- Do not publish the improved package without explicit user authorization.
+
+## Evidence Required
+
+- File or renderer changed.
+- Why flicker was reduced.
+- Screenshot, static frame, or TTY smoke evidence.
+- Commands run and results.

package/docs/skill-candidates/v0.0.10/webapp-testing/LICENSE.txt

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Anthropic, PBC.
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/docs/skill-candidates/v0.0.10/webapp-testing/SKILL.md

@@ -0,0 +1,96 @@
+---
+name: webapp-testing
+description: Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
+license: Complete terms in LICENSE.txt
+---
+
+# Web Application Testing
+
+To test local web applications, write native Python Playwright scripts.
+
+**Helper Scripts Available**:
+- `scripts/with_server.py` - Manages server lifecycle (supports multiple servers)
+
+**Always run scripts with `--help` first** to see usage. DO NOT read the source until you try running the script first and find that a customized solution is abslutely necessary. These scripts can be very large and thus pollute your context window. They exist to be called directly as black-box scripts rather than ingested into your context window.
+
+## Decision Tree: Choosing Your Approach
+
+```
+User task → Is it static HTML?
+    ├─ Yes → Read HTML file directly to identify selectors
+    │         ├─ Success → Write Playwright script using selectors
+    │         └─ Fails/Incomplete → Treat as dynamic (below)
+    │
+    └─ No (dynamic webapp) → Is the server already running?
+        ├─ No → Run: python scripts/with_server.py --help
+        │        Then use the helper + write simplified Playwright script
+        │
+        └─ Yes → Reconnaissance-then-action:
+            1. Navigate and wait for networkidle
+            2. Take screenshot or inspect DOM
+            3. Identify selectors from rendered state
+            4. Execute actions with discovered selectors
+```
+
+## Example: Using with_server.py
+
+To start a server, run `--help` first, then use the helper:
+
+**Single server:**
+```bash
+python scripts/with_server.py --server "npm run dev" --port 5173 -- python your_automation.py
+```
+
+**Multiple servers (e.g., backend + frontend):**
+```bash
+python scripts/with_server.py \
+  --server "cd backend && python server.py" --port 3000 \
+  --server "cd frontend && npm run dev" --port 5173 \
+  -- python your_automation.py
+```
+
+To create an automation script, include only Playwright logic (servers are managed automatically):
+```python
+from playwright.sync_api import sync_playwright
+
+with sync_playwright() as p:
+    browser = p.chromium.launch(headless=True) # Always launch chromium in headless mode
+    page = browser.new_page()
+    page.goto('http://localhost:5173') # Server already running and ready
+    page.wait_for_load_state('networkidle') # CRITICAL: Wait for JS to execute
+    # ... your automation logic
+    browser.close()
+```
+
+## Reconnaissance-Then-Action Pattern
+
+1. **Inspect rendered DOM**:
+   ```python
+   page.screenshot(path='/tmp/inspect.png', full_page=True)
+   content = page.content()
+   page.locator('button').all()
+   ```
+
+2. **Identify selectors** from inspection results
+
+3. **Execute actions** using discovered selectors
+
+## Common Pitfall
+
+❌ **Don't** inspect the DOM before waiting for `networkidle` on dynamic apps
+✅ **Do** wait for `page.wait_for_load_state('networkidle')` before inspection
+
+## Best Practices
+
+- **Use bundled scripts as black boxes** - To accomplish a task, consider whether one of the scripts available in `scripts/` can help. These scripts handle common, complex workflows reliably without cluttering the context window. Use `--help` to see usage, then invoke directly. 
+- Use `sync_playwright()` for synchronous scripts
+- Always close the browser when done
+- Use descriptive selectors: `text=`, `role=`, CSS selectors, or IDs
+- Add appropriate waits: `page.wait_for_selector()` or `page.wait_for_timeout()`
+
+## Reference Files
+
+- **examples/** - Examples showing common patterns:
+  - `element_discovery.py` - Discovering buttons, links, and inputs on a page
+  - `static_html_automation.py` - Using file:// URLs for local HTML
+  - `console_logging.py` - Capturing console logs during automation

package/docs/skill-candidates/v0.0.10/webapp-testing/examples/console_logging.py

@@ -0,0 +1,35 @@
+from playwright.sync_api import sync_playwright
+
+# Example: Capturing console logs during browser automation
+
+url = 'http://localhost:5173'  # Replace with your URL
+
+console_logs = []
+
+with sync_playwright() as p:
+    browser = p.chromium.launch(headless=True)
+    page = browser.new_page(viewport={'width': 1920, 'height': 1080})
+
+    # Set up console log capture
+    def handle_console_message(msg):
+        console_logs.append(f"[{msg.type}] {msg.text}")
+        print(f"Console: [{msg.type}] {msg.text}")
+
+    page.on("console", handle_console_message)
+
+    # Navigate to page
+    page.goto(url)
+    page.wait_for_load_state('networkidle')
+
+    # Interact with the page (triggers console logs)
+    page.click('text=Dashboard')
+    page.wait_for_timeout(1000)
+
+    browser.close()
+
+# Save console logs to file
+with open('/mnt/user-data/outputs/console.log', 'w') as f:
+    f.write('\n'.join(console_logs))
+
+print(f"\nCaptured {len(console_logs)} console messages")
+print(f"Logs saved to: /mnt/user-data/outputs/console.log")

package/docs/skill-candidates/v0.0.10/webapp-testing/examples/element_discovery.py

@@ -0,0 +1,40 @@
+from playwright.sync_api import sync_playwright
+
+# Example: Discovering buttons and other elements on a page
+
+with sync_playwright() as p:
+    browser = p.chromium.launch(headless=True)
+    page = browser.new_page()
+
+    # Navigate to page and wait for it to fully load
+    page.goto('http://localhost:5173')
+    page.wait_for_load_state('networkidle')
+
+    # Discover all buttons on the page
+    buttons = page.locator('button').all()
+    print(f"Found {len(buttons)} buttons:")
+    for i, button in enumerate(buttons):
+        text = button.inner_text() if button.is_visible() else "[hidden]"
+        print(f"  [{i}] {text}")
+
+    # Discover links
+    links = page.locator('a[href]').all()
+    print(f"\nFound {len(links)} links:")
+    for link in links[:5]:  # Show first 5
+        text = link.inner_text().strip()
+        href = link.get_attribute('href')
+        print(f"  - {text} -> {href}")
+
+    # Discover input fields
+    inputs = page.locator('input, textarea, select').all()
+    print(f"\nFound {len(inputs)} input fields:")
+    for input_elem in inputs:
+        name = input_elem.get_attribute('name') or input_elem.get_attribute('id') or "[unnamed]"
+        input_type = input_elem.get_attribute('type') or 'text'
+        print(f"  - {name} ({input_type})")
+
+    # Take screenshot for visual reference
+    page.screenshot(path='/tmp/page_discovery.png', full_page=True)
+    print("\nScreenshot saved to /tmp/page_discovery.png")
+
+    browser.close()