New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Submitting Feedback

by letta-ai in letta-ai/letta-code

Submits user-approved product feedback and bug reports about Letta Code to the Letta team.

Apache-2.0Auto-check passedTesting & QA

Install Submitting Feedback

skills CLI
$ npx skills add letta-ai/letta-code --skill submitting-feedback -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install letta-ai/letta-code submitting-feedback --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/letta-ai/letta-code.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/skills/builtin/submitting-feedback .claude/skills/submitting-feedback && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
submitting-feedback
GitHub stars
3.6k
Token cost
~739 tokens
SKILL.md length
368 words
Files
1
Skills in repo
25
Repo updated
First seen
Licence
Apache-2.0

At a glance

Submits user-approved product feedback and bug reports about Letta Code to the Letta team.

  • Works in 4 steps: Gather the relevant context already… → Write a concise, factual report in your… → Submit it with → …
  • Reports a Letta Code bug
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Requests a product

What it does

Submitting Feedback is an agent skill from letta-ai/letta-code. Submits user-approved product feedback and bug reports about Letta Code to the Letta team. Load when the user reports a Letta Code bug, requests a product or developer change, or explicitly asks to send feedback. Do not load for corrections to the current agent's behavior or preferences; those are memory edits. Works with cloud-hosted and local agents. Ask before submitting unless the user already explicitly requested submission.

Its SKILL.md is about 740 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering QA and bug reports. It works with Letta. The repository describes itself as: Stateful agents that are like people, with memory, identity, and the ability to learn and adapt. The licence is Apache-2.0.

When your agent uses it

  • Reports a Letta Code bug
  • Requests a product
  • Developer change
  • Explicitly asks to send feedback

Example prompts

  • “Use the submitting-feedback skill to submit user-approved product feedback and bug reports about Letta Code to the Letta team”
  • “/submitting-feedback”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Gather the relevant context already available in the conversation and environment. If a detail essential to understanding or reproducing…
  2. Write a concise, factual report in your own voice as the agent. Do not impersonate the user or make the report sound user-authored. The…
  3. Submit it with
  4. Tell the user whether submission succeeded. If it failed, report the safe CLI error and do not claim the team received it.

What it can do on your machine

Read from SKILL.md and the folder at commit 253a3bc. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Submitting Feedback loads about 739 tokens when it runs. Until then it costs about 113 tokens; SKILL.md has 368 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~113
When it runs · the whole SKILL.md, loaded when a task matches
~739

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from letta-ai/letta-code at commit 253a3bc, republished under its Apache-2.0 licence (© letta-ai). 368 words, ~739 tokens.

Download SKILL.mdSave it as .claude/skills/submitting-feedback/SKILL.md (or your agent's skills folder).
name
submitting-feedback
description
Submits user-approved product feedback and bug reports about Letta Code to the Letta team. Load when the user reports a Letta Code bug, requests a product or developer change, or explicitly asks to send feedback. Do not load for corrections to the current agent's behavior or preferences; those are memory edits. Works with cloud-hosted and local agents. Ask before submitting unless the user already explicitly requested submission.

Submitting Feedback

Use this skill for product and developer feedback about Letta Code: reproducible bugs, broken features, confusing product behavior, and requested changes to the software or its developer-facing behavior.

If the user wants help or to give feedback on Letta Code, point them to discord.gg/letta or https://github.com/letta-ai/letta-code/issues.

Do not use this skill when the user corrects how the current agent should behave, communicate, remember, or work with them. Treat that as learning: make the appropriate memory edit so the correction changes the agent's future behavior. A user's frustration with the agent is not by itself product feedback and is not a reason to offer feedback submission.

If the user says yes, or directly asks you to submit feedback:

  1. Gather the relevant context already available in the conversation and environment. If a detail essential to understanding or reproducing the problem is missing, ask the user one focused question before submitting. Do not invent missing details.

  2. Write a concise, factual report in your own voice as the agent. Do not impersonate the user or make the report sound user-authored. The first line must disclose: Agent-submitted feedback on behalf of the user.

    Include:

    • Your agent name.
    • Who you are working with (the user's name or role, if known; otherwise say user not identified).
    • The task or goal underway when the problem occurred and enough surrounding context to understand why it mattered.
    • What actually happened, what the user expected, and the impact on the task.
    • Concrete evidence already available, such as exact error text, the failed command or action, relevant paths or links, and reliable reproduction steps. Distinguish what the user reported from what you observed or inferred.

    Prefer specific nouns and observable behavior over generic judgments. Do not submit context-free summaries such as “the feature is broken,” “the UX should be improved,” or polished product-language filler. Keep unknowns explicit rather than guessing.

  3. Submit it with:

Show full SKILL.md (52 more words)Show less
bash
letta feedback --message '<feedback>'
  1. Tell the user whether submission succeeded. If it failed, report the safe CLI error and do not claim the team received it.

Do not include secrets, credentials, unrelated conversation content, or private file contents. The command adds the current agent and conversation identifiers so the team can find the relevant run.

© letta-ai, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in src/skills/builtin/submitting-feedback of letta-ai/letta-code.

Open the folder on GitHubat commit 253a3bc

Compare with similar skills

Submitting Feedback next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Submitting Feedback compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Submitting Feedback this skillletta-ai/letta-code3.6k—~739Automated safety check: PassApache-2.0
Dogfood Exploratory QAvercel-labs/agent-browser44k8 repos~2.7kAutomated safety check: PassApache-2.0
DeerFlow Smoke Testbytedance/deer-flow84k—~2.5kAutomated safety check: NotesMIT
CodexBar Live QAsteipete/CodexBar22k—~1.2kAutomated safety check: PassMIT
Diagnose Playwright Failure as Product Bugappsmithorg/appsmith41k—~1.5kAutomated safety check: PassApache-2.0
Acceptance Evidence for Deliverieslobehub/lobehub83k—~9.7kAutomated safety check: PassApache-2.0

Similar skills

  • Dogfood Exploratory QA

    vercel-labs/agent-browser

    Official

    Explores a web app with the agent-browser CLI to find bugs and UX problems, then writes a report with screenshots, repro videos and step-by-step reproduction for each issue.

    44k GitHub starsUsed in 8 repos~2.7k tokens
    Testing & QAAuto-check passed

  • DeerFlow Smoke Test

    bytedance/deer-flow

    Walks through an end-to-end smoke test of a DeerFlow deployment: pull the latest code, deploy with Docker or locally, verify services, run health checks and write a report.

    84k GitHub stars~2.5k tokensUpdated today
    Testing & QAAuto-check: notes

  • CodexBar Live QA

    steipete/CodexBar

    Runs live QA for the CodexBar app: provider usage matrix checks through its packaged CLI, config validation and menu checks, with 1Password-backed credentials handled safely.

    22k GitHub stars~1.2k tokensUpdated today
    Testing & QAAuto-check passed

  • Diagnose Playwright Failure as Product Bug

    appsmithorg/appsmith

    Investigates a stubbornly failing Playwright test as a possible product bug, using error output, screenshots, traces and server code, and writes a structured bug report.

    41k GitHub stars~1.5k tokensUpdated today
    Testing & QAAuto-check passed

  • Acceptance Evidence for Deliveries

    lobehub/lobehub

    Verifies a delivery end to end by driving the real product on a CLI, web, desktop or iOS Simulator surface, capturing evidence and publishing a round with the lh CLI.

    83k GitHub stars~9.7k tokensUpdated today
    Testing & QAAuto-check passed

  • Codex Plugin QA

    code-yeongyu/oh-my-openagent

    Tests the omo Codex plugin in an isolated CODEX_HOME with a local mock model, proving hooks fired through app-server notifications without touching ~/.codex.

    70k GitHub stars~1.9k tokensUpdated today
    Testing & QAAuto-check passed

More from letta-ai/letta-code

All 25 skills in this repo

  • Creating Skills

    letta-ai/letta-code

    Guide for creating effective skills. An agent skill from letta-ai/letta-code.

    3.6k GitHub stars~4.6k tokensUpdated today
    Auto-check passed

  • Generating Mod Envs

    letta-ai/letta-code

    Generates and reviews mod learning env JSON files for Letta Code local mods.

    3.6k GitHub stars~1.5k tokensUpdated today
    Auto-check passed

  • Initializing Memory

    letta-ai/letta-code

    Comprehensive guide for initializing or reorganizing agent memory.

    3.6k GitHub stars~4.8k tokensUpdated today
    Auto-check passed

  • Self Configuration

    letta-ai/letta-code

    Inspect or modify Letta Code's own memory, model, context window, system prompt, compaction, permissions, toolsets, mods, skills, channels, schedules, agent secrets, and local runtime settings.

    3.6k GitHub stars~7k tokensUpdated today
    Auto-check passed

  • Browser Use

    letta-ai/letta-code

    Control a real browser to navigate pages, click, type, fill forms, inspect rendered UI, take screenshots, or record video.

    3.6k GitHub stars~3.3k tokensUpdated today
    Auto-check passed

  • Creating Mods

    letta-ai/letta-code

    Creates and edits trusted local Letta Code mods, including tools, slash commands, local-only model providers, lifecycle/turn events, scoped conversation helpers, panels, and capability-gated behavior.

    3.6k GitHub stars~2.5k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Submitting Feedback

What does Submitting Feedback do?

Submits user-approved product feedback and bug reports about Letta Code to the Letta team. Submitting Feedback is an agent skill from letta-ai/letta-code. Submits user-approved product feedback and bug reports about Letta Code to the Letta team.

When should I use Submitting Feedback?

Submitting Feedback fits situations like: reports a Letta Code bug; requests a product; developer change; explicitly asks to send feedback.

How do I install Submitting Feedback in Claude Code?

Run `npx skills add letta-ai/letta-code --skill submitting-feedback -a claude-code`. Or copy the skill folder (src/skills/builtin/submitting-feedback in letta-ai/letta-code) into .claude/skills/submitting-feedback in your project. Claude Code loads it when a task matches its description.

How do I install Submitting Feedback in Codex?

Run `npx skills add letta-ai/letta-code --skill submitting-feedback -a codex`. Or copy the skill folder (src/skills/builtin/submitting-feedback in letta-ai/letta-code) into .agents/skills/submitting-feedback in your project. Codex loads it when a task matches its description.

Can I use Submitting Feedback in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add letta-ai/letta-code --skill submitting-feedback -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/submitting-feedback, .gemini/skills/submitting-feedback, .github/skills/submitting-feedback and .opencode/skills/submitting-feedback in your project.

What does Submitting Feedback need to run?

SKILL.md names no scripts, command-line tools or credentials: Submitting Feedback is instructions for the agent only.

Does Submitting Feedback access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Submitting Feedback safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Submitting Feedback use?

Submitting Feedback is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Submitting Feedback use?

About 739 tokens (SKILL.md is roughly 3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Submitting Feedback?

Skills that share tags, products or a category with Submitting Feedback: Dogfood Exploratory QA (vercel-labs/agent-browser, 44k stars), DeerFlow Smoke Test (bytedance/deer-flow, 84k stars), CodexBar Live QA (steipete/CodexBar, 22k stars) and Diagnose Playwright Failure as Product Bug (appsmithorg/appsmith, 41k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Submitting Feedback?

letta-ai (a GitHub organization) maintains it in letta-ai/letta-code, which has 3,552 GitHub stars. The repository holds 25 skills in this directory. The repository was last updated on October 9, 2026.

Source: letta-ai/letta-code on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.