Skip to main content
Cart 0

Contributor Guidelines

Turn your publication’s requirements into a clear contributor brief and submission checklist.

Use Contributor Guidelines

$49.99 / month

Includes every Agent on Ai-GEN. 15,000+ Agents for one monthly price, cancel anytime.

From the creator of GPTs with 8.5M+ chats · 4.2 stars · 37K+ reviews

Start Contributor Guidelines — $49.99 / month

Your account is created at checkout. After payment, this Agent opens when access is ready.

Already subscribed? Sign in · Account terms

Cancel future renewals from Account & Billing → Subscriptions.

See the work before you buy.

An example of what this Agent writes.

Create newsletter submission guidelines

The task

Draft concise guidelines for a fictional neighborhood newsletter accepting 600–900 word local-history pieces from residents. Use a friendly factual tone. Require sources and permission for quoted interviews; accept pitches by email. Include pitch format, editing expectations, conflicts, and no promise of publication. Do not invent payment, copyright/license, or response-time terms; label optional policy suggestions as proposed.

The Agent’s response

Neighborhood Newsletter: Contributor Guidelines for Local-History Pieces

Thank you for your interest in contributing to our neighborhood newsletter! We welcome residents’ stories about local history, community events, and personal recollections. To ensure a smooth and enjoyable process, please review these guidelines:

Submission Content & Length

  • Focus on local history topics relevant to our neighborhood.
  • Aim for contributions between 600 and 900 words.
  • Write in a friendly, factual tone suitable for a general audience.

Sources & Permissions

  • Provide clear citations for any historical facts, quotes, or external material.
  • If using quotes or information from interviews with residents, obtain their permission and include their name and your interview date.

Pitches & Submission Process

  • Send your story pitch via email, including the following format:
  • Title:
  • Brief summary (2-3 sentences):
  • Key sources or interview info (if applicable):

Editing & Revisions

  • We reserve the right to edit for clarity, length, tone, and style.
  • Contributors should be prepared to make reasonable revisions if requested.

Conflicts of Interest

  • Disclose any personal or professional relationships that might influence your story.
  • Avoid submitting content with a conflict of interest that could compromise objectivity.

Publication & Response

  • Submission does not guarantee publication.
  • We will notify you if your story is accepted or if revisions are needed.

Optional Policy Suggestions (for consideration)

  • Establish a review timeline (e.g., response within 2–4 weeks).
  • Clarify copyright and licensing expectations.
  • Invite feedback for improving the submission process.

Thank you for sharing your stories and helping us celebrate our neighborhood’s rich history!

See the follow-up

The next request

Add a short first-time contributor checklist and a proposed policy requiring disclosure of AI assistance without banning it outright. Do not add new payment, rights, or turnaround commitments. Output text only.

The result

Neighborhood Newsletter: Contributor Guidelines for Local-History Pieces

Thank you for your interest in contributing to our neighborhood newsletter! We welcome residents’ stories about local history, community events, and personal recollections. To ensure a smooth and enjoyable process, please review these guidelines:

Submission Content & Length

  • Focus on local history topics relevant to our neighborhood.
  • Aim for contributions between 600 and 900 words.
  • Write in a friendly, factual tone suitable for a general audience.

Sources & Permissions

  • Provide clear citations for any historical facts, quotes, or external material.
  • If using quotes or information from interviews with residents, obtain their permission and include their name and your interview date.

Pitches & Submission Process

  • Send your story pitch via email, including the following format:
  • Title:
  • Brief summary (2-3 sentences):
  • Key sources or interview info (if applicable):

First-Time Contributor Checklist

  • Ensure your story focuses on local history relevant to our neighborhood.
  • Include sources and permissions for quotes or interview content.
  • Keep your piece within 600–900 words.
  • Write in a friendly, factual tone.
  • Submit your pitch via email as outlined above.

Editing & Revisions

  • We reserve the right to edit for clarity, length, tone, and style.
  • Contributors should be prepared to make reasonable revisions if requested.

Conflicts of Interest

  • Disclose any personal or professional relationships that might influence your story.
  • Avoid submitting content with a conflict of interest that could compromise objectivity.

AI Assistance Disclosure (Proposed Policy)

  • We ask contributors to disclose if parts of their submission were generated with AI assistance.
  • Use of AI tools is permitted but should be transparently noted in your submission.

Publication & Response

  • Submission does not guarantee publication.
  • We will notify you if your story is accepted or if revisions are needed.

Thank you for sharing your stories and helping us celebrate our neighborhood’s rich history!

See another real example

Prepare a technical blog contribution brief

The task

Create concise contributor guidelines for a fictional beginner-Python blog: 800–1,200 word posts, stated prerequisites, reproducible text code samples, no promotional affiliate links, and text submissions for review. Include originality, attribution, accessibility, and review steps. Do not claim you execute or verify code, generate files, or provide downloads.

The Agent’s response

Contributor Guidelines for the Beginner Python Blog

Thank you for your interest in contributing to our beginner-friendly Python blog. These guidelines are designed to ensure clarity, consistency, and quality across all submissions. Please read carefully before submitting your article.

---

1. Content Scope and Style

  • Topic Focus: Articles should be aimed at beginner Python programmers, covering foundational concepts, tutorials, or practical projects suitable for those starting their coding journey.
  • Word Count: Submissions should be between 800 and 1,200 words.
  • Tone: Clear, accessible, and encouraging language. Avoid jargon or assumptions of prior extensive knowledge.

2. Prerequisites and Audience

  • Clearly state any prerequisites or necessary prior knowledge at the beginning of your article (e.g., familiarity with basic programming concepts).
  • Be explicit about the environment setup, such as Python version or libraries needed.

3. Text Code Samples

  • All code snippets must be reproducible, self-contained, and formatted for clarity.
  • Use proper syntax highlighting and indentation.
  • Ensure code examples are minimal yet sufficient to illustrate the concept.
  • Do not include files or external dependencies that require downloads; all code should be included inline or in embedded blocks.

4. Originality and Attribution

  • Content must be your original work or appropriately attributed if adapted from external sources.
  • Offer proper credit when referencing other creators, tutorials, or resources.
  • Plagiarism is strictly prohibited and will result in rejection.

5. Accessibility

  • Write with clarity and simplicity to make content accessible to a wide range of readers.
  • Use descriptive headings, bullet points, and visual cues to enhance readability.
  • Provide alt text or descriptions for visuals if included.

6. Submission and Review

  • Submit your article in a plain text or markdown format preferred.
  • Include a short bio and a link to your own relevant work or social profiles if desired.
  • Submit your draft via our designated review process.
  • We will review your submission for clarity, accuracy, and adherence to guidelines.
  • You will receive feedback or requests for revisions within a reasonable timeframe.

7. Promos and Links

  • Do not include promotional affiliate links or marketing content.
  • Links to external resources are allowed if directly relevant, but must be educational, reputable, and clearly labeled.

8. Responsible Code Sharing

  • We do not verify, execute, or test submitted code.
  • Authors are responsible for ensuring their code is accurate, secure, and functional.
  • Clearly state if code is untested or experimental.

9. Originality and Ethical Use

  • Ensure all content respects intellectual property rights.
  • Avoid sharing harmful, insecure, or malicious code.
  • Emphasize ethical programming practices and responsible use of technology.

---

Thank you for contributing to our community! Your shared knowledge helps others learn and grow in their Python journey. We look forward to your submission.

See the follow-up

The next request

Write a short encouraging acceptance email template requesting clearer setup steps and descriptive link text. Keep it a text template; do not offer unsupported file delivery or sending.

The result

Subject: Your Submission Has Been Accepted — A Few Small Suggestions

Dear [Author's Name],

Thank you for sharing your article with us! We’re pleased to inform you that your submission has been accepted for publishing.

As we prepare to finalize your piece, we kindly ask you to review and clarify the setup steps listed in your article to help readers follow along more easily. Additionally, please consider making any external links more descriptive with meaningful link text, which improves accessibility and reader understanding.

We appreciate your contributions and look forward to publishing your work. Please send us your revised version at your earliest convenience.

Best regards,
[Your Name]
[Your Position/Team Name]

Describe your publication, audience, accepted topics, word count, and editorial policies. This Agent helps draft contributor guidelines, clarify submission requirements, and prepare revision or acceptance messages. It works from your supplied text; it does not receive submissions, contact contributors, execute code, or enforce policies.

What you can take away

  • A contributor brief tailored to your publication
  • A clear submission and review checklist
  • Follow-up policies or editorial messages

How to use it

Begin with the publication details that matter, get a structured brief, and refine specific policies and contributor messages in the same conversation. The examples show how a broad idea becomes usable editorial guidance.

What you bring

  • Publication audience, topics, format, and word count
  • Submission process, editorial policies, and known payment terms
  • Know the publication’s submission and editorial requirements

A good fit for

  • Drafting a contributor brief
  • Creating a first-time submission checklist
  • Preparing an editorial revision message

Ways to start

A few requests this Agent can handle.

Draft contributor guidelines for a fictional neighborhood newsletter. We accept 600–900 word local-history pieces from residents, use a friendly factual tone, require sources and permission for quoted interviews, and accept pitches by email. Include pitch format, editing expectations, conflicts of interest, and a clear statement that we cannot promise publication. Do not invent payment terms.

Create contributor guidelines for a fictional technical blog covering beginner Python tutorials. Posts should be 800–1,200 words, explain prerequisites, include reproducible text code samples, avoid promotional affiliate links, and be submitted as text for review. Include originality, attribution, accessibility, and review steps. Do not claim you will execute or verify code.

Good to know

This workspace provides text assistance.

  • Receiving or publishing submissions
  • Inventing payment or legal terms
  • Contacting contributors on your behalf
  • Drafts text only; does not publish or contact contributors
  • Editorial and legal terms need your review

Before you subscribe

What am I buying?

One monthly subscription that opens this Agent and every other Agent on Ai-GEN. Cancel from Account & Billing.

What happens after payment?

Checkout creates or uses your Ai-GEN account. When payment and entitlement are confirmed, the purchased Agent opens. Choose a starter task, add your inputs, and send your first request.

Can I cancel?

Yes. Manage cancellation under Account & Billing → Subscriptions. Review the status and cancellation details shown there before confirming.

Can I use the response in my work?

Use it as a draft to review and adapt. Verify calculations, facts, rights, and suitability before relying on it. Do not provide information you do not have permission to share.

Have a question? Contact support
Report This Agent

Tell Ai-GEN about broken behavior, poor performance, misleading capabilities, or a safety concern.