agentleFS
Sign inStart free
graphed-incgraphed-inc/marketing-skills/skills/feedback/SKILL.md

feedback

Skill30 starsChanged 9 days agoMITView on GitHub

Report a Graphed platform problem. Use when a Graphed command, the platform, or the docs fail or a capability is missing, and the user should send that report with `graphed feedback`.

  • Installs packages

26 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use setup, status and 6 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • VercelSkill

    setup

    Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".

    Also in 5 projects that use this

  • AnthropicSkill

    status

    Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.

    Also in 3 projects that use this

  • GitHubSkill

    refactor

    Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.

    Also in 3 projects that use this

  • AnthropicSkill

    debug

    Structured debugging session — reproduce, isolate, diagnose, and fix. Trigger with an error message or stack trace, "this works in staging but not prod", "something broke after the deploy", or when behavior diverges from expected and the cause isn't obvious.

    Also in 3 projects that use this

  • BlockSkill

    plan

    Draft a TDD, PRD, or lightweight plan in the conversation without committing it.

    Also in 3 projects that use this

  • SentrySkill

    review

    Fixture review skill.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 24 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When a Graphed platform problem shows up, ask the user to send it with graphed feedback.

    line 8
  2. Distinctive:

    Use this for platform bugs, missing platform features, and docs that are wrong or missing.

    line 11
  3. Very specific:

    If graphed is not on PATH, stop and ask the user to install it (npm i -g @graphed-inc/cli).

    line 17
  4. Distinctive:

    Read the current usage before drafting the report:

    line 19
  5. Very specific:

    Put the command that failed and what you expected in --context.

    line 39
  6. Distinctive:

    Leave secret values, tokens, and credentials out of the message and the context.

    line 50

“Common” is measured: kept by at least 6 in 10 of the 24 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Feedback

When a Graphed platform problem shows up, ask the user to send it with graphed feedback. The report goes to the Graphed team.

Use this for platform bugs, missing platform features, and docs that are wrong or missing. Problems in the user's own application code stay in the project.

What to do

  1. If graphed is not on PATH, stop and ask the user to install it (npm i -g @graphed-inc/cli).

  2. Read the current usage before drafting the report:

    graphed docs feedback
  3. Draft a short message and the exact command. Show it to the user and ask them to run it. Send it yourself only after they ask you to.
  4. The command needs graphed login or GRAPHED_TOKEN.

Command

graphed feedback "what happened"
graphed feedback --kind bug "graphed logs --follow exits immediately on empty log streams"
graphed feedback --kind feature_request --context "graphed deploy --account acc_123" "deploy should print the service URL when the rollout finishes"

--kind is bug, feature_request, or general (the default).

Put the command that failed and what you expected in --context. For a long log, pipe it in with - as the last message argument:

graphed logs --project <project_slug> --account <account_id> 2>&1 | graphed feedback "logs failed unexpectedly" - --kind bug --context "graphed logs --project <project_slug>"

Include what the user was trying to do, the exact command, and what happened instead. Re-run with --verbose when that output explains the failure, and attach it as context.

Leave secret values, tokens, and credentials out of the message and the context.

About Graphed

Graphed is a marketing cloud. It includes the infrastructure for an agent to do marketing: a data warehouse, data pipelines, a Postgres database, cron jobs, runtime servers, a tool catalog, custom domains, and internal app tooling.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free