CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pipecat-friday-agent

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

Quality

73%

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 ./skills/pipecat-friday-agent/SKILL.md
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.

A well-organized, actionable body with a clear three-step workflow, real bundle integration, and effective troubleshooting. Its main weaknesses are the missing explicit validation checkpoint in the run workflow, a dangling reference to a non-bundled test_audio_output.py script, and slight redundancy between the Overview, 'When to Use', and frontmatter.

Suggestions

Add an explicit validation step after launching (e.g. confirm the mic/speaker devices initialize and a first transcript round-trips) so the run workflow has a checkpoint.

Ship or inline the device-index discovery logic currently attributed to the missing test_audio_output.py, or remove the reference to the non-bundled script.

Trim the 'Core Concepts' explanations that restate what the script itself documents, and drop redundant restatement of the frontmatter description in the Overview.

DimensionReasoningScore

Conciseness

Sections are tight and command-driven with no padding of known concepts, but there is minor over-explanation ('This allows for granular control over each stage, unlike end-to-end speech-to-speech models') and the Overview/'When to Use' sections slightly restate the frontmatter, matching anchor 4 rather than the lean anchor 5.

4 / 5

Actionability

Concrete, executable guidance throughout: a copy-paste 'pip install pipecat-ai[openai,google,silero]', a specific .env block, and 'python scripts/friday_agent.py' which is a real bundled script. Minor gaps keep it below anchor 5: the referenced 'test_audio_output.py' is not in the bundle, and device-index discovery is left to the user.

4 / 5

Workflow Clarity

The install → configure → run sequence is clearly ordered and executable, and the Troubleshooting section provides error recovery for the two main failure modes. It falls short of anchor 5 because there are no explicit validation checkpoints (e.g. verifying the pipeline starts or keys load) before or after running.

4 / 5

Progressive Disclosure

The body works as an overview with a well-signaled, one-level-deep reference to the real bundle file scripts/friday_agent.py, and the heavy implementation (the Google compatibility shim) is appropriately delegated to it. Minor gaps: 'test_audio_output.py' is referenced but absent from the bundle, and the 'Related Skills' pointers are not part of it, so structure is good but not flawless (anchor 4, not 5).

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.

A specific, distinct description with a clear 'what' and good technical keywords, weakened by the complete absence of a 'when to use' clause and limited action coverage beyond a single 'Build' verb. Adding an explicit trigger clause with natural synonyms ('voice agent', 'real-time voice') would lift it substantially.

Suggestions

Add an explicit trigger clause, e.g. 'Use when building real-time voice agents, speech-to-speech pipelines, or Pipecat-based voice applications.'

Include natural synonyms and variations such as 'voice agent', 'real-time voice', 'STT/TTS', or 'speech-to-speech' alongside the existing keywords.

List the concrete actions involved (orchestrate the STT/LLM/TTS pipeline, bridge Gemini to Pipecat, configure local audio) rather than the single verb 'Build'.

DimensionReasoningScore

Specificity

The description names the domain ('voice assistant') and one concrete action ('Build') with a specific stack ('Pipecat, Gemini, and OpenAI'), but offers only a single action verb rather than the several specific actions of anchor 4.

3 / 5

Completeness

The 'what' is clear (build a voice assistant with the named stack), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Terms like 'voice assistant', 'Pipecat', 'Gemini', 'OpenAI', and 'low-latency' are natural phrases users would say. Common variations such as 'voice agent', 'real-time', 'speech-to-speech', or 'STT/TTS' are missing, so it does not reach anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The 'Pipecat + Gemini + OpenAI tactical voice assistant' combination is a mostly distinct niche with framework-specific triggers, but the broad 'voice assistant' phrasing leaves minor overlap risk with closely related voice-agent skills rather than the minimal risk of anchor 5.

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.

Validation — 15 / 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

Path

skills/pipecat-friday-agent/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.