actor-profiling

Featured

Understand who the user is — background, resources, constraints, and deep motivations. Produces an ActorProfile that informs all downstream decisions. Use this tactic at the start of any crystallization process to build a model of the user's capabilities, limitations, and intent.

AI & Automation 501 stars 41 forks Updated yesterday Apache-2.0

Install

View on GitHub

Quality Score: 93/100

Stars 20%
90
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Actor Profiling Build a comprehensive model of the user as a research actor — who they are, what they have, what constrains them, and why they're doing this. ## Available SOPs | SOP | Purpose | Execution | |-----|---------|-----------| | explore-resume | Background, skills, projects, publications, research experience | dialogue (once only) | | clarify-resources | Compute, timeline, collaboration, data, environment | dialogue | | ask-constraints | Venue targets, methodology preferences, avoidance areas, advisor requirements | dialogue | | ask-intentionality | Deep WHY probing — motivation, risk tolerance, innovation preference, etc. | dialogue | ## Methodology Guidance The goal is to construct an ActorProfile with enough information to inform field exploration and goal decomposition. How you get there is your decision. **Typical flow:** 1. `explore-resume` first (one-time, never re-run) 2. `clarify-resources` → `ask-constraints` → `ask-intentionality` **But you may:** - Return to `ask-intentionality` at any point when you discover a deeper WHY to probe - Interleave `clarify-resources` when intentionality probing reveals resource-related gaps - Skip or abbreviate SOPs when the user's initial message already provides the information **End condition:** You judge that you have enough information to construct a meaningful ActorProfile. In cold-start scenarios, "enough" may mean just establishing boundaries (what the user won't do) rather than specifics. ## Cold-Start Spe...

Details

Author
yogsoth-ai
Repository
yogsoth-ai/de-anthropocentric-research-engine
Created
7 months ago
Last Updated
yesterday
Language
HTML
License
Apache-2.0

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

setup

Build the candidate profile from scratch through a guided interview. Run this first, before any other skill. Populates profile/*.md and career_facts.yaml.

1 Updated 1 months ago
HimadriTrying
AI & Automation Listed

opportunity-brief

Research a company and a specific role, then produce an honest brief on whether it is worth pursuing. Use this whenever the user mentions a recruiter reaching out, a job posting they found, a company someone told them about, or a role they are weighing. Triggers on "a recruiter contacted me," "should I apply to," "what do you know about [company]," "look into this company," "is this role real," "assess this posting," "vet this opportunity," "a friend mentioned a job at," or when the user pastes a job description, recruiter email, or LinkedIn InMail. Also triggers on "compare these two roles" and "what should I ask the recruiter."

1 Updated 2 weeks ago
btmoriarty
AI & Automation Listed

whoami

A short, conversational interview that builds a portable profile of the user — who they are and how they want to be collaborated with — so the agent can tailor its responses. Triggers on `/whoami`, "get to know me", "set up my profile", "personalize how you work with me", "calibrate how you respond", the user mentioning they are new to AI or switching agent vendors, or a request for their collaboration "character sheet" or player profile. Produces six collaboration dials, an RPG-style class + subclass with a character portrait, a memory profile, and a self-contained HTML character sheet. When a profile exists, bare `/whoami` reviews it and offers to correct or re-run; `/whoami rerun` restarts the interview. Does NOT trigger for project- or task-specific work calibration (use `handshake`), routine memory edits or CRUD (use memory-management), or brand-voice work. `whoami` is person-level and broad; `handshake` is project-level and feeds from it.

1 Updated 1 months ago
sorawit-w