CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dogfood

Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A deliberately minimal router skill that delegates volatile details to the CLI's own help output, which keeps it lean and current. It provides concrete commands and a clear sequenced loop with setup validation, with only minor gaps in mid-loop checkpoints and slight phrasing redundancy.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, but the 'stop and tell the user to ... or approve an exact-version npm command' instruction repeats nearly verbatim, and the time-sensitive version pin ('agent-device >= 0.14.0') sits in the main flow rather than a deprecated/old-patterns section. This is efficient with minor trims possible, not the every-token-earns-its-place top anchor.

4 / 5

Actionability

Provides copy-paste-ready commands ('agent-device --version', 'agent-device help dogfood') and a concrete loop with subcommands ('snapshot -i + screenshot', 'close --shutdown'). It is not 5 because evidence-capture specifics and report shape are deferred entirely to external help output, leaving minor gaps.

4 / 5

Workflow Clarity

The sequence (version gate -> read help -> open/snapshot/explore/capture/close) is clear, with an explicit setup validation checkpoint and failure feedback ('If that fails, stop and tell the user...') plus conditional shutdown handling. It falls short of 5 because the exploration loop itself lacks mid-loop validation checkpoints or error-recovery guidance.

4 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external reference files (none exist in the bundle), and is organized into clear topical paragraphs. Its single delegation to 'agent-device help dogfood' is a clearly signaled, one-level-deep reference, which satisfies the simple-skill exception for a top score.

5 / 5

Total

17

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that clearly states what the skill does and when to use it, with natural trigger terms and a well-defined mobile QA niche. The main weaknesses are a vague tail ('other problems'), a few missing trigger synonyms, and slightly generic action verbs.

DimensionReasoningScore

Specificity

The description names the domain ('a mobile app on iOS/Android with agent-device') and several actions ('explore and test', 'find bugs, UX issues'), matching the anchor for several specific actions with minor gaps. It is not 3 because it goes beyond 1-2 concrete actions, and not 5 because 'explore and test' is generic and 'other problems' is vague padding.

4 / 5

Completeness

It explicitly answers both 'what' ('Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues') and 'when' ('Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile') with concrete trigger phrases, matching the top anchor exactly.

5 / 5

Trigger Term Quality

Triggers ('dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile') are natural user phrasings with good coverage of the domain. It falls short of 5 because common synonyms like 'dogfooding', 'quality assurance', or 'beta test' are missing.

4 / 5

Distinctiveness Conflict Risk

The niche (mobile exploratory QA with agent-device) is clear, but the unqualified triggers 'QA' and 'find issues' could overlap with general testing or code-QA skills. This is mostly distinct with minor overlap risk rather than the minimal-conflict top anchor.

4 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository

callstack/agent-device

Path

skills/dogfood/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.