AB linkedin-followup
Manage LinkedIn outreach leads from Google Sheets — search by name, read live conversation threads, update status, and send contextual follow-up messages. Use after linkedin-dm to move leads through the pipeline (Sent → Replied → Call Scheduled → Demo Done → Closed).
Manage LinkedIn outreach leads from Google Sheets — search by name, read live conversation threads, update status, and send contextual follow-up messages.
As a process B 70/100 · Nearly there — weak spots: when it triggers, inputs and preconditions
How to improve
- 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 · 6
✓ No critical or high findings
Medium and low: 6
-
low Secrets in code
secret-high-entropy-tokenreferences/sheet-schema.md:4High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)ID: `1eEZ…khM`
quoted -
low Secrets in code
secret-high-entropy-tokenreferences/sheet-schema.md:36High-entropy token-like string (may be an id, hash or a credential)gog sheets update 1eEZ…khM "Sheet1!M1:P1" \
-
low Secrets in code
secret-high-entropy-tokenreferences/sheet-schema.md:64High-entropy token-like string (may be an id, hash or a credential)gog sheets get 1eEZ…khM "Sheet1!A:P" --json
-
low Secrets in code
secret-high-entropy-tokenreferences/sheet-schema.md:76High-entropy token-like string (may be an id, hash or a credential)gog sheets update 1eEZ…khM "Sheet1!J5" \
-
low Secrets in code
secret-high-entropy-tokenreferences/sheet-schema.md:82High-entropy token-like string (may be an id, hash or a credential)gog sheets update 1eEZ…khM "Sheet1!J5:P5" \
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:25High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)1. **Sheet ID** — Confirm the CRM sheet ID (from `linkedin-dm` setup). Default: `1eEZ…khM`, tab: `Sheet1` (or `Outreach` if renamed).
quoted
Files scanned: 3. 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 70/100
- 20When it triggers. No condition that starts the skill
- 30Inputs and preconditions. Does not say what the process needs to start
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 45 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2339 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
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)
- -42 reference files, but SKILL.md never points to them: the model will not open them
- +1No license
- +2Single-language instructions
- +3Description length 267: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 45 items
- +3Output format is stated explicitly
- +4Has examples (11 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.