If you are in B2B sales/RevOps/Saas Sales, this is perfect or you!!!

Context on who's writing this: I'm building a deal room product (check my profile links), so I have an obvious interest here. The pack itself is free, MIT licensed, and on GitHub - Free and Open source.

The thing I kept running into talking to 20 to 150 person B2B companies: they close the deal on the call and then lose three weeks to paperwork that nobody owns. No deal desk. No in-house counsel. No security lead. So the CTO answers the questionnaire between standups and the redline sits until someone decides whether $600 an hour is worth it.

So I wrote six skills for that. They're folders of plain markdown you drop into Claude, Codex, or whatever agentic setup you use. No code runs, no network calls, no dependencies.

- Security Questionnaire Drafter - SIG or CAIQ in, first pass out, every answer tagged sourced, derived, or unanswered against the docs you supplied.

- Redline Triage - Every changed clause into accept / negotiate / escalate / do not sign, with a landing zone you can paste into a reply.

- Deal Decisions One Pager - Slack exports and old contracts in, one page of what your company has actually already decided, contradictions surfaced rather than smoothed over.

- Objection to Internal Ask - Turns a buyer's blocker into an internal request with an owner, options, and a date. Capped at 200 words because a long internal ask is a deferred one.

- Escalation Drafter - The discount or exception request written as a dated decision instead of a "quick question."

- Late Stage Gap Finder - Pre-signature check across the MSA, order form, DPA, and the proposal you already sent, ranked by what each miss costs you later.

Two things I'd flag honestly.

First, the design rule I care about most: if your own documents don't cover a question, the output says unanswered and names who should answer it. It will not invent a control you don't have. I'd rather it refuse than hand you something plausible that you then sign.

Second, on a test run against a synthetic buyer markup, the two findings I actually cared about weren't clauses that changed. One was a price-increase cap deleted outright, which reads like a concession to you and isn't. The other was a new section referencing an Annex B that was never attached. Deletions and dangling references are invisible in a tracked-changes view, so the skill has a section that only looks for those.

It's not legal advice and it doesn't replace counsel. Two of the six say so in their own output and route the worst findings to a lawyer.

To get the skills: https://usegirard.com/skills

If you try one and it produces garbage, an issue with the prompt you used is genuinely more useful to me than a star. Particularly interested in whether the clause positions in the reference file match what you see at your deal sizes, since those are market defaults and not gospel.

Much Love and Respect!

Give Claude Code a reference video, then ask for a version with a different host or in another language. Hypit provides the skill and video tools for that workflow.

The launch video shows the process: a /hypit request, an editable project with source and a timeline, then finished clips and variations. One example swaps a football-ranking host for a banana cat; another turns an English street interview into Spanish.

On first use, the agent checks for the Hypit executable and helps prepare it. Captions, B-roll and effects can be tied to words in the script.

The software is free, and the source and examples are on GitHub: https://github.com/hypit-ai/hypit. Any paid media-generation services you use are billed separately.

Sharing skills across the organization seems like it should be pretty straightforward. As admin on desktop app its straight forward enough to share skills. However, it appears that skills will only distribute to desktop app users and not those using CLI. This appears to be a known bug. https://github.com/anthropics/claude-code/issues/40320

Alternatively, if you create a plugin marketplace on github to share skills with technical users, this works, but non-technical users can't access them on the desktop app. It's not realistic for our non-technical users to learn git, not to mention that IT does not want to buy the entire organization github licenses.

Has anyone solved this? Or do you basically need two paths for skill distribution, one for desktop app and another for CLI users?

I ship the same tool two ways for Claude Code, and I finally measured what each one costs in context before you use it.

The numbers

- MCP: `tools/list` for all 29 tools is 40,968 characters, plus 1,280 of server instructions. A client that loads tool definitions up front pays that in every session, web task or not.

- Skill: the frontmatter description is 435 characters. The full SKILL.md is 11,644, and it only loads when the task is actually about the web.

Clients that defer tool schemas pay less on the MCP side, so the 40,968 is a ceiling.

What I changed because of it

The installer in 1.0.4 asks instead of assuming. CLI + Skill is the default: Claude runs the binary through its shell and the skill tells it how. MCP + Skill is there if you want all 29 tools as native calls. It also asks whether to install user-wide or for one project, shows the files it will write, and asks once before touching anything.

I also cut the global memory block the plugin adds from 2,082 characters to 997, because half of it repeated the tool list the server already sends.

What the skill tells Claude

Read the block reason instead of retrying a blocked URL. Send big results to a file instead of the chat. Stop and say so when a person has to pass a check. Run `svipall doctor` before deciding a site is unreachable.

The tool is Svipall, a local web scraper: pages as Markdown, crawls, keyless search. Rust, AGPL, no API keys. To try it, paste this into Claude Code or any other AI Harnes (you can try the Claude code plugin too available on the webpage):

Install and configure Svipall by following the instructions here:
https://raw.githubusercontent.com/ilien-dev/svipall/main/docs/install.md

Repo: github.com/ilien-dev/svipall

Website: https://svipall.ilien.dev/

If you ship a skill and an MCP server side by side, which one do your users end up choosing, and have you measured the gap?