Short answer: in one scripted new-owner run per skill, Stop the Calls reached a filled stop-request letter in under 10 seconds of machine time and passed. Chase the Invoices dead-ended because the shipped skill had no follow-up step, and the blogging skill worked but was hard to find. Small sample, n=1 per skill.
Why test the three skills as a new owner?
MCAFax now treats three skills as its primary products: Stop the Calls, Chase the Invoices, and the blogging system. The goal is for business owners to find and use them. Nothing in production logs time to first result yet, so this test measures it directly, once, the way a new visitor would meet each skill.
What did we expect to find?
Jan's hypothesis: a new owner cannot complete Chase the Invoices or the blogging system from the homepage today, and Stop the Calls is reachable only on the second click, because the nav item opens the article series.
How was the run done?
- A scripted browser (Playwright, headless Chromium) started at https://mcafax.com/ and clicked only visible links. It ran at 1280x800 with video and again at 375x812 (mobile).
- Each click's label, the resulting URL, and the HTTP code (including redirects) were recorded.
- Each skill zip was downloaded, opened, and checked for a SKILL.md with a name and description.
- For the first result, the skill's own instructions were followed on a fictional example, all locally:
- Stop the Calls: fill the bundled stop-request letter.
- Blogging: run the Pam skill's steps 1 to 3 up to a draft held for the owner's yes.
- Chase the Invoices: look for a follow-up step.
- The clock ran from homepage load until the first result was written.
- No forms were submitted. No accounts were created, nothing was paid for, and no email was sent.
- Runs took place on 2026-11-11 between 13:27 and 13:30 Asia/Jerusalem time.
What happened on each skill?
| Skill | Click path (desktop) | HTTP codes | Clicks to skill file | First result | Time desktop / mobile | Verdict |
|---|---|---|---|---|---|---|
| Stop the Calls | "Stop the Calls" (nav) > "Look up who's calling" > "Install the one MCAFax Finance skill (all modes)" | / 200; /stop-broker-calls 301; series 200; /stop-calls 200; /skills/finance.zip 200 | 3 (product page on 2) | Filled stop-request letter, 0 placeholders left | 9.47 s / 7.96 s | PASS |
| Chase the Invoices | "Oscar Grants" > "Skills" (footer) > "Download skill (.zip)" | / 200; /oscar 200; /skills 200; /skills/finance.zip 200 | 3 | None. The skill has no chase or follow-up step | Dead end at 10.24 s / 8.48 s | FAIL |
| Blogging system | "Pam Notebook" > "Skills" (footer) > Pam "Download skill" | / 200; /pam 200; /skills 200; /home/skills/mcafax-team-pam.zip 200 | 3 (2 if the visitor starts from the footer) | Sourced draft stub held for the owner's yes. The prose needs an AI assistant | 6.75 s / 6.87 s | FAIL (findability) |
What each run showed:
- Stop the Calls
- The zip is valid: 45 files, and finance/SKILL.md has a name and description.
- The bundled letter filled cleanly.
- On desktop, hovering the nav item opens no submenu. The first click lands on the series, and the product is one click further.
- INSTALL.md gives only Claude-style folder paths. It has no step for ChatGPT.
- Chase the Invoices
- No page on the path uses the name.
- /oscar has no download and no invoice text.
- The shipped finance skill (v1.6) has no invoicing file. Its only invoice guidance is a single line: "who, what, amount, date, and terms."
- The routing rule for "unpaid invoice" points to a bank-statement article (200). That article contains no invoice text.
- Blogging system
- The Pam zip is valid.
- /pam has no download link and never says "blog."
- On /skills, the only use of "blog" is the finance skill's "do not use: write a blog post."
- The skill is usable once found, but it is a 4-step prompt that needs Claude or ChatGPT to write the draft.
Hypothesis outcome:
- Chase the Invoices: held.
- Blogging system: partly held. The obvious path dead-ends and the product is never named, but the skill can be reached through the footer "Skills" link and it works.
- Stop the Calls: held for the product page, which is click 2. The skill download is click 3.
What does this test not prove?
- The sample is small: n=1 run per skill per viewport, from one network location, on one day.
- Times are scripted machine time. They leave out human reading time, unzipping by hand, installing into an AI assistant, and the AI's own drafting time, so real owner times will be longer.
- The first results used fictional data and a script in place of an AI assistant. The blogging draft is a stub, not a finished article.
- The caller lookup on /stop-calls was not used, because it would have meant submitting a form.
- No usage numbers are reported. None were measured in this test.
What gets re-tested next week?
- Re-run the same script after the planned homepage Products block and the Stop the Calls nav fix ship. Compare clicks and time.
- Re-test Chase the Invoices once a public home and an invoicing mode are live.
- Add a timed human pass, installing into a real AI assistant, to measure owner time and not just script time.
Where to go next
Try the skills yourself at Stop the Calls and Chase the Invoices. Contractors looking at funding can start with the contractor funding guide.
Disclosure
MCAFax may receive compensation from some providers. It does not affect our grades or what we show you.
