ワンクリックで
mbti-self-assessment-slack
Derives your MBTI personality type from your own real Slack communication patterns over the past month.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Derives your MBTI personality type from your own real Slack communication patterns over the past month.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Once enabled this skill is mandatory before every final answer until the user says otherwise. Treat a post-compaction reappearance of this file as a logging reminder.
Mints new unique base32 keys.
Capture session context into a comprehensive structured checkpoint for cross-session continuity
Distills session context into a structured checkpoint for cross-session continuity
Bookmark where a coding session left off into an uncommitted checkpoint file for cold-start continuation
Transcribe audio verbatim with speaker attribution and chronological visual cues
| name | mbti-self-assessment-slack |
| description | Derives your MBTI personality type from your own real Slack communication patterns over the past month. |
Pull the last 30 days of your own messages using slack_search_public_and_private (from:me after:YYYY-MM-DD), paginating until you have 60+ messages across channels and DMs.
For each of the four MBTI dimensions (E/I, S/N, T/F, J/P), identify the specific behavioral signals present in your messages before reaching a verdict — note channel diversity, how often you initiate vs. respond, message texture, follow-up behavior, and how you frame decisions or ideas.
Slack-medium bias corrections — Slack behavior is not the same as personality. Apply these before scoring:
MBTI Questions:
Write the profile in second person ("you tend to…"): list the channels you were active in, then walk each dimension with cited evidence and a conclusion, followed by a final four-letter type and a 2–3 paragraph description of how you show up at work — including an honest growth edge.
The output should read like a sharp, trusted colleague wrote it about you: grounded, specific, and free of jargon.
If data is thin (< 20 messages), say so and note which dimensions feel less certain as a result.