BD facebook-group-monitor
Monitor Facebook groups for new posts using Playwright browser automation with stealth mode and persistent login session. Scrapes group feed, tracks seen posts, reports only new ones. Captures a single stitched "feed strip" screenshot (viewport scroll + Pillow stitch) for efficient LLM vision analysis — one image covers the full feed. Use when: monitoring Facebook groups, scraping FB posts, checking new group activity, Facebook automation, marketplace monitoring, book sale tracking, competitor group monitoring. Triggers: 'check Facebook group', 'scrape FB posts', 'new posts in group', 'monitor group', 'Facebook marketplace', 'group update'.
Monitor Facebook groups for new posts using Playwright browser automation with stealth mode and persistent login session.
As a process D 38/100 · Unfinished process — References files that are not bundled: scripts/.browser-data/, scripts/.seen-posts.json, scripts/screenshots/
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: scripts/.browser-data/ - warning
missing-refreference to a missing file: scripts/.seen-posts.json - warning
missing-refreference to a missing file: scripts/screenshots/
Process rating: all ten parameters 38/100
- 0Tools and files. 3 referenced file(s) missing: scripts/.browser-data/, scripts/.seen-posts.json, scripts/screenshots/
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 5 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 100Steps. 27 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1544 tokens
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 648: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 27 items
- +4Has examples (10 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +3All 2 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.