BB Openclaw Facebook Marketing
Facebook browser automation skill for posting, reading comments, generating intelligent replies, and tracking comment threads. Designed for brand engagement and high-frequency community operations. 中文：Facebook 浏览器自动化技能，支持发布帖子、抓取评论、智能生成并提交回复，支持评论线程化追踪。面向品牌互动与社群运营的高频维护场景。 日本語：Facebookブラウザ自動化エージェント。投稿、コメント取得、文脈対応返信、スレッド追跡返信を実行し、継続的なコミュニティ運用を支援。 한국어：Facebook 브라우저 자동화 스킬. 게시물 업로드, 댓글 조회, 컨텍스트 기반 답변, 댓글 스레드 추적 자동화를 통해 소셜 운영 효율을 높입니다. Español：Automatización de navegador para Facebook: publica, lee comentarios, genera y envía respuestas inteligentes y continúa en hilos. Diseñado para operación de comunidad y mantenimiento continuo de engagement.
As a process B 67/100 · Nearly there — weak spots: when it triggers, consistency, running it twice
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 67/100
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 2 mutating operations with no state check
- 40Consistency. Frontmatter name (Openclaw Facebook Marketing) differs from the folder (openclaw-mark)
- 60Tools and files. Uses tools (web, node) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 61 steps
- 100Failures and branches. 2 branches, has a failure section
- 100Execution cost. Instruction body is 1402 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 14 top-level sections: this looks like several domains in one skill
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)
- -4Absolute local paths (C:\Users, /home/…): not portable
- +1No license
- +2Single-language instructions
- +3Description length 645: enough signal without eating the budget
- +4Structure: 24 headings
- +3Step-by-step instructions: 61 items
- +3Output format is stated explicitly
- +4Has examples (7 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.