agentleFS
Sign inStart free
ggkguelensanggkguelensan/asana-cli/skills/source/asana-cli-insights/SKILL.md

asana-cli-insights

Skill1 starsChanged 9 days agoMITView on GitHub

Analyze metadata-only local asana-cli history and suggest improvements without exposing Asana content or credentials.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Use asana-cli insights to review local invocation metadata.

    line 8
  2. Distinctive:

    If more context is needed, ask the user.

    line 19
  3. Very specific:

    Ask the user to run asana-cli doctor for installation/auth diagnostics.

    line 21

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Asana CLI insights

Use asana-cli insights to review local invocation metadata. The log contains command categories, outcomes, durations, effects, and normalized error codes. It intentionally excludes free-form argument values, GIDs, paths, task/comment content, and credentials.

Procedure

  1. Run asana-cli insights --days 30.
  2. Explain the strongest observations first: success rate, common commands, recurring error classes, and whether maintenance checks are being used.
  3. Turn deterministic recommendations into practical next steps. Do not claim to know task content, project quality, employee performance, or intent from metadata.
  4. If more context is needed, ask the user; do not inspect unrelated local files or expand into raw Asana reads automatically.
  5. Ask the user to run asana-cli doctor for installation/auth diagnostics; agent mode cannot inspect human installation paths or credential state. Use asana-cli man insights for details.

Insights are advisory and perform no Asana writes.

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