mcpbeat

Gsd Profile User

coco-research/gsd-profile-user

Generate developer behavioral profile and create Claude-discoverable artifacts

405 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
196
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/coco-research/coco --skill gsd-profile-user

The instruction itself

as written by the author

<objective>

Generate a developer behavioral profile from session analysis (or questionnaire) and produce artifacts (USER-PROFILE.md, /gsd-dev-preferences, CLAUDE.md section) that personalize Claude's responses.

Routes to the profile-user workflow which orchestrates the full flow: consent gate, session analysis or questionnaire fallback, profile generation, result display, and artifact selection.

</objective>

<execution_context>

@$HOME/.claude/get-shit-done/workflows/profile-user.md

@$HOME/.claude/get-shit-done/references/ui-brand.md

</execution_context>

<context>

Flags from $ARGUMENTS:

  • --questionnaire -- Skip session analysis entirely, use questionnaire-only path
  • --refresh -- Rebuild profile even when one exists, backup old profile, show dimension diff

</context>

<process>

Execute the profile-user workflow end-to-end.

The workflow handles all logic including:

  • Initialization and existing profile detection
  • Consent gate before session analysis
  • Session scanning and data sufficiency checks
  • Session analysis (profiler agent) or questionnaire fallback
  • Cross-project split resolution
  • Profile writing to USER-PROFILE.md
  • Result display with report card and highlights
  • Artifact selection (dev-preferences, CLAUDE.md sections)
  • Sequential artifact generation

10. Summary with refresh diff (if applicable)

</process>

How to use it

Copy the folder

Take coco-research/gsd-profile-user from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.