agentleFS
DevinoSolutionsDevinoSolutions/claude-plugins/skills/analyzing-page-performance/SKILL.md

analyzing-page-performance

Skill0 starsChanged 9 days agoMITView on GitHub

Reports how a BioFlow link-in-bio page performs and who it captured: views, link clicks, CTR, top links, referrers, tip revenue, newsletter and lead signups, contacts, and uploaded files. Use when the user asks 'how did my page do last month', 'who signed up through my page', 'which links get the most clicks', 'where does my traffic come from', 'show my bio link analytics', or 'list my leads'. Read-only.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 3 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the workspace's analytics, captured leads, and uploaded files, and turn them into a short, honest report.

    line 9
  2. Very specific:

    Every tool in this skill comes from the bioflow MCP server, the BioFlow connector, and is written here as bioflow:<tool>.

    line 13
  3. Very specific:

    Tools listed by name: call them directly, for example bioflow:page.list.

    line 15
  4. Very specific:

    If the user asks about signups or leads, call bioflow:contacts.list and give the count, the split by capture method, and the most recent …

    line 31
  5. Very specific:

    If the user asks about files or gated downloads, call bioflow:file.list and list the files by name.

    line 32
  6. Distinctive:

    Only report numbers the tools returned.

    line 37
  7. Distinctive:

    Do not compare against industry benchmarks.

    line 38

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
<!-- Generated from plugins/bioflow/skills/analyzing-page-performance/SKILL.md by scripts/sync-skills.mjs. Edit the plugin copy, then run the script. -->

BioFlow page insights

Read the workspace's analytics, captured leads, and uploaded files, and turn them into a short, honest report. Read only.

Connecting and calling the tools

Every tool in this skill comes from the bioflow MCP server, the BioFlow connector, and is written here as bioflow:<tool>.

  • Tools listed by name: call them directly, for example bioflow:page.list.
  • Only bioflow:search_tools and bioflow:execute_typescript listed (Code Mode, the default): call bioflow:search_tools first, then call each tool inside bioflow:execute_typescript as external_ plus the tool name with dots swapped for underscores (for example external_page_list for bioflow:page.list); the program must return its result. Scopes, confirmations and gates are identical on both surfaces.
  • "Tool not found": switch to the Code Mode route instead of retrying the direct call. If bioflow:search_tools does not return the tool either, its OAuth scope was not granted; the user reconnects BioFlow and approves that scope.
  • No bioflow tools at all: BioFlow is not connected yet. Follow the setup-bioflow skill.

Tools you will use

  • bioflow:analytics.summary: aggregated views, clicks, CTR, top links, referrers, and tip revenue for the workspace.
  • bioflow:contacts.list: the leads the page has captured, with how each was captured (for example a newsletter signup or a file gate).
  • bioflow:file.list: the files uploaded to the account.
  • bioflow:page.list: page names and public URLs, so numbers can be tied to a page.

Workflow

  1. Agree the window (default: the last 30 days). Call bioflow:analytics.summary for it.
  2. Report in this order: views, clicks, CTR, the top links with their click counts, the top referrers, then tip revenue if there is any.
  3. If the user asks about signups or leads, call bioflow:contacts.list and give the count, the split by capture method, and the most recent entries.
  4. If the user asks about files or gated downloads, call bioflow:file.list and list the files by name.
  5. Close with at most three concrete suggestions drawn from the numbers, such as moving the most clicked link higher. Offer the editing-page-drafts skill to make the change.

Rules

  • Only report numbers the tools returned. If a metric is not in the response, say it is not available.
  • Do not compare against industry benchmarks; there are none in the data.
  • Contacts are personal data. Show only what the user asked for, and do not copy the full list into the chat unless they ask.
  • This skill only reads. Never call bioflow:page.create, bioflow:page.update_draft, bioflow:page.add_block, bioflow:page.remove_block, bioflow:page.reorder_blocks, bioflow:page.publish, or bioflow:page.schedule_publish from it.

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.