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.
In this repository66 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- adding-uptime-monitorsSkill
- booking-meetingsSkill
- building-onboarding-workflowsSkill
- building-study-guidesSkill
- capturing-tasksSkill
- capturing-web-pagesSkill
- chasing-unpaid-invoicesSkill
- checking-domain-connectionsSkill
- checking-email-deliverabilitySkill
- checking-notification-deliverySkill
- checking-uptime-statusSkill
- cleaning-up-bookkeepingSkill
- connecting-customer-domainsSkill
- discussing-buildsSkill
- drafting-invoicesSkill
- drafting-social-postsSkill
- editing-demosSkill
- editing-page-draftsSkill
- extracting-document-textSkill
- finding-meeting-timesSkill
- handling-flaky-changesSkill
- investigating-tasksSkill
- making-demo-videosSkill
- managing-bookingsSkill
- managing-content-calendarSkill
- managing-demosSkill
- managing-voice-librarySkill
- planning-revisionSkill
- preflighting-domainsSkill
- publishing-pagesSkill
- reading-financial-reportsSkill
- reading-text-aloudSkill
- reading-web-pagesSkill
- reporting-snapvisor-usageSkill
- researching-course-materialSkill
- researching-summary-librarySkill
- responding-to-incidentsSkill
- reviewing-email-performanceSkill
- reviewing-notification-workflowsSkill
- reviewing-social-performanceSkill
- reviewing-visual-buildsSkill
- reviewing-workloadSkill
- searching-getitdone-api-docsSkill
- sending-email-campaignsSkill
- sending-notificationsSkill
- setup-bioflowSkill
- setup-calySkill
- setup-demofySkill
- setup-dodomainSkill
- setup-getitdoneSkill
- setup-notiflySkill
- setup-postifySkill
- setup-sendlySkill
- setup-shortySkill
- setup-snapvisorSkill
- setup-superbooksSkill
- setup-unotesSkill
- setup-upapiSkill
- setup-uptimelySkill
- The first 60 shown.
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
- Distinctive: line 9
Read the workspace's analytics, captured leads, and uploaded files, and turn them into a short, honest report.
- Very specific: line 13
Every tool in this skill comes from the bioflow MCP server, the BioFlow connector, and is written here as bioflow:<tool>.
- Very specific: line 15
Tools listed by name: call them directly, for example bioflow:page.list.
- Very specific: line 31
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 …
- Very specific: line 32
If the user asks about files or gated downloads, call bioflow:file.list and list the files by name.
- Distinctive: line 37
Only report numbers the tools returned.
- Distinctive: line 38
Do not compare against industry benchmarks.
≈ “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.
Files
<!-- 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_toolsandbioflow:execute_typescriptlisted (Code Mode, the default): callbioflow:search_toolsfirst, then call each tool insidebioflow:execute_typescriptasexternal_plus the tool name with dots swapped for underscores (for exampleexternal_page_listforbioflow:page.list); the program mustreturnits 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_toolsdoes not return the tool either, its OAuth scope was not granted; the user reconnects BioFlow and approves that scope. - No
bioflowtools at all: BioFlow is not connected yet. Follow thesetup-bioflowskill.
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
- Agree the window (default: the last 30 days). Call
bioflow:analytics.summaryfor it. - Report in this order: views, clicks, CTR, the top links with their click counts, the top referrers, then tip revenue if there is any.
- If the user asks about signups or leads, call
bioflow:contacts.listand give the count, the split by capture method, and the most recent entries. - If the user asks about files or gated downloads, call
bioflow:file.listand list the files by name. - Close with at most three concrete suggestions drawn from the numbers, such as moving the most clicked link higher. Offer the
editing-page-draftsskill 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, orbioflow:page.schedule_publishfrom it.
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
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.

