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

38%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/pipecat-friday-agent/SKILL.md

Quality

Content

32%Scale 1-5

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

This skill reads more like a README overview than an actionable skill for Claude. The critical implementation—the actual Python agent code, the GoogleSafeContext shim, the system prompt—is entirely absent, making it impossible for Claude to build the described agent. The content also includes unnecessary sections (When to Use, Core Concepts) that explain things Claude already knows, while omitting the concrete details it actually needs.

Suggestions

Include the actual `friday_agent.py` script content either inline or as a bundle file—this is the core deliverable and without it the skill is non-functional.

Remove the 'When to Use This Skill' and 'Core Concepts' sections; Claude doesn't need to be told when to use a skill or what a pipeline architecture is.

Add validation steps: verify API keys work (e.g., a quick test call), verify audio device selection before running the full agent, and add a feedback loop for the Google shim validation errors.

Provide the GoogleSafeContext/GoogleSafeMessage shim code explicitly—this is the novel, non-obvious part that Claude genuinely needs.

Dimension	Reasoning	Score
Conciseness	The 'When to Use This Skill' section is largely unnecessary padding—Claude doesn't need to be told when to use a skill it's been given. The 'Overview' section re-explains what STT/LLM/TTS are. The 'Core Concepts' section explains pipeline architecture at a level Claude already understands. However, the best practices and troubleshooting sections are reasonably tight.	3 / 5
Actionability	The skill tells you to 'execute the provided Python script' but never provides the actual script content. The core implementation—the pipeline setup, the GoogleSafeContext shim, the system prompt—is entirely absent. The only executable content is pip install and env file setup, which are trivial. Claude cannot build this agent from what's given.	2 / 5
Workflow Clarity	The three steps (install, configure, run) are a rough sequence but are extremely high-level with no validation checkpoints. There's no verification that dependencies installed correctly, no check that API keys are valid, no feedback loop for common failures. The troubleshooting section hints at issues but doesn't integrate into the workflow as validation steps.	2 / 5
Progressive Disclosure	The skill references 'the provided Python script' at `scripts/friday_agent.py` and a `test_audio_output.py`, but no bundle files exist. The related skills reference other skills with @ syntax but these are unverifiable. The actual implementation code that should either be inline or in a referenced bundle file is completely missing, making the skill non-functional as written.	2 / 5
	Total	9 / 20 Passed

Description

45%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 reads more like a project title than a skill description. While it names specific technologies (Pipecat, Gemini, OpenAI) that provide some distinctiveness, it lacks concrete actions beyond 'build' and entirely omits a 'when to use' clause. The Iron Man/F.R.I.D.A.Y. reference adds flavor but doesn't help Claude determine when to select this skill.

Suggestions

Add a 'Use when...' clause with trigger terms like 'voice assistant', 'Pipecat', 'real-time audio', 'conversational AI', 'streaming voice pipeline'.

Expand the capabilities beyond 'build' to list specific actions such as 'configures audio pipelines, integrates speech-to-text and text-to-speech, sets up real-time conversation handling, deploys WebSocket-based voice interfaces'.

Include natural user phrases and synonyms like 'voice bot', 'speech assistant', 'audio chatbot', or 'real-time voice AI' to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (tactical voice assistant) and mentions specific technologies (Pipecat, Gemini, OpenAI), but the concrete actions are limited to 'build' without detailing what capabilities the assistant has or what steps are involved.	3 / 5
Completeness	Has a somewhat clear 'what' (build a voice assistant using specific tools) but completely lacks a 'when' clause. There is no guidance on when Claude should select this skill, which caps this dimension. The 'what' itself is also more of a project title than a detailed capability description.	2 / 5
Trigger Term Quality	Includes some relevant keywords like 'voice assistant', 'Pipecat', 'Gemini', 'OpenAI', and 'F.R.I.D.A.Y.', but misses natural user phrases like 'real-time audio', 'speech-to-text', 'conversational AI', 'voice bot', or 'streaming voice'. The Iron Man reference is niche and may not match typical user queries.	3 / 5
Distinctiveness Conflict Risk	The combination of Pipecat, Gemini, OpenAI, and the F.R.I.D.A.Y. branding makes this fairly distinctive. It's unlikely to conflict with generic coding or voice assistant skills, though there could be minor overlap with other voice/AI assistant building skills.	4 / 5
	Total	12 / 20 Passed

Validation

90%

Warnings & errors only

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

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/pipecat-friday-agent/SKILL.md
Commit: 57c135b

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.