AC resy-fpx
Query and act on Resy (resy.com restaurant reservations) from a shell without running the resy-mcp server — search venues, check slot availability, book/cancel reservations, and manage favorites/Priority Notify with curl against api.resy.com, using the fpx CLI (@fetchproxy/cli) only for the one-time token bootstrap when you have no RESY_EMAIL/RESY_PASSWORD. Use when you want Resy data or actions without the MCP, in a script, or on a machine where the MCP isn't installed.
Query and act on Resy (resy.com restaurant reservations) from a shell without running the resy-mcp server — search venues, check slot availability…
As a process C 53/100 · Has gaps — weak spots: result and completion, 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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Secrets in code
secret-high-entropy-tokenreferences/resy-api.md:7High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)RESY_API_KEY='VbWk…7n5' # public web-app key, see SKILL.md
quoted -
low Secrets in code
secret-labelled-tokenSKILL.md:31Labelled token / key literal (vendor format unknown — verify it is not a live credential) (quoted — discussed, not commanded)-H 'Authorization: ResyAPI api_key="VbWk…7n5"' \
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:31High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)-H 'Authorization: ResyAPI api_key="VbWk…7n5"' \
quoted -
low Secrets in code
secret-password-literalSKILL.md:31Hard-coded password / key literal (may be an example) (quoted — discussed, not commanded)-H 'Authorization: ResyAPI api_key="VbWk…7n5"' \
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:70High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)RESY_API_KEY='VbWk…7n5' # override if Resy rotates it
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 53/100
- 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. 3 mutating operations with no state check
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 100Steps. 10 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1094 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 475: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 10 items
- +4Has examples (4 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.