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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

92%

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

A highly actionable, concise deployment guide with executable code and clear validation steps across platforms. Its main gap is progressive disclosure: the monolithic single-file structure could be split into per-platform reference files to keep SKILL.md a true overview.

Suggestions

Move each platform guide (Vercel, Lambda, Docker self-host, Cloud Run) into its own referenced file under references/ and keep SKILL.md as a concise overview with one-level-deep links, e.g. 'Vercel/Next.js: See [VERCEL.md](references/VERCEL.md)'.

Add a brief 'Choose your platform' decision pointer at the top so Claude routes to the right reference file rather than scanning all inline guides.

Dimension	Reasoning	Score
Conciseness	The body is lean: a one-line overview, three prerequisite bullets, executable code blocks, and compact tables, with no padding or explanation of concepts Claude already knows; the only prose is genuinely non-obvious domain detail (the OTel v3/v4 flush note).	3 / 3
Actionability	Every step provides copy-paste-ready, executable artifacts — a full docker-compose.yml, `vercel env add` and `gcloud run deploy` commands, and complete TypeScript handlers — with specific values rather than pseudocode.	3 / 3
Workflow Clarity	Steps are explicitly sequenced (Step 1–5) and risky deploy operations include validation checkpoints, e.g. the Docker path generates secrets, runs `docker compose up -d`, then 'Wait and verify' with `curl ... /api/public/health`, and an Error Handling table provides recovery guidance.	3 / 3
Progressive Disclosure	No bundle files exist in references/scripts/assets, yet the ~180-line body inlines five independent platform guides plus tables that could each be split into one-level-deep referenced files (e.g. VERCEL.md, DOCKER.md), matching the score-2 'content that should be separate is inline' anchor rather than a clean overview-plus-references structure.	2 / 3
	Total	11 / 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, well-structured description with an explicit Use-when clause and natural trigger phrases. Its only weakness is action specificity, naming platforms more concretely than the distinct deploy/integrate actions it performs.

Suggestions

Replace generic verbs with concrete capabilities, e.g. 'Add Langfuse SDK tracing, configure serverless flush behavior, and self-host the Langfuse server via Docker' to lift specificity toward the score-3 anchor.

Dimension	Reasoning	Score
Specificity	Names the domain and target platforms ('Deploy Langfuse with your application across different platforms', 'Vercel, AWS, GCP, or Docker') but relies on only two verbs (deploy, integrate) rather than listing multiple distinct concrete actions, matching the score-2 anchor rather than the multi-action score-3 example.	2 / 3
Completeness	It states what the skill does ('Deploy Langfuse with your application across different platforms') and gives an explicit 'Use when deploying Langfuse to Vercel, AWS, GCP, or Docker, or integrating Langfuse into your deployment pipeline' clause, answering both what and when.	3 / 3
Trigger Term Quality	Explicit natural trigger phrases are listed — 'deploy langfuse', 'langfuse Vercel', 'langfuse AWS', 'langfuse Docker', 'langfuse production deploy' — giving good coverage of terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	The Langfuse-deployment niche is specific and the trigger phrases are product-scoped, making it unlikely to fire for an unrelated skill.	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
Commit: 3022dd3

Reviewed: 1 day 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.