langfuse-deploy-integration

Deploy Langfuse with your application across different platforms. Use when deploying Langfuse to Vercel, AWS, GCP, or Docker, or integrating Langfuse into your deployment pipeline. Trigger with phrases like "deploy langfuse", "langfuse Vercel", "langfuse AWS", "langfuse Docker", "langfuse production deploy".

Quality

77%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/saas-packs/langfuse-pack/skills/langfuse-deploy-integration/SKILL.md

Quality

Content

64%

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

This skill provides strong, actionable deployment guidance across multiple platforms with executable code examples and useful troubleshooting tables. Its main weaknesses are the monolithic structure (all platforms inline rather than split into referenced files) and missing explicit validation steps after deployment on most platforms. The content would benefit from restructuring into a concise overview with platform-specific details in separate files.

Suggestions

Split platform-specific deployment sections (Vercel, Lambda, Docker, Cloud Run) into separate referenced files, keeping SKILL.md as a concise overview with links to each.

Add explicit verification/validation steps after each deployment (e.g., 'Send a test request and verify traces appear in the Langfuse dashboard within 30 seconds').

Remove the numbered 'Step' labeling since these are independent deployment options, not sequential steps — use platform names as section headers instead.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient with executable code examples, but includes some unnecessary verbosity — the health check endpoint and some inline comments could be tightened. The platform-specific considerations table is useful but the overall document is quite long for what could be more modular.	2 / 3
Actionability	Fully executable code examples across all platforms — bash commands, TypeScript handlers, docker-compose YAML, and Cloud Run deploy commands are all copy-paste ready with specific imports, configurations, and concrete patterns.	3 / 3
Workflow Clarity	Steps are clearly sequenced and labeled, but they represent independent deployment options rather than a true sequential workflow. The Docker section includes a health check verification step, but other sections lack explicit validation/verification checkpoints (e.g., no 'verify traces appear in dashboard' step after deploying to Vercel or Lambda).	2 / 3
Progressive Disclosure	The content is a long monolithic document covering 5 different deployment platforms inline. The platform-specific sections would benefit from being split into separate files with the SKILL.md serving as an overview with links. External resource links are provided at the bottom but the body itself is not well-layered.	2 / 3
	Total	9 / 12 Passed

Description

89%

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

This is a solid skill description with excellent trigger terms and completeness. Its main weakness is that the capability description is somewhat thin—it says 'deploy' but doesn't enumerate specific deployment actions or configurations. The Langfuse-specific focus makes it highly distinctive and unlikely to conflict with other skills.

Suggestions

Add more specific concrete actions beyond 'deploy', such as 'configure environment variables, set up database connections, manage infrastructure-as-code templates' to improve specificity.

Dimension	Reasoning	Score
Specificity	The description names the domain (deploying Langfuse) and mentions specific platforms (Vercel, AWS, GCP, Docker), but doesn't list concrete actions beyond 'deploy' and 'integrating into deployment pipeline'. It lacks specifics like configuring environment variables, setting up databases, or managing infrastructure.	2 / 3
Completeness	Clearly answers both 'what' (deploy Langfuse across different platforms) and 'when' (explicit 'Use when' clause with specific scenarios plus a 'Trigger with phrases' section listing concrete trigger terms).	3 / 3
Trigger Term Quality	Includes strong natural trigger terms users would actually say: 'deploy langfuse', 'langfuse Vercel', 'langfuse AWS', 'langfuse Docker', 'langfuse production deploy'. These cover multiple platform variations and common phrasing patterns.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive due to the specific product name 'Langfuse' combined with deployment contexts. Very unlikely to conflict with other skills since it targets a specific tool's deployment across named platforms.	3 / 3
	Total	11 / 12 Passed

Validation

81%

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 — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	9 / 11 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 00c0702

Reviewed: 2 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.