pasky

Stars and mentions

Last 30 days, Oct 4 – Nov 2

GitHub stars11
mentions2
01234Oct 4Oct 18Nov 2
UTC days · repositories pasky owns3 repositories

Package downloads

Cumulative recorded downloads · since 2025-10-19

npm6.5K
01.6K3.3K4.9K6.5KOct 4Oct 18Nov 2
Oct 27npm: 1/2 packages observed

Across 2 known packages in repositories pasky owns. Cumulative totals include recorded downloads before the selected range. Missing observations leave gaps; totals may be incomplete.

Top repositories

pasky’s repositories ranked by pull request authors, as on trending.

Loading

Contributes to

Repositories outside pasky’s account where pasky opened or reviewed pull requests in the past 365 days.

Who noticed pasky

Everyone who starred or forked pasky’s repositories since the archive began in 2011.

Notable accounts

Ordered by the stars their own repositories have received.

Biggest fans

Accounts that starred the most of these repositories.

Breakout weeks

Each repository’s best week of new stars, with the release published around it.

Mentions

2posts
Nov 30 posts
  1. Reddit · · r/Playwright · u/parallelit · pasky/chrome-cdp-skill

    Best approach to generate production-ready Playwright scripts for ~10 heavily customized Salesforce-based CRMs? Ciao everyone, I'm working on a project to automate order creation on our suppliers' CRM portals. Most of them are built on Salesforce, but each one is heavily customized, so the flows differ a lot from one supplier to another. The flows are long and multi-step: an experienced user takes about 5–8 minutes per order, mostly copying and pasting data from our internal CRM into the supplier's portal. We handle around 50 orders a day. I started writing Playwright automations with codegen, but development is very slow, and I have around 10 different supplier CRMs to cover. Some context and constraints: - No APIs: the suppliers don't provide or allow API access, so UI automation is the only option. - Authentication is solved: MFA is handled programmatically via TOTP, no issues there. - Portals are stable: the UIs rarely change, so a deterministic script would stay valid for a long time once written. - Why not RPA: I'm comfortable with Playwright, and the UiPath quote I received was far beyond our budget. - Stack is open: I'm not tied to a language, and I'm even open to alternatives to Playwright if there's a better fit. So far I've tried generating the Playwright code with: - browser-use harness - Playwright MCP - Stagehand by Browserbase - Browserbase Agent - Claude Chrome Extension - chrome-cdp-skill With very specific prompts that force the AI through the task step by step, most of these tools can complete the flow. But that's not really what I need: I want the AI to perform the task once, "look" at how the pages are built, and output a deterministic Playwright script I can run in production without an LLM in the loop. The generated code has been consistently poor: brittle selectors, reliance on Salesforce's dynamic IDs, badly handled waits, and missing steps. Getting it production-ready takes a huge number of iterations, which defeats the purpose. Has anyone tackled something similar? I'd love to hear how you'd approach this differently, whether that's a different tool, a better workflow (e.g. recording plus AI refactoring, page object generation), or tips specific to Salesforce UIs. Anything that speeds up writing reliable Playwright code would help. Thanks!

    1 point · 2 comments
  2. This /board skill has been working pretty well for me in @badlogicgames's @pidotdev to have multiple models (Fable+Astra+Argon in my case) hash something out: github.com/pasky/pi-agent-config/blob/main/skills… (Tell your pi to remix it for your multi-agent setup of choice, ootb it's pi-side-agents.) t.co

    1 like · 196 views
Trending awards, every completed day and week
Gold
01st place finishes
Silver
02nd place finishes
Bronze
03rd place finishes
Awarded repositories
0Owned by pasky now

No trending awards yet

None of the repositories pasky owns has finished in the top three of a completed trending day or week, by stars, forks or PR authors. See who is trending now.

A repository earns an award for finishing first, second or third in a completed trending day or week, ranked by new stars, new forks or pull request authors. Awards follow a repository through renames and transfers and count toward its current owner. Weeks run Monday to Sunday, UTC.