Guidejar
Guidejar v0.1.6
Create, edit and search guides
From the developer
Declared capabilities
- Read
- Write
Cost & access
The plugin does not support payments or purchases. An existing Guidejar account with a paid subscription is required. Subscription management occurs separately on the Guidejar website.
Declared limitations
- General how-to question that doesn't mention the user's own guides. Answer normally without invoking any Guidejar tools.
- User wants a draft to use elsewhere, not saved to Guidejar. Return a draft in chat without invoking any Guidejar tools.
- Asks to find a document stored in another tool, not in Guidejar. Do not invoke Guidejar tools; use the appropriate connected drive search if available, or ask how to access the shared drive.
Onboarding example
Write a step-by-step guide on processing a vendor invoice.
Sources & dates
Developer declarations; not independently tested. Listing last checked Nov 17, 2026. Package observed Nov 17, 2026.
Description
From the marketplace listing
Connect your Guidejar workspace to create, update, and search guides and help articles
Language: English · Automatically detected from descriptions.
Changes
No changes recorded yet. Follow this plugin to keep track of future changes.
First seen Nov 17, 2026. Last seen Nov 17, 2026.
Similar plugins
Similar plugins could not be prepared right now. Please try again in a moment.
Browse plugins →Keywords
Files & skills
File archives
Skill instructions
guidejar5.11 KB
--- name: guidejar description: Find, read, create, or update guides and help articles in Guidejar. Use when the user refers to Guidejar content, supplies a Guidejar guide or article URL, asks questions about their documented processes or existing guides, or wants to turn rough notes or existing docs into a guide or article in Guidejar. --- # Work with Guidejar Use the connected Guidejar tools and their live schemas; never invent a tool or parameter. See [tool workflows](references/workflows.md) for step edits, articles, folders, and media. ## When to use Guidejar Use Guidejar for requests to create or save guides/help articles, work with existing guides, or check the user's documented processes. A short authoring request such as "Create a guide on scheduling an email in Gmail" can use Guidejar; it requests documentation, not an action in Gmail. Do not invoke Guidejar for a general how-to question that does not ask to check the user's guides. Return drafts requested for pasting into another document in chat. Search requests that explicitly name another source, such as a shared drive, belong to that source's tools; do not substitute a Guidejar search. Evaluate these boundaries in the context of the user's current request. ## Find and answer - Use `search_guides` for a topic and `list_guides` to browse recent content. Respect pagination; do not describe one page as the entire workspace. - To see what is in a team or folder, get the team ID from `get_teams`, then, for a folder, the folder ID from `get_team_folders` with that team ID. Pass `teamId` (and `folderId`) to `list_guides`. A folder filter returns only items directly in that folder, not its subfolders. - Resolve a supplied guide or article URL with `get_id_from_guide_url`, then fetch it with `get_guide`. Do not guess IDs from custom slugs. - Read relevant documents before answering process questions. Link to the returned URLs and distinguish documented facts from suggestions. If nothing relevant is found, say so. ## Create 1. Resolve the destination team with `get_teams`. If more than one team is possible and the user hasn't chosen, ask. Never guess team IDs. 2. Only when the user names a folder, call `get_team_folders` with the team ID from step 1 to resolve it. Otherwise omit `folderId`. 3. Use `create_guide` for ordered procedures and walkthroughs, and `create_article` for longer reference content. 4. Ground the content in the user's notes, supplied media, or existing documents. Ask for missing facts that affect correctness. Do not invent screenshots, UI labels, or completed actions. 5. Return the URL from the tool result. A request for a draft alone stays in chat. New documents are private; a returned URL does not make them public. ## Browser walkthroughs and screenshots When the user asks you to perform a workflow and document it with screenshots, first check whether this host provides browser interaction, screenshot capture, access to the captured image bytes, and HTTP PUT uploads. Guidejar tools do not provide these capabilities; use the host's available tools for them. - If browser interaction or screenshot capture is unavailable, explain that you cannot perform or screenshot the workflow here. Ask for supplied screenshots or offer a text-only guide grounded in the user's notes or documentation. - If image bytes or HTTP PUT uploads are unavailable, explain that limitation separately and offer a guide without media, with an editor link for adding it. - If the user explicitly requested screenshots, get agreement before creating a fallback that omits them, unless the request already permits that fallback. - Never invent screenshots or claim to have performed actions you did not perform. Follow the media workflow in [tool workflows](references/workflows.md) and confirm each upload before attaching its hosted URL. A guide without the requested screenshots does not pass a screenshot/upload test. ## Edit Fetch t
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 1 — file references are metadata, not package contents.
Release notes
0.1.6: Add the review video, align positive test cases with the recorded Todoist workflow, and clarify browser, screenshot, and upload capability checks and fallbacks.
Declared in the saved package. Remote tools may change independently.
Package details
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
- Package author
- Guidejar
- Keywords
- See keywords
- Declared availability
- No country restrictions declaredDeclared regions; live availability may differ.
- Commerce declaration
- Does not support commerceThis does not establish whether access is free or paid.
- Review scenarios
- 5 positive · 3 negativeScenario counts, not test results.
Declared capabilities
- Read
- Write
Package observed Nov 17, 2026.
Technical details
- First seen
- Nov 17, 2026 · 06:00 UTC
- Last seen
- Nov 17, 2026 · 18:00 UTC
- Collection status
- Collected
plugin_asdk_app_6ac4df13c6cc819181cce1fc82f39bbe
Download plugin data (JSON)Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.