CtrlK
BlogDocsLog inGet started
Tessl Logo

pipecat-friday-agent

Build a low-latency, Iron Man-inspired tactical voice assistant (F.R.I.D.A.Y.) using Pipecat, Gemini, and OpenAI.

58

Quality

68%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/pipecat-friday-agent/SKILL.md

The canonical home for this skill is pipecat-friday-agent in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

75%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.

The skill body is efficient, actionable, and well-structured, with concrete commands and a real executable script referenced one level deep. Scores are held at 4 rather than 5 by a missing referenced test script, a hardcoded device index, and the absence of an explicit run-verification step.

Suggestions

Provide the referenced test_audio_output.py in scripts/ (or remove the reference) so troubleshooting guidance is fully actionable.

Replace the hardcoded OUTPUT_DEVICE with env-driven or auto-detection guidance so the run command works across machines.

Add a brief verification step after Step 3 (e.g. 'Confirm the console prints the F.R.I.D.A.Y. banner and responds to a test utterance') to close the workflow-clarity gap.

DimensionReasoningScore

Conciseness

The body is lean and well-sectioned with copy-paste commands and no padding about basic concepts; minor trim opportunities exist in the slightly redundant 'When to Use' bullets and decorative commentary.

4 / 5

Actionability

It gives concrete, executable install/env/run commands and points to a real complete script, but troubleshooting references a test_audio_output.py that is not in the bundle and OUTPUT_DEVICE is hardcoded, leaving a minor gap.

4 / 5

Workflow Clarity

A clear three-step sequence (install, configure, run) is present and ordered; it lacks an explicit verification checkpoint, but the operation is not destructive or batch so the cap does not apply.

4 / 5

Progressive Disclosure

Content is well-organized into clear sections and the bulk of code is correctly placed one level deep in scripts/friday_agent.py; the only gap is a referenced test_audio_output.py that does not exist in the bundle.

4 / 5

Total

16

/

20

Passed

Description

61%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.

The description is specific and distinct, naming a concrete build target and tech stack, but it omits any explicit "Use when..." trigger guidance, which caps its completeness. Trigger-term coverage is good but lacks synonyms. Adding a use-when clause with natural trigger phrases would raise the score.

Suggestions

Add a 'Use when...' clause with concrete trigger phrases, e.g. 'Use when building a real-time voice assistant with Pipecat, or when integrating Gemini and OpenAI into a voice loop.'

Include natural synonyms such as 'speech agent' or 'conversational voice AI' to broaden trigger-term coverage.

Optionally enumerate 1-2 more concrete actions (e.g. 'orchestrate STT/LLM/TTS stages') to lift specificity above a single action.

DimensionReasoningScore

Specificity

The description states one concrete action ("Build a ... tactical voice assistant") and names the stack ("Pipecat, Gemini, and OpenAI"), but lists only that single action rather than multiple concrete capabilities.

3 / 5

Completeness

It clearly answers the "what" (build a low-latency tactical voice assistant) but includes no "Use when..." trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

"voice assistant" is a natural keyword a user would say, and "Pipecat"/"Gemini"/"OpenAI" are terms a user of those tools would naturally mention, though common synonyms like "speech agent" or "conversational AI" are absent.

4 / 5

Distinctiveness Conflict Risk

The F.R.I.D.A.Y./tactical theme with a specific Pipecat+Gemini+OpenAI stack carves a distinct niche, though it has minor overlap with the general @voice-agents skill.

4 / 5

Total

14

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.