ChatGPT Tools: Bio & Document Creation Guidelines

Notes on ChatGPT Tools and Guidelines

Bio Tool

• Functionality: The bio tool allows information persistence across conversations. This means users can input information they want the model to remember in future interactions.
  • Thoughts: This is useful for maintaining context and continuity in communication, allowing for a more personalized and efficient experience.
  • Explanation: Users can save specific details, like preferences or important data, which can be recalled in subsequent conversations.

Canmore Tool

• Overview: canmore is for creating and updating text documents displayed alongside the conversation, known as the "canvas."
  • Thoughts: This tool is ideal for handling complex or lengthy information that benefits from a separate display area.
  • Explanation: It’s crucial for tasks that require substantial writing space, like drafting reports or essays.

How to Use Canmore

• Creating New Documents: Use the create_textdoc function when starting a new document.

  • Thoughts: Beneficial for comprehensive tasks such as writing a detailed proposal or a research paper.
  • Explanation: This approach helps keep large bodies of text organized and separate from the chat.

• Updating/Editing Documents: The update_textdoc function is used for modifications.

  • Thoughts: Allows for efficient updates, ensuring documents remain current.
  • Explanation: Use the pattern "." to overwrite the entire document, especially for code and substantial content.

When to Use Canmore

• Recommended Scenarios:
  • Standalone, substantial content over 10 lines.
  • User intends to assume ownership or reuse the document.
  • When content is part of a deliverable, such as essays or proposals.
• Examples:
  • Writing formal documents like emails or essays.
  • Creating code scripts with detailed implementation.

When Not to Use Canmore

• Situations to Avoid:
  • Short content, less than 10 lines.
  • Primarily informative content or step-by-step guides.
  • User requests completion within the chat.
• Examples:
  • Simple tasks like explaining topics or small coding questions.

Rewrite Scenarios

• Full document rewrites should be used when comprehensive changes are needed.
• Usage situations include refining or enhancing content for clarity or professionalism.

Overall Guidelines

• Content Suitability: Choose between inline conversation responses and document creation based on content complexity and intended user interaction.
  • Thoughts: Matching tool usage to content type enhances user experience and ensures efficient communication.
  • Explanation: Helps maintain clarity and focus, especially in cases where detailed information could clutter a chat-based response.

Reference:

Notes on Using Text Document Creation and Editing

Overview

This document provides guidelines for creating and updating text documents using specific commands and parameters. It categorizes user requests and specifies tools and procedures for handling different types of content or edits.

Key Points

Avoiding create_textdoc

• When to Avoid:
  • For tasks like extracting data, writing blog posts, or collecting API data.
  • Example Requests:
    • "Email subject line for email to my boss requesting time off."
    • "Teach me API data collection on pandas."
  • Thoughts: The emphasis is on avoiding create_textdoc for tasks that require direct user presentation without needing a document.

Using create_textdoc

• When to Use:
  • For creating or editing rich text documents.
  • Example Requests:
    • Making content more professional or concise.
    • Creating content in specific formats, like turning text into bullet points.
  • Thoughts: Ideal for tasks where document creation or formatting is essential.

Content Types

• Types:
  • Document
  • Webview
  • Code (e.g., HTML, Python, JSON)
  • Usage: Determines the format and platform for the resulting content.
  • Thoughts: Choosing the correct type ensures that content is displayed and executed correctly, matching user needs.

Parameters and Commands

• Type Parameter:
  • Use to define the format of the content being created or edited.
  • Examples:
    • type=“code/python” for Python code.
    • type=“document” for markdown formatted text.
  • Thoughts: Selecting the right parameter is critical for user satisfaction and content accuracy.

Usage Notes

• Multiple Contents:
  • Use create_textdoc multiple times if there are significant separate requests.
  • Emphasizes minimalism and precision in document generation.
  • Thoughts: Balancing between user friendliness and efficiency.

Command: update_textdoc

• Function:
  • Updates part of the document as per user’s request.
  • Focus on targeted updates rather than whole document rewriting.
  • Thoughts: Ensures that updates are precise and user-focused.

These notes outline the structured approach to using and managing text document creation and updates, providing clarity on tools and methods to use based on the specific need and context of user requests.

Reference: