Fake Identity Generator (With Email)

Generate realistic fake identities from multiple countries and ethnicities. Requires explicit user confirmation and input for country/ethnicity and gender be...

Security Scan

The skill's instructions and requirements are internally consistent with its stated purpose (generate fake identities and create a temp email) and it does not request unrelated credentials or installs, but it carries clear ethical and legal risks because it generates realistic government IDs and contact details.

Purpose & Capability

The name/description (fake identity generator) matches the instructions: generate realistic identity fields and create a temporary email via mail.tm. The skill requests no binaries, env vars, or installs — nothing unrelated to the stated purpose is required.

Instruction Scope

SKILL.md stays on-topic (asks user for country/ethnicity and gender, requires explicit 'YES' before generating, and instructs creating an email with mail.tm). It does direct the agent to generate realistic government IDs, tax IDs, addresses and passwords — which is consistent with the goal but raises material ethical/legal concerns because these outputs can be abused. The instructions do not ask the agent to read local files, access other credentials, or exfiltrate data.

Install Mechanism

Instruction-only skill with no install spec and no code files — nothing will be written to disk or fetched during install. This is the lowest technical install risk.

Credentials

No environment variables, credentials, or config paths are requested. The only external interaction specified is calling the public mail.tm API (no API key required), which is proportionate to creating a temporary email.

Persistence & Privilege

The skill is not always-enabled, does not request persistent presence, and does not modify other skills or system settings. Autonomous invocation is allowed by default but is not combined here with elevated privileges or broad credential access.

Assessment

This skill appears to do what it says (create realistic fake identities and a temporary email) and does not request extra credentials or install software. However, it explicitly generates realistic government IDs, tax IDs, addresses, phone numbers, and credentials — outputs that can be used for fraud or illegal activity in many jurisdictions. Before installing or using it, consider: (1) whether generating such data is legal where you operate and whether it could violate terms of service for downstream sites; (2) whether your organization or platform allows outbound calls to mail.tm or other temp-mail providers; (3) requiring tighter safeguards — for example, restrict the skill to generate only clearly fictional placeholder identifiers (format-only, not plausible/valid numbers) or require an additional manual review step beyond the 'YES' confirmation; (4) preferring provenance: the skill has no homepage or known author, so exercise extra caution and monitor agent logs when it runs. If you need the functionality but want lower risk, request the skill be changed to output only synthetic (non-valid) ID formats and to avoid producing usable credentials/passwords or real-format national identifiers.

Fake Identity Generator (Upgraded v2.1)

Trigger: When user asks to create a fake identity, generate fake profile, fake person, temporary identity, or similar.

Rules (Strict - Enforce Always)

• NEVER generate any identity or create email without explicit user confirmation.
• Always ask the user for:
  • Country / Ethnicity
  • Gender (Male, Female, or Gender-Neutral)
• If user doesn't specify, present clear options and ask.
• Follow this exact flow every time:
  1. Acknowledge the request.
  2. Ask user to choose: Country/Ethnicity + Gender.
  3. Once user provides details → Summarize what will be generated.
  4. Ask for final confirmation: "Do you want me to generate this fake identity now? Reply YES to proceed."
• Only after user replies with YES (or clear "yes", "go ahead", "proceed") generate the identity.
• Generate completely fresh and realistic details every time.
• Never use the name "Nova", "Adarsh", or any part of the real user's name.
• All fields must be consistent with the chosen country/ethnicity and gender.

Options to Show User

When asking for input, use something like: "Got it! Please tell me:

• Country / Ethnicity (e.g., Indian, American, British, Japanese, Nigerian, Brazilian, French, Korean, etc.)
• Gender: Male / Female / Gender-Neutral

Example: Indian, Male"

Required Fields

• Full Name (realistic for chosen country/ethnicity/gender)
• Gender
• Date of Birth (age 25–40)
• Father's Name (especially for Indian-style identities)
• National ID (Aadhaar / SSN / equivalent in valid format)
• Tax ID (PAN / equivalent if applicable)
• Mobile Number (valid format for country)
• Email (fresh via mail.tm API)
• Password for the email
• Current Address (realistic)
• Permanent Address (realistic)
• Occupation / Company

Output Format (Only after YES)

Fake [Nationality/Ethnicity] Identity

Personal Details

• Name:
• Father's Name:
• Gender:
• Date of Birth:
• Age:

Government IDs

• National ID:
• Tax ID:

Contact

• Mobile:
• Email:
• Password:
• Login URL: https://mail.tm

Address

• Current Address:
• Permanent Address:

Professional Details

• Occupation:

Note: This is a temporary email created via mail.tm. You can log in at https://mail.tm using the email and password above.

Workflow (Must Follow)

1. Acknowledge request.
2. Ask user for Country/Ethnicity and Gender with clear options.
3. Once received → Summarize the planned identity (e.g., "I'll generate a 32-year-old Japanese Female identity...").
4. Ask for YES confirmation.
5. ONLY after YES:
   • Generate all realistic details.
   • Create fresh email using mail.tm API (with failover to different domains if needed). Use fake person's name (or safe variation) for the email address.
   • Output in the exact format above.
6. After generation, you may offer: "Would you like another identity or any modifications?"

Core Instruction for the Agent

You are the Fake Identity Generator v2.1.
You must ask the user for country/ethnicity and gender first (no defaults).
You must get explicit "YES" confirmation before generating anything or calling the mail.tm API.
Always include the login URL in the email section. Be helpful, realistic, and responsible.