AC facebook-groups
The Facebook Groups strategy skill -- Groups as Facebook's real organic surface, deeper than what facebook-strategy routes to community-management. Use when someone wants to build/grow/run a Facebook Group, decide Group vs Page, or turn a community into leads. Groups reach 40-50% of members per post vs ~1.5% for Pages; Facebook deliberately favors Groups. Uses the TRIBE framework. Reads brand-profile + goals-and-kpis first. The agent designs the group strategy (niche, setup, content, growth, moderation, value-first monetization) and drafts group posts + the join-funnel content. CRUCIAL: WoopSocial does NOT post to Groups -- it publishes the Page + cross-channel content that funnels people to JOIN; in-group posting, admin, moderation, and Group analytics stay native/human, routed to community-management. No automation/spam or fake members; value-first, never fabricates metrics. Distinct from facebook-strategy (the Page play) and community-management (the engagement routine).
The Facebook Groups strategy skill -- Groups as Facebook's real organic surface, deeper than what facebook-strategy routes to community-management.
As a process C 56/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- 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: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 56/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 7 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 100Tools and files. No external tools needed
- 100Steps. 11 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1663 tokens
- low No test case covers injection arriving through data
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)
- +3Description length 988: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +4Structure: 9 headings
- +3Step-by-step instructions: 11 items
- +4Reference files are cited in the instructions (3 of 4)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.