AF smart-linkedin-inbox
LinkedIn inbox manager and conversation assistant powered by Linxa. Use this skill whenever the user mentions LinkedIn messages, LinkedIn inbox, LinkedIn conversations, LinkedIn DMs, or wants to read, search, filter, or manage their LinkedIn messaging. Trigger when the user asks "who messaged me on LinkedIn", "show my LinkedIn inbox", "find conversations about hiring", "list hot leads", "what are my next actions on LinkedIn", "mark conversation as read", or asks about LinkedIn message sentiment, labels, intent, or lead management. This skill supports: listing and searching conversations with rich filters (labels, sentiment, intent direction, product interest), fetching full message threads, generating next-action summaries for leads, adding CRM-style comments to contacts, and marking conversations as read. Also trigger when the user mentions Linxa. Always use this skill for any LinkedIn messaging or LinkedIn lead management task.
LinkedIn inbox manager and conversation assistant powered by Linxa.
As a process F 55/100 · Will not run — References files that are not bundled: references/openapi.yaml
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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/openapi.yaml
Process rating: all ten parameters 55/100
- 0Tools and files. 1 referenced file(s) missing: references/openapi.yaml
- 0Progress reporting. Says nothing while it works
- 30Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 1 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 100Steps. 26 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1737 tokens
- low 11 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 943: 120–800 characters recommended
- +1No license
- +2Single-language instructions
- +5Description quotes 6 example trigger phrases
- +4Structure: 18 headings
- +3Step-by-step instructions: 26 items
- +3Output format is stated explicitly
- +4Has examples (14 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.