Recently updated open-source projects

Uri reviews products and decisions against three stages: problem-solution fit, product-market fit, and scale. It uses retention curves, the Sean Ellis 40% test, push-versus-pull signals, a 10x value test, and Lean Canvas assumptions to identify missing evidence. Each critique ends with a concrete next validation step so a team can test demand before committing more money to growth.

Boris reviews SaaS tools, APIs, automations, and AI agents as a fractional CTO, looking for duplicated capabilities, unnecessary complexity, failures, and runaway token spend. It rates proposed changes by feasibility, dependencies, security surface, and build time, while delegated agents scout platform changes, monitor scheduled jobs, and build or retire agents when a concrete operational gap is found.

Richard applies Rumelt's strategy kernel to separate a clear diagnosis, an excluding guiding policy, and actions that reinforce one another. It flags fluff, goals masquerading as strategy, scattered stakeholder compromises, and distant objectives, scores sprint tasks against the guiding policy, and compares actual metrics with targets. Daily resource-allocation checks cover time, capital, agents, knowledge, assets, relationships, and attention, while the weekly review realigns the next week's work.

Anthony reads CRM records, call transcripts, and campaign metrics to score conversations across preparation, value created, commitment gained, one-up positioning, and follow-through. It then uses pipeline math to choose the most important deal to advance and delegates prospecting, pipeline, cold-delivery, value-first, and inbound work to specialized agents. Notion, Discord, and Granola are required for the documented setup.

Run a project, decision, or team meeting through six timed stages: purpose, principles, vision, brainstorm, organization, and next actions. The roughly eleven-minute structure keeps one discussion phase from consuming the rest and ends with concrete, owned, dated actions. The plain Markdown skill can be installed in Claude Code or adapted to other agent runtimes.

Use natural-language requests to send, check, forward, or bulk-deliver SMS and RCS messages through a mobile messaging interface. The skill covers text and template messaging, with support described for richer media and interactive cards. It is intended for agent workflows and requires Python 3.6 or newer, the requests library, and valid APP_ID and APP_SECRET credentials.

Describe a product or service and the skill generates candidate brand names, checks default and custom TLDs in real time, then ranks the shortlist by availability, length, pronunciation, and meaning. It is aimed at founders and indie makers who want to shorten the naming loop. A local whois command is required, and some .app or .dev results rely on best-effort DNS checks.

Shiplog watches Git commits to discover features, update progress, and retain architecture decisions and coding patterns so a new Claude Code session can continue without a full re-explanation. After each commit it can run background agents for specs, PRD status, security review, and memory. Both freeform and planned tracking modes are available, all records stay local, and the project must use Git.

Start a persistent persona with the slash command or trigger the skill from phrases asking for a cheesy Chinese pickup line. It can weave a person’s name, job, or situation into puns, reversals, and playful questions, making it useful for casual entertainment or message inspiration. Installation differs between Claude Code and OpenClaw, and explicit exit phrases immediately end the role-playing mode.

The skill classifies a project as a local tool, full-stack product, automation agent, AI web app, or mobile app, asking only a few questions when needed. It previews the folder tree and key files before writing, then creates CLAUDE.md, an initial build prompt, dependency files, environment templates, and a numbered prompt chain for later work.

Give the CLI an EXE or DLL and one or more virtual addresses to translate them into file offsets and print aligned x86-32 linear disassembly for inspection or Claude-assisted analysis. It uses pefile and Capstone, assumes addresses relative to the static ImageBase, and deliberately omits symbols, control-flow recovery, decompilation, and PDB parsing.

With ProLine Partner API access, an agent can create leads, book inspections, move deals through stages, write project notes, and look up team members. The repository also syncs CRM data into local SQLite for reporting and deal-quality scoring and includes weather-based rain-day decisions; both partner and company credentials are required, and several API operations remain blocked or nonfunctional.

This template combines Electron, Vite, Vue 3, and TypeScript into a minimal desktop application starter. After cloning and installing dependencies, developers can run a live development window, preview a production build, or package the app with the included scripts. It also supplies Electron main and preload process examples, electron-builder settings for macOS and Windows, and a VS Code configuration for debugging the main process.

Provide a comma-separated company list and the skill searches official sites, brand pages, image search, and Wikipedia in parallel. It visually checks identity, current branding, colors, and whether a full wordmark is available before saving verified files locally. It does not require a logo-service API key.

Feed it chats, social posts, photos, and your own context to map the relationship timeline, estimate its direction, and suggest practical next moves. It is designed for reflection around crushes, mixed signals, or cold spells, not as professional counseling, and it declines serious abuse or self-harm scenarios.

Give it an HTML file or folder to capture desktop, mobile, and optionally tablet viewports, then combine the normalized panels into one PNG or JPEG. A temporary local HTTP server preserves relative CSS, scripts, images, and fetch calls, while full-page capture, batch processing, separate device files, and custom backgrounds are available.

Starting from a vague idea, the skill asks one question at a time about the goal, reason, and definition of done before producing a structured brief that can be copied or saved in the project. Quick, standard, and deep modes add different levels of detail, and unanswered essentials are left as gaps rather than silently invented.

Say “save this” at the end of a Claude Code discussion and knowledge-capture extracts the topic, three to five takeaways, reusable rules, and open questions. It detects available destinations such as Notion through MCP, an Obsidian vault, or a local Markdown inbox, shows the proposed note, asks where to store it, and returns the resulting path or link. Local Markdown works without an external knowledge-base integration.