Dev like

Skill marcusrbrown/dev-like/skills/dev-like

Profile a tech company or developer's engineering culture from public sources and generate a develop-like-<target> skill that makes the agent work the way they do. Use when the user invokes /dev-like <target>, asks to "develop like <company>", "code like <person>", "adopt <shop>'s engineering practices", or wants a dev-culture profile of a company, team, or individual developer.From its SKILL.md

Install

npx -y skills add marcusrbrown/dev-like --skill dev-like

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.9 KB, 566 tokens by cl100k_base, as published. Nobody here has run it

dev-like

Turn a shop's public engineering exhaust into an installable develop-like-<slug> skill, with a source citation for every claim.

Target: $ARGUMENTS (if empty, ask the user who they want to develop like).

Workflow

1. Resolve

Fetch the registry index and resolve the target against slugs and aliases (case-insensitive):

https://raw.githubusercontent.com/marcusrbrown/dev-like/main/registry/index.json

Every → every; theo.gg, t3.gg, Theo Browne → theo. If ambiguous, ask.

2a. Cache hit → install

Fetch registry/<slug>/profile.md and registry/<slug>/entry.json (same raw URL base).
Tell the user the profile date, consent tier, and top sources before applying anything.
Generate the develop-like-<slug> skill from the profile — follow references/distilling.md.
Write it to .agents/skills/develop-like-<slug>/ and mirror into .claude/skills/ if the project uses Claude Code (symlink preferred, copy fallback). See references/harnesses.md for other harnesses.
Offer the optional <slug>-developer reviewer/pair agent persona.

2b. Cache miss → collect, distill, contribute

Tell the user this target is uncached and a live profile takes a few minutes. Confirm.
Run the collection workflow — follow references/profiling.md. Public sources only, official APIs preferred, every claim gets a source URL.
Distill into profile.md + entry.json per references/distilling.md.
Generate and install the skill as in 2a.
Offer to PR the new profile back to the registry — follow references/registry.md. This is opt-in, never automatic.

Hard rules

Every claim in a profile or generated skill carries a provenance link. No source, no claim.
Individuals (kind: person) require stated-tier sources or better — never build a person's profile purely from social posts. Orgs may use the full source taxonomy.
Extract principles, workflows, and stack facts. Never reproduce prose beyond quotation scale.
Check registry/OPTOUT.md before profiling anyone; a listed target is a hard stop.
State the profile date in the generated skill: cultures drift, receipts age.

What ships with it: 8 files

10.7 KB alongside SKILL.md