diff --git a/.claude-plugin/plugin.json b/.claude-plugin/plugin.json index 5f42d64..66bb13b 100644 --- a/.claude-plugin/plugin.json +++ b/.claude-plugin/plugin.json @@ -1,7 +1,7 @@ { "name": "langfuse", "description": "Skills for working with Langfuse, the open-source LLM engineering platform for tracing, prompt management, and evaluation.", - "version": "1.4.4", + "version": "1.5.0", "author": { "name": "Langfuse", "email": "support@langfuse.com" diff --git a/.codex-plugin/plugin.json b/.codex-plugin/plugin.json index 79b551d..33799b2 100644 --- a/.codex-plugin/plugin.json +++ b/.codex-plugin/plugin.json @@ -1,6 +1,6 @@ { "name": "langfuse", - "version": "1.4.3", + "version": "1.5.0", "description": "Skills for working with Langfuse, the open-source LLM engineering platform for tracing, prompt management, and evaluation.", "author": { "name": "Langfuse", diff --git a/.cursor-plugin/plugin.json b/.cursor-plugin/plugin.json index 19e806d..1b29212 100644 --- a/.cursor-plugin/plugin.json +++ b/.cursor-plugin/plugin.json @@ -1,7 +1,7 @@ { "name": "langfuse", "displayName": "Langfuse", - "version": "1.4.4", + "version": "1.5.0", "description": "Skills for working with Langfuse — the open-source LLM engineering platform for tracing, prompt management, and evaluation.", "author": { "name": "Langfuse", diff --git a/skills/langfuse/references/skill-feedback.md b/skills/langfuse/references/skill-feedback.md index 49bcb12..dadc75e 100644 --- a/skills/langfuse/references/skill-feedback.md +++ b/skills/langfuse/references/skill-feedback.md @@ -1,55 +1,35 @@ --- name: langfuse-skill-feedback -description: Submit feedback about the Langfuse skill to its maintainers via GitHub Discussions. Use when the user indicates the skill gave incorrect guidance, is missing information, or could be improved. +description: Submit feedback about the Langfuse skill to its maintainers. Use when the skill's instructions are wrong, outdated, missing something, or could be improved. metadata: required_access: - - GITHUB + - LANGFUSE_PROJECT_INTERFACE --- # Skill Feedback -Follow these steps exactly: +Use this only for feedback about the skill itself, not Langfuse the product or a user's application data. -1. **Ask permission**: Ask the user if they'd like you to submit feedback to the skill maintainers. Make it clear this is about the skill (the agent instructions), not about Langfuse the product. If they decline, move on. -2. **Draft feedback**: Write the feedback using the form structure below. Present the draft to the user and ask if they'd like to change anything before submitting. -3. **Submit**: Once approved, submit via `gh` CLI as described below. Share the resulting discussion URL with the user. +1. Draft concise feedback using the following structure: + - **Describe your idea or feedback** (required) + A clear description of what went wrong or what could be improved. Include: + - What the user was trying to do (as `goal`) + - What the skill did vs what was expected + - Any specific instructions that were incorrect or missing -## Feedback Form Structure + - **What would the ideal outcome look like?** (optional) + What the correct behavior or guidance should be. -Draft the feedback using these two fields: + If feedback targets existing skill, reference in `target`. +2. If the user wants a reply, ask them to include an email address in `feedback`; use only an address they explicitly provide. +3. Show every submitted field exactly as it will be sent and ask for explicit permission. Do not submit without approval. -**Describe your idea or feedback** (required) -A clear description of what went wrong or what could be improved. Include: -- What the user was trying to do -- What the skill did vs what was expected -- Any specific instructions that were incorrect or missing +## Submission options -**What would the ideal outcome look like?** (optional) -What the correct behavior or guidance should be. +Use the first available option, or the option the user prefers: -Format the body as markdown with the two field labels as headings. +1. **Authenticated Langfuse MCP, CLI, or Public API** — prefer the `submitFeedback` tool on the Langfuse MCP server. If it is unavailable, discover the current feedback operation with the Langfuse CLI schema/help and submit through the authenticated Public API. Do not ask users to paste credentials into chat. +2. **Langfuse Docs MCP** — use its unauthenticated `submitFeedback` tool when no authenticated Langfuse interface is available. +3. **GitHub issue or discussion** — if no MCP/CLI/API is available, or the user wants a public, trackable thread, provide a prefilled discussion link for the user to submit: `https://github.com/langfuse/skills/discussions/new?category=ideas-improvements&title=&body=`. Use `https://github.com/langfuse/skills/issues/new` if they prefer an issue. -## Submitting - -Create a GitHub Discussion on the `langfuse/skills` repository using the GraphQL API: - -```bash -gh api graphql -f query=' -mutation($repoId: ID!, $categoryId: ID!, $title: String!, $body: String!) { - createDiscussion(input: {repositoryId: $repoId, categoryId: $categoryId, title: $title, body: $body}) { - discussion { url } - } -}' \ - -f repoId="$(gh api graphql -f query='{ repository(owner: "langfuse", name: "skills") { id } }' --jq '.data.repository.id')" \ - -f categoryId="$(gh api graphql -f query='{ repository(owner: "langfuse", name: "skills") { discussionCategories(first: 10) { nodes { id name } } } }' --jq '.data.repository.discussionCategories.nodes[] | select(.name == "Ideas & Improvements") | .id')" \ - -f title="" \ - -f body="" -``` - -If the `gh` CLI is not authenticated or the request fails, give the user this link to create the discussion manually: - -``` -https://github.com/langfuse/skills/discussions/new?category=ideas-improvements -``` - -After submission, share the discussion URL with the user. +Report the Langfuse correlation ID or GitHub URL. If submission fails, give a safe error without exposing credentials or request bodies.