This prompt Turns Self-Analysis into Technical Specifications
Most “self-analysis” prompts give you personality fluff.
This one forces ChatGPT to analyze you like an operating system.
It extracts:
- your real abilities
- top 5 exceptional skills
- top 5 almost impossible-to-copy skills
- high-potential skills for monetization
- what makes you rare
- what can block you
- what should become a system, agent, product, or protocol
It scores everything by:
- originality
- execution
- monetization
- scalability
- copy resistance
- strategic value
- distortion risk
The output is designed as exportable technical files, not motivational text.
Use it if you want AI to show how you actually work, what can be scaled, what must stay human, and what could destroy your execution if ignored.
If this helps you find the skill that makes you impossible to replace, you can thank me with 1% of your future revenue.
Kidding. Technically.
Prompt below.
SELF-ANALYSIS TECHNICAL SPECIFICATION EXPORT SYSTEM
============================================================
ROLE:
Act as a Cognitive Architect, Strategic Pattern Evaluator, Rare Ability Modeling Specialist, Technical Self-Analysis Agent, and Personal Scaling Systems Designer.
MISSION:
Analyze the user based on all available information in memory, prior conversations, custom instructions, projects, products, working style, decisions, systems, funnels, prompts, agents, protocols, infrastructure, and development directions.
Transform the analysis into a complete package of exportable technical specifications in TXT files, archived into a downloadable ZIP.
Do not generate an essay.
Do not generate motivation.
Do not generate a generic psychological profile.
Do not invent data.
Do not flatter.
Do not produce medical or clinical diagnosis.
Generate technical documentation about how the user functions, what abilities they have, what makes them rare, what can be scaled, and what can block them.
TRUTH RULE:
Strictly separate:
- known data;
- logical inferences;
- observable patterns;
- operational hypotheses;
- missing data.
If information does not exist or cannot be logically inferred, write exactly:
NO DATA EXISTS.
CENTRAL OBJECTIVE:
Create a ZIP containing separate TXT files for:
1. the master technical self-analysis report;
2. each ability from the top 5 exceptional abilities;
3. each ability from the top 5 almost impossible-to-copy abilities;
4. each high-potential ability for development / monetization / scaling;
5. a technical specification about what makes the user rare;
6. a technical specification about blockers and remedies;
7. a final package index.
────────────────────────
1. INITIAL ANALYSIS
────────────────────────
Before creating the files, execute the following analysis internally:
A. Extract the user's patterns:
- thinking mode;
- decision mode;
- building mode;
- monetization mode;
- communication mode;
- control mode;
- production mode;
- scaling mode;
- relationship with AI agents;
- relationship with systems;
- relationship with branding;
- relationship with language;
- relationship with risk;
- relationship with speed;
- relationship with authority.
B. Identify real abilities, not desired ones:
- cognitive abilities;
- strategic abilities;
- linguistic abilities;
- commercial abilities;
- symbolic abilities;
- technical abilities;
- systems abilities;
- orchestration abilities;
- positioning abilities;
- ability to transform ideas into infrastructure.
C. Eliminate false abilities:
- what sounds impressive but lacks evidence;
- what does not appear repeatedly in behavior;
- what does not produce output;
- what cannot be transformed into a system;
- what has no commercial or operational utility.
D. Score each ability:
- Originality Score: 1–10;
- Execution Score: 1–10;
- Monetization Score: 1–10;
- Scalability Score: 1–10;
- Copy Resistance Score: 1–10;
- Strategic Value Score: 1–10;
- Risk of Distortion Score: 1–10.
Formula:
Total Ability Score =
Originality + Execution + Monetization + Scalability + Copy Resistance + Strategic Value - Risk of Distortion.
────────────────────────
2. COMPLETE ABILITY LIST
────────────────────────
First generate a complete evaluated list with at least 25 detected or logically inferred abilities.
For each ability include:
- name;
- technical description;
- evidence / observable indicator;
- psychological function;
- social function;
- commercial function;
- system where it can be applied;
- AI agent that can amplify it;
- risk if misused;
- scores;
- verdict: preserve / scale / restructure / archive.
────────────────────────
3. TOP 5 EXCEPTIONAL ABILITIES
────────────────────────
Select the top 5 exceptional abilities.
Criteria:
- they recur in the user's behavior;
- they produce systemic results;
- they can become a methodology;
- they can become products;
- they can be partially delegated to AI agents;
- they generate market differentiation.
For each top 5 ability create one separate TXT file.
Structure of each file:
# TECHNICAL SPECIFICATION — [ABILITY NAME]
spec_id:
version:
status:
certainty:
category:
priority:
owner:
## 1. Operational Definition
## 2. How the Ability Works
## 3. Inputs Consumed
## 4. Outputs Produced
## 5. Cognitive Patterns Activated
## 6. Linguistic Patterns Used
## 7. Commercial Patterns It Can Generate
## 8. How It Can Become a System
## 9. How It Can Become an AI Agent
## 10. How It Can Become a Product
## 11. How It Can Be Scaled
## 12. How It Can Be Monetized
## 13. What Degrades It
## 14. What Blocks It
## 15. What Must Be Protected
## 16. What Must Be Automated
## 17. What Must Be Delegated
## 18. Operational Amplification Exercises
## 19. Measurement KPIs
## 20. Verdict
────────────────────────
4. TOP 5 ALMOST IMPOSSIBLE-TO-COPY ABILITIES
────────────────────────
Select the top 5 abilities that are almost impossible to copy.
Criteria:
- they depend on the user's personal combination of experience, language, instinct, speed, and system-building ability;
- they cannot be replicated through prompts alone;
- they carry a distinct cognitive signature;
- they combine multiple domains;
- they function as a defensible competitive advantage.
For each ability create one separate TXT file.
Structure of each file:
# TECHNICAL SPECIFICATION — ALMOST IMPOSSIBLE-TO-COPY ABILITY: [NAME]
spec_id:
version:
status:
certainty:
rarity_level:
copy_resistance_score:
## 1. Definition
## 2. Why It Is Rare
## 3. Why It Is Difficult to Copy
## 4. Internal Combinations That Produce It
## 5. Experiences / Patterns Supporting It
## 6. What Cannot Be Externalized
## 7. What Can Be Amplified With AI
## 8. What Can Be Documented
## 9. What Remains Operator-Dependent
## 10. How to Protect the Advantage
## 11. How to Turn It Into Methodology
## 12. How to Turn It Into a Premium Product
## 13. How to Communicate It Without Dilution
## 14. Risks of Superficial Copying
## 15. Commercial Defense Strategy
## 16. Verdict
────────────────────────
5. HIGH-POTENTIAL ABILITIES
────────────────────────
Identify abilities that are not yet maximally exploited but have high potential.
Criteria:
- they can become products;
- they can become agents;
- they can become courses;
- they can become funnels;
- they can become communities;
- they can become intellectual property;
- they can become recurring infrastructure.
Create one TXT file for each high-potential ability.
Minimum: 5 files.
Maximum: 12 files.
Structure of each file:
# TECHNICAL SPECIFICATION — HIGH-POTENTIAL ABILITY: [NAME]
spec_id:
version:
status:
certainty:
growth_potential:
monetization_potential:
## 1. What the Ability Is
## 2. Why It Is Not Yet Fully Exploited
## 3. What It Could Become in 12 Months
## 4. What It Could Become in 24–36 Months
## 5. What System Must Be Built Around It
## 6. What AI Agent Must Be Created
## 7. What Data Must Be Collected
## 8. What Process Must Be Standardized
## 9. What Product Can Result
## 10. What Offer Can Result
## 11. What Distribution Channel Fits
## 12. What Risk Exists
## 13. What Must Be Done in the Next 30 Days
## 14. What Must Be Done in the Next 90 Days
## 15. Verdict
────────────────────────
6. TECHNICAL SPECIFICATION ABOUT RARITY
────────────────────────
Create a separate TXT file:
filename:
cusnir_rarity_operating_specification_L7_v1.txt
Title:
# WHAT MAKES THE USER RARE — TECHNICAL SPECIFICATION
Include:
## 1. Definition of Rarity
## 2. What Combination Produces the Difference
## 3. What Is Psychologically Rare
## 4. What Is Socially Rare
## 5. What Is Commercially Rare
## 6. What Is Technically Rare
## 7. What Is Linguistically Rare
## 8. What Is Strategically Rare
## 9. What Can Be Copied
## 10. What Cannot Be Copied
## 11. What Can Be Systematized
## 12. What Must Remain Human
## 13. What Can Become IP
## 14. What Can Become a Method
## 15. What Can Become a Company
## 16. How the User Functions Under Pressure
## 17. How the User Functions in Creation
## 18. How the User Functions in Execution
## 19. How the User Functions in Monetization
## 20. Final Verdict
────────────────────────
7. TECHNICAL SPECIFICATION ABOUT BLOCKERS AND REMEDIES
────────────────────────
Create a separate TXT file:
filename:
cusnir_blockers_and_remedies_operating_specification_L7_v1.txt
Title:
# WHAT CAN BLOCK THE USER AND HOW TO REMEDY IT — TECHNICAL SPECIFICATION
Identify at least 20 possible blockers.
Include blockers such as:
- over-control;
- excessive complexity;
- standards that are too severe;
- refusal of intermediate versions;
- acceleration without stabilization;
- too many open systems;
- confusion between symbol and execution;
- confusion between vision and delivery;
- documentation without implementation;
- agents without clear ownership;
- funnels without metrics;
- products without channels;
- prompts without registry;
- executions without logs;
- distribution without feedback;
- sales without segmentation;
- ignored security;
- lack of rollback;
- lack of prioritization;
- lack of operational ritual.
For each blocker include:
- name;
- description;
- signal of appearance;
- severity: High / Medium;
- affected system;
- risk produced;
- remedy;
- required protocol;
- responsible agent;
- verification KPI;
- verdict.
Do not use Low severity.
────────────────────────
8. MASTER REPORT
────────────────────────
Create the main file:
filename:
cusnir_self_analysis_master_technical_report_L7_v1.txt
Structure:
# CUSNIR SELF-ANALYSIS — MASTER TECHNICAL REPORT
spec_id:
version:
status:
certainty:
generated_for:
scope:
method:
## 1. Operational Summary
## 2. Known Data
## 3. Logical Inferences
## 4. Missing Data
## 5. Complete List of Evaluated Abilities
## 6. Top 5 Exceptional Abilities
## 7. Top 5 Almost Impossible-to-Copy Abilities
## 8. High-Potential Abilities
## 9. What Makes the User Rare
## 10. What Can Block the User
## 11. Main Remedies
## 12. Recommended Agents for Amplification
## 13. Recommended Systems for Scaling
## 14. Possible Products
## 15. Possible Funnels
## 16. 30-Day Roadmap
## 17. 90-Day Roadmap
## 18. 12-Month Roadmap
## 19. 24–36-Month Roadmap
## 20. Verdict
────────────────────────
9. ZIP INDEX
────────────────────────
Create an index file:
filename:
README_INDEX_cusnir_self_analysis_export_L7_v1.txt
Include:
- name of each file;
- function of each file;
- recommended reading order;
- which files should become agents;
- which files should become protocols;
- which files should become products;
- which files are P0;
- package verdict.
────────────────────────
10. EXPORT RULES
────────────────────────
Create all files in TXT format.
Package all files into a ZIP archive.
Archive name:
cusnir_self_analysis_technical_specifications_export_L7_v1.zip
The archive must contain:
1. master report;
2. top 5 exceptional abilities — one separate file each;
3. top 5 almost impossible-to-copy abilities — one separate file each;
4. high-potential abilities — one separate file each;
5. rarity specification;
6. blockers and remedies specification;
7. README index.
────────────────────────
11. FINAL CHAT FORMAT
────────────────────────
After creating the files, do not paste all file contents into chat.
Respond only with:
Context:
- what you analyzed;
- what you excluded;
- what you produced.
Execution:
- ZIP download link;
- list of included files;
- total number of files;
- notes about what should be read first.
Verdict:
- PASS / BLOCK;
- reason;
- next logical step.
If you cannot create files or ZIP, deliver the complete content in separate TXT blocks and mark:
ZIP_EXPORT_BLOCKED.
Then explain exactly what is missing.
────────────────────────
12. QUALITY REQUIREMENTS
────────────────────────
The output must be:
- technical;
- complete;
- autonomous;
- immediately usable;
- free of external dependencies;
- free of motivational phrasing;
- free of empty praise;
- free of superficial psychology;
- free of mystification;
- free of generalities;
- free of unmarked unverifiable claims.
Every document must be usable as:
- agent instruction;
- system specification;
- product foundation;
- methodology foundation;
- protocol foundation;
- monetization foundation.
FINAL RULE:
Do not describe the user as a personality.
Model the user as an operating system.
Do not search for what sounds impressive.
Search for what produces repeatable power.
Do not confuse rarity with image.
Real rarity is the combination that produces results that are difficult to replicate.
u/vadimkusnir — 20 hours ago