fetch
ChatGPTInternal APP fetch tool for accessing internal APIs
knowledge-graph
ChatGPTGenerate a non-hierarchical, network-based knowledge graph visualization. You (ChatGPT) should create a FLAT, interconnected knowledge graph where nodes represent entities, concepts, or objects, and edges represent semantic relationships between them. IMPORTANT - Network Topology (NO Hierarchy): This is NOT a tree structure. Create a densely connected network where: ✓ All nodes are peers with equal hierarchical weight ✓ Any node can connect to any other node through multiple relationship types ✓ Support many-to-many connections and cyclic relationships ✓ Avoid parent-child hierarchies or tree-like structures ✓ Create clusters based on relationship patterns, not hierarchy Node Design: - Each node should include: • id: Unique identifier (kebab-case, e.g., "react", "typescript") • label: Display name • type: concept/issue/solution/metric/technology/skill/project • description: 1-2 sentences explaining the entity • metadata: Optional properties (e.g., {popularity: "high", difficulty: "medium"}) Edge Design - Semantic Relationships: - Use SPECIFIC semantic relationships, not generic "connected to" - Examples of good relationship labels: • "depends on", "implements", "extends", "uses" • "influences", "causes", "leads to", "results in" • "belongs to", "part of", "contains" • "similar to", "related to", "contrasts with" • "requires", "enables", "supports" Connection Patterns: 1. Hub Nodes: Some nodes naturally have many connections (e.g., "React" in a frontend tech graph) 2. Cross-domain Links: Connect different entity types (e.g., technology → concept → skill) 3. Bidirectional Relations: Same nodes can have multiple edges with different meanings 4. Transitive Relations: Show both direct and indirect relationships 5. Cyclic Relations: Allow circular dependencies where they exist Example - React Ecosystem (Network Structure): Nodes (all peers): - react, typescript, nextjs, hooks, state-management, redux, testing, jest, tailwind Edges (many-to-many connections): - react → typescript ("commonly used with") - react → nextjs ("framework built on") - react → hooks ("provides") - hooks → state-management ("enables") - state-management → redux ("can use") - react → testing ("requires") - testing → jest ("uses") - react → tailwind ("styled with") - typescript → testing ("improves") - nextjs → typescript ("built-in support") Note: No center node, no layers, dense interconnections forming natural clusters.
knowledge-graph-list
ChatGPTWhen to use: - User asks: "Show me my saved knowledge graph list" - User asks: "Display my knowledge graph" - User asks: "Load the knowledge graph I saved" - User asks: "Show my knowledge graph history" you can call the tool
knowledge-graph-storage
ChatGPTPerform one of four fixed operations for the authenticated user's private knowledge-graph library: list one page, request a JSON upload URL, complete that upload, or save the graph record. The tool cannot accept arbitrary URLs, methods, headers, query parameters, payloads, credentials, or conversation history. It never deletes or overwrites data and cannot publish content to the public internet. The short-lived upload URL and private list data are returned only to the widget in result metadata.