feishu-doc-verifier_skill

Overview

This skill verifies that a Feishu document was created successfully and is reachable. It uses Playwright to open the document URL, confirm page load and title, capture a screenshot, and write a structured verification result to output. The skill supports saved login state to run headless after the first interactive login.

How this skill works

The verifier reads document metadata (ID and URL) from the doc_info.json produced by the creator. It launches Playwright with a persistent context: the first run opens a visible browser for QR login and saves the authentication state; subsequent runs reuse the saved state and run headless. The skill navigates to the document URL, checks page title and visible content, takes a screenshot, and writes a verify_result.json with success status, timestamps, and file pointers.

When to use it

• After generating a Feishu document to confirm it was created and is accessible.
• As a CI/automation step to validate document creation in workflow pipelines.
• When debugging permission or access issues for a generated document.
• Periodically to re-validate document availability using saved login state.

Best practices

• Run the verifier interactively once to complete Feishu QR login so state.json is created.
• Keep .claude/playwright_state backed up if you want repeatable headless runs.
• Store outputs (verify_result.json and screenshot) with build artifacts for audits.
• Remove .claude/playwright_state to force a fresh login when credentials expire.
• Provide the exact doc_info.json generated by the creator skill to avoid mismatches.

Example use cases

• A CI job runs the creator skill, then calls this verifier to fail the pipeline if the doc is not accessible.
• A QA engineer verifies a batch of generated documents and collects screenshots for review.
• An automation workflow checks that permission updates allowed external viewers to access the doc.
• A scheduled task re-validates important documentation pages and reports availability.