borghei/Claude-Skills / tools/linkedin/linkedin-humanizer
linkedin-humanizer
VerifiedAudits and rewrites LinkedIn drafts to remove machine-sounding patterns: tiered tell catalogue, emoji-pattern scoring, rule explanations, and a voice fingerprint built from the author's own posts. Use when a draft reads generated, before publishing, or when an edit flattened someone's voice.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 17.9 KB |
| assets/audit_report_template.md | markdown | 2.3 KB |
| assets/sample_draft.txt | markdown | 1.0 KB |
| assets/sample_draft_edited.txt | markdown | 1.1 KB |
| assets/sample_past_posts.txt | markdown | 2.7 KB |
| assets/sample_voice.json | config | 899 B |
| assets/voice_profile_template.md | markdown | 3.0 KB |
| references/emoji-patterns.md | markdown | 7.4 KB |
| references/rewrite-playbook.md | markdown | 12.0 KB |
| references/rule-catalogue.md | markdown | 19.4 KB |
| references/voice-fingerprint-guide.md | markdown | 9.7 KB |
| scripts/emoji_audit.py | script | 8.6 KB |
| scripts/tell_audit.py | script | 10.8 KB |
| scripts/tell_rules.py | script | 17.5 KB |
| scripts/voice_fingerprint.py | script | 11.1 KB |
assets/sample_draft_edited.txt
View on GitHubOur median time from signup to first shipped label was 9 days in January. It is 2 days now, and the change that did most of the work was deleting things.
I run onboarding at Tidewell. In February Maren Okafor on our support team pulled 60 onboarding calls and tagged the minute each customer first went quiet. In 41 of them it was the same screen: the carrier-rates table, which asked for seven fields before you could print anything.
We'd built that table because enterprise buyers asked for it during sales calls. New accounts with three staff and one warehouse didn't need it, and they couldn't skip it.
So we made it optional and pre-filled the two fields we could guess from the postcode. That took Isak four days. Nothing else we shipped this quarter moved the number by more than half a day, including the guided tour I'd argued for since last autumn (I was wrong about the tour).
What we haven't solved: accounts that connect a second warehouse still stall at about the same rate as before, and I don't know why yet.
If you've cut an onboarding step and seen activation get worse, I'd like to hear which step it was.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |