agentleFS
scalyax-aiscalyax-ai/claude-plugin-performance-marketing-agency/skills/save/SKILL.md

save

Skill0 starsChanged 9 days agoMITView on GitHub

Save something to this client's Analify Brain right now — a finding, decision, client rule, audit or file.

37 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use load, ingest and 10 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.
  • TheLatentSpaceLabSkill

    load

    Load a document into memory for RAG

    Also in 4 projects that use this

  • JaimeGBASkill

    ingest

    Digest an external source (article, paper, transcript, URL, book chapter) and integrate its content into the knowledge base

    Also in 8 projects that use this

  • ArtemXTechSkill

    query

    Query data from this vault. USE WHEN user asks about projects, clients, tasks, daily notes. Use grep to extract frontmatter - do NOT read full files.

    Also in 4 projects that use this

  • szweibelSkill

    idea

    Generate a wide field of options when the user is brainstorming, exploring, expanding, or pressure-testing — not recommending or implementing

    Also in 3 projects that use this

  • GoogleSkill

    dashboard

    Configures and launches the GKE Capacity & Triage Dashboard scoped to a GCP project ID, GKE cluster name, or target ML workload ID. Uses the configure-and-launch-dashboard action and launch-workload-dashboard workflow to verify local dashboard health, discover cluster capacity, trigger live scans, and generate deep-linked URLs. Use when the user types "/dashboard", says "launch dashboard", "open dashboard", "show capacity", or "view triage dashboard" with a project, cluster, or workload. Don't use for general workload log querying or automated failure attribution (use the troubleshoot skill).

    Also in 4 projects that use this

  • Microsoft AzureSkill

    lint

    Run all linting and spell checking for TypeScript and Rust code. Run this before committing to catch style issues, clippy warnings, and misspellings.

    Also in 5 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 31 edited versions we read keep these.

  • 0

    Distinctive

    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:

    Only in a client folder, using this client's own mcp__analify-<client>__ tools.

    line 10
  2. Very specific:

    Make sure the connection is confirmed (analify_brain_session_start with this session's id) and names this client's Brand.

    line 14

“Common” is measured: kept by at least 6 in 10 of the 31 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

Save to this client's Brain

Only in a client folder, using this client's own mcp__analify-<client>__ tools. The user asked for this save, so it is approved.

What to save: $ARGUMENTS (if empty, save the important findings and decisions from this session so far).

  1. Make sure the connection is confirmed (analify_brain_session_start with this session's id) and names this client's Brand.
  2. A file (Markdown, CSV, text): analify_call_write_tool with tool_name analify_brain_files_post, arguments { filename, text, import: true }.
  3. A finding worked out from data: analify_call_write_tool with tool_name analify_brain_remember, arguments { question, answer, toolsUsed }.
  4. A decision, client rule, test or procedure: analify_brain_capture with kind, a one- or two-sentence statement starting with the agency name, the date, decisionItImproves and entities.
  5. A rule the client's founder stated in their own words: analify_call_write_tool with tool_name analify_brain_statements, arguments { text }. Only for the founder's own words.
  6. Say in one line what was saved and where.

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.