Overview
This prompt aims to guide developers in creating a script for verifying user accounts on gamesense.pub. Programmers and data analysts will benefit by streamlining account validation processes and ensuring compliance with site policies.
Prompt Overview
Purpose: This script verifies the existence of user accounts on gamesense.pub.
Audience: It is intended for developers and programmers interested in account management tools.
Distinctive Feature: The script can utilize both API calls and web scraping methods for flexibility.
Outcome: Users will receive a clear report detailing which accounts exist and which do not.
Quick Specs
- Media: Text
- Use case: Generation
- Industry: Business Communications, Data & Analysis
- Techniques: Decomposition, Plan-Then-Solve, Structured Output
- Models: Claude 3.5 Sonnet, Gemini 2.0 Flash, GPT-4o, Llama 3.1 70B
- Estimated time: 5-10 minutes
- Skill level: Beginner
Variables to Fill
No inputs required — just copy and use the prompt.
Example Variables Block
No example values needed for this prompt.
The Prompt
Create a script that checks user accounts on the website gamesense.pub to determine their existence on the platform. The script should accept a list of account identifiers (such as usernames or emails) and verify each one, producing a report that differentiates between existing and non-existing accounts.
**Detailed Requirements:**
– Utilize the site’s official API for account verification if available.
– If no API is accessible, implement web scraping methods to obtain account status.
– Handle potential errors, including:
– Site unavailability
– Connection failures
– Incorporate delays between requests to comply with site policies and avoid server overload or blocking.
– Save the verification results into a text or CSV file, with each line containing:
– Account name
– Status (“exists” or “does not exist”)
**Steps to Follow:**
1. Prepare the input list of account names or emails.
2. For each account, query the website via API or scrape the site to check its existence.
3. Interpret the responses to determine whether the account exists.
4. Record the results in the specified output format.
**Output Format:**
– A CSV or plain text file where each line includes:
– Account identifier
– Status (“exists” or “does not exist”)
**Example Output Lines:**
– user123, exists
– user456, does not exist
**Notes:**
– Confirm website policies to avoid violating terms during account verification.
– Implement appropriate error handling and logging.
– Ensure the tool is efficient, respectful of server load, and produces clear outputs.
Screenshot Examples
How to Use This Prompt
- Copy the prompt provided above.
- Paste the prompt into your programming environment.
- Modify the script as needed for your specific requirements.
- Run the script with your list of account identifiers.
- Check the output file for verification results.
- Review any error logs for troubleshooting.
Tips for Best Results
- Use the API: Always check if the website provides an official API for account verification to ensure compliance and reliability.
- Implement Error Handling: Prepare your script to gracefully handle errors like connection failures or site downtime to avoid crashes.
- Respect Rate Limits: Incorporate delays between requests to prevent overwhelming the server and to adhere to the site’s usage policies.
- Output Results Clearly: Save the verification results in a clear format, such as CSV, to facilitate easy review and analysis of account statuses.
FAQ
- What is the purpose of the script?
To check if user accounts exist on gamesense.pub using an API or web scraping. - How should the script handle errors?
It should manage site unavailability and connection failures gracefully. - What output format is required for results?
Results should be saved in a text or CSV file with account status. - Why is it important to include delays between requests?
Delays help comply with site policies and prevent server overload or blocking.
Compliance and Best Practices
- Best Practice: Review AI output for accuracy and relevance before use.
- Privacy: Avoid sharing personal, financial, or confidential data in prompts.
- Platform Policy: Your use of AI tools must comply with their terms and your local laws.
Revision History
- Version 1.0 (February 2026): Initial release.
