Thrunt Profile User

Name: Thrunt Profile User
Author: backbay-labs

ASecurity

Generate developer behavioral profile and create Claude-discoverable artifacts

36 stars
0 votes
0 copies
1 view
Added May 28, 2026

ai-agentsgobashgit

Security analysis

A100/100

Scanned May 28, 2026

npx -y skills add backbay-labs/thrunt-god --skill thrunt-profile-user --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Thrunt Profile User?

Add the live security badge to your README. It updates with every re-scan.

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/backbay-labs-thrunt-profile-user/badge)](https://www.skillsdirectory.com/skills/backbay-labs-thrunt-profile-user)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

---
name: thrunt-profile-user
description: Generate developer behavioral profile and create Claude-discoverable artifacts
argument-hint: "[--questionnaire] [--refresh]"
allowed-tools: Read, Write, Bash, Glob, Grep, AskUserQuestion, Task
---


<objective>
Generate a developer behavioral profile from session analysis (or questionnaire) and produce artifacts (USER-PROFILE.md, /thrunt-dev-preferences, copilot-instructions.md section) that personalize the agent'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>
@.github/thrunt-god/workflows/profile-user.md
@.github/thrunt-god/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:
1. Initialization and existing profile detection
2. Consent gate before session analysis
3. Session scanning and data sufficiency checks
4. Session analysis (profiler agent) or questionnaire fallback
5. Cross-project split resolution
6. Profile writing to USER-PROFILE.md
7. Result display with report card and highlights
8. Artifact selection (dev-preferences, copilot-instructions.md sections)
9. Sequential artifact generation
10. Summary with refresh diff (if applicable)
</process>