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

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No known issues

Quality

Content

80%

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

A highly actionable, token-efficient skill body with strong executable examples and useful error/platform tables. Its main gaps are missing explicit verification checkpoints on the serverless steps and no progressive disclosure via bundle files for the sizable per-platform content.

Suggestions

Add an explicit verify step to each deployment path (e.g. after Vercel deploy: `vercel inspect <url>`; after Cloud Run: `gcloud run services describe` / curl the service URL) so every step has a validation checkpoint, not just the Docker path.

Move the per-platform deployment recipes (Vercel, Lambda, Cloud Run, self-hosted Docker) into separate reference files under references/ (e.g. references/vercel.md, references/lambda.md) and have SKILL.md overview + link to them, improving progressive disclosure.

Turn the Error Handling table into an explicit validate-fix-retry feedback loop note attached to the risky self-hosted Docker and serverless flush steps so the recovery path is actionable per-step rather than a standalone table.

Dimension	Reasoning	Score
Conciseness	The body is dense with executable code and compact tables, with no padding explaining concepts Claude already knows (e.g. it never explains what observability or Langfuse is); the Overview and Prerequisites are brief and every code block earns its place.	3 / 3
Actionability	Provides fully executable, copy-paste-ready guidance per platform: vercel env commands, a Next.js route handler, a Lambda handler, a docker-compose.yml, openssl/docker/curl shell commands, and gcloud run deploy commands.	3 / 3
Workflow Clarity	Steps are sequenced (Step 1-5) and the Docker path has explicit verification (healthcheck + depends_on + "curl ... health"), but the Vercel, Lambda, and Cloud Run steps lack explicit validation checkpoints, so checkpoints are missing or implicit for most steps.	2 / 3
Progressive Disclosure	Sections are well-organized and the Resources section links one level deep to external Langfuse docs, but no bundle files exist and per-platform deployment guides are inlined in a single ~240-line SKILL.md that could be split into separate reference files.	2 / 3
	Total	10 / 12 Passed

Description

90%

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, third-person description that covers what the skill does, when to use it, and concrete trigger phrases for a well-scoped niche. The only minor weakness is specificity, which lists platforms more than a breadth of distinct actions.

Dimension	Reasoning	Score
Specificity	Names the domain ("Deploy Langfuse with your application across different platforms") and the action verbs deploy/integrate, but does not enumerate multiple distinct concrete actions like the level-3 anchor (e.g. extract, fill, merge); it lists platforms rather than a breadth of actions.	2 / 3
Completeness	Clearly answers both what ("Deploy Langfuse with your application across different platforms") and when ("Use when deploying Langfuse to Vercel, AWS, GCP, or Docker, or integrating Langfuse into your deployment pipeline") with explicit triggers, matching the level-3 anchor.	3 / 3
Trigger Term Quality	Explicit natural trigger phrases ("deploy langfuse", "langfuse Vercel", "langfuse AWS", "langfuse Docker", "langfuse production deploy") plus "Use when deploying Langfuse to Vercel, AWS, GCP, or Docker" give good coverage of terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche (Langfuse deployment) with product-specific triggers ("langfuse Vercel", "langfuse Docker", etc.) that are unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

87%

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 — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/saas-packs/langfuse-pack/skills/langfuse-deploy-integration/SKILL.md
Commit: b2e8c53

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