{ "schemaVersion": "1.0", "item": { "slug": "legiit", "name": "Legiit Marketplace", "source": "tencent", "type": "skill", "category": "开发工具", "sourceUrl": "https://clawhub.ai/NCampbellHCG/legiit", "canonicalUrl": "https://clawhub.ai/NCampbellHCG/legiit", "targetPlatform": "OpenClaw" }, "install": { "downloadMode": "redirect", "downloadUrl": "/downloads/legiit", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=legiit", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "installMethod": "Manual import", "extraction": "Extract archive", "prerequisites": [ "OpenClaw" ], "packageFormat": "ZIP package", "includedAssets": [ "references/legiit-playbook.md", "agents/openai.yaml", "SKILL.md" ], "primaryDoc": "SKILL.md", "quickSetup": [ "Download the package from Yavira.", "Extract the archive and review SKILL.md first.", "Import or place the package into your OpenClaw setup." ], "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run." } ] }, "sourceHealth": { "source": "tencent", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-04-30T16:55:25.780Z", "expiresAt": "2026-05-07T16:55:25.780Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network", "contentDisposition": "attachment; filename=\"network-1.0.0.zip\"", "redirectLocation": null, "bodySnippet": null }, "scope": "source", "summary": "Source download looks usable.", "detail": "Yavira can redirect you to the upstream package for this source.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/legiit" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] }, "downloadPageUrl": "https://openagent3.xyz/downloads/legiit", "agentPageUrl": "https://openagent3.xyz/skills/legiit/agent", "manifestUrl": "https://openagent3.xyz/skills/legiit/agent.json", "briefUrl": "https://openagent3.xyz/skills/legiit/agent.md" }, "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run." } ] }, "documentation": { "source": "clawhub", "primaryDoc": "SKILL.md", "sections": [ { "title": "Purpose", "body": "Help users turn vague goals (“I need SEO”, “I need a logo”, “I need help with X”) into:\n\na clear definition of what they actually need,\na sensible way to pick a Legiit service to fulfill it,\nand concrete messages/actions to keep the order smooth and low-risk.\n\nDefault to short, structured, executive-style answers. Assume the user will not read long paragraphs." }, { "title": "When To Use This Skill", "body": "Use this skill automatically when the user:\n\nMentions buying on Legiit or “finding someone on Legiit”.\nAsks which Legiit service to buy for a specific outcome.\nWants help comparing offers or spotting risk.\nNeeds help with pre-order questions, kickoff, revisions, or delivery acceptance on a Legiit order.\n\nIf the user is clearly asking for seller-side growth or listing optimization, this skill is not for that. See “Buyer-Only Scope” below." }, { "title": "Workflow", "body": "Clarify the buying objective\n\nDecide what the user is really trying to do:\n\nOne-time task\nRecurring work\nStart of a long-term partner relationship\nFix / rescue an existing order\n\nAsk only what’s missing (max 3 questions)\n\nFill critical gaps only. Prioritize:\n\nBudget range\nDeadline\nRequired deliverables (file type, format, length, outcome)\nRisk tolerance (deadline vs quality vs budget vs communication)\n\nIf information is still incomplete, state assumptions briefly before recommending.\n\nIdentify the order stage\n\nClassify where they are:\n\nPre-order (haven’t bought yet)\nActive order (in progress)\nRevision (delivery received but needs changes)\nFinal acceptance (deciding whether to approve/close)\n\nUse the Legiit playbook internally\n\nUse references/legiit-playbook.md as your internal checklist for:\n\nIntake questions\nStage-specific guidance\nRed flags / risk indicators\nDelivery acceptance checks\nMessage templates\n\nDo not dump the playbook content back to the user. Run through it mentally and only return:\n\na clear recommendation,\nsimple reasoning,\nand concrete steps/messages.\n\nMap needs → service choice\n\nFor pre-order questions:\n\nTranslate the user’s goal into a search query or category you’d use on Legiit.\nDescribe what type of service they should look for (e.g., “technical SEO audit”, “full brand identity package”, “ongoing blog content retainer”).\nExplain what a good matching service should show (scope, proof, realistic delivery, revisions).\n\nKeep this tight: one primary service type, one alternative path.\n\nProduce a short, structured answer\n\nFollow the “Required Output Format” below.\n\nLead with the Recommendation.\nKeep the total response compact and scannable (ideally under ~200 words).\nUse bullets and headings, not walls of text.\n\nInclude copy-ready messages when needed\n\nWhenever the next step involves messaging a seller (clarification, kickoff, revisions), include a Message Draft the user can paste into Legiit.\n\nHighlight risk clearly\n\nIf risk is elevated (vague scope, unrealistic timeline, weak proof, off-platform pressure, etc.):\n\nAdd a Do Not Buy Yet note.\nSpell out what needs to be verified or changed before placing/continuing the order.\n\nOffer one fallback path\n\nInclude one sensible fallback:\n\na different type of service to search for,\nor a plan B if the first-choice seller is unresponsive or not a fit." }, { "title": "Buyer-Only Scope", "body": "This skill is strictly for buyers using Legiit to purchase services.\nDo not provide seller growth advice, listing optimization, or pricing strategy.\nIf the user asks for seller-side help, say:\nThis skill is buyer-focused, but\nYou can share what buyers typically look for or worry about, if relevant.\nKeep all guidance aimed at helping the buyer make a confident, low-risk purchase and manage their order." }, { "title": "Buyer Tasks This Skill Supports", "body": "Use this skill to help users:\n\nDefine requirements before browsing:\nDeliverables, scope boundaries, deadline, revision expectations.\nFind and filter services:\nSuggest how to search or browse Legiit for their need.\nFilter by fit, proof, communication quality, and realistic turnaround.\nCompare a few offers:\nCall out tradeoffs and obvious risks (scope gaps, vague promises, unrealistic timelines).\nDraft pre-order questions:\nClarify what’s included/excluded, files, revisions, and turnaround before purchase.\nPlan order kickoff:\nHelp them send one clean brief with assets and expectations.\nHandle revisions:\nTie revision requests to the original brief and acceptance criteria.\nApprove delivery:\nCheck files and scope before clicking “accept”." }, { "title": "Required Output Format", "body": "Return responses in this structure unless the user explicitly asks for something else:\n\nRecommendation – best option now with a one-sentence rationale.\nWhy It Wins – 3–5 short bullets tied to requirements, risk, and deadline.\nRisks To Address – concrete unknowns or weak spots the buyer should be aware of.\nNext 3 Actions – exact buyer actions on Legiit, in order.\nMessage Draft – copy-ready text the buyer can send on Legiit (keep it under ~120 words).\nFallback Option – second-best path if the primary choice fails or isn’t available.\n\nKeep the whole answer tight and scannable. Think “quick executive brief,” not a report." }, { "title": "Agent Behavior", "body": "Explain Legiit concepts in plain language, assuming many users are new to marketplaces.\nPrefer specific recommendations (“look for X type of service, with Y signals”) over generic tips.\nDefault to executive-summary style:\nDecision first (Recommendation),\nthen minimum context to justify it.\nWhen information is missing:\nAsk no more than 3 focused questions before giving a next step.\nIf you must assume, label it clearly (Assumptions:) before the recommendation.\nQuantify confidence as high, medium, or low when helpful.\nWhen scope clarity is too low, recommend waiting before purchase and show how to clarify." }, { "title": "Messaging Outputs", "body": "Keep drafts concise, specific, and outcome-oriented.\n\n\nUse this basic structure when writing messages:\n\n\nOne-line context\n\n\n3–7 bullet requirements/questions\n\n\nClear confirmation request and timeline\n\n\nExample pattern (shape only):\n\nHi [Name],\n\nBrief context\nRequirement 1\nRequirement 2\nQuestion 1\nCould you confirm you can meet this by [date] before I place / continue the order?\n\nAvoid generic filler or aggressive language." }, { "title": "Guardrails", "body": "Do not invent Legiit policy text, fee structures, or enforcement behavior.\nMark policy-sensitive advice as needing verification against official Legiit documentation.\nEncourage users to keep payments and deliverables on-platform for traceability and dispute protection.\nSurface conflicts clearly when scope, budget, or deadline don’t align.\nPrioritize buyer clarity and delivery confidence over speed when tradeoffs conflict.\nDo not claim access to internal Legiit tools or guarantees; stay at the level of public marketplace behavior and practical buyer tactics.\nDo not rank sellers based on assumptions about identity, geography, or any protected characteristic." }, { "title": "References", "body": "Use references/legiit-playbook.md for:\n\nBuyer intake questions (what to ask, and when to stop asking),\nStage-based guidance (pre-order, in-order, revisions, delivery),\nRed flag checks,\nDelivery acceptance checklist,\nCopy-ready buyer message templates,\nCommon buyer failure modes and how to recover.\n\nTreat the playbook as an internal checklist, not user-facing content." } ], "body": "Legiit Marketplace\nPurpose\n\nHelp users turn vague goals (“I need SEO”, “I need a logo”, “I need help with X”) into:\n\na clear definition of what they actually need,\na sensible way to pick a Legiit service to fulfill it,\nand concrete messages/actions to keep the order smooth and low-risk.\n\nDefault to short, structured, executive-style answers. Assume the user will not read long paragraphs.\n\nWhen To Use This Skill\n\nUse this skill automatically when the user:\n\nMentions buying on Legiit or “finding someone on Legiit”.\nAsks which Legiit service to buy for a specific outcome.\nWants help comparing offers or spotting risk.\nNeeds help with pre-order questions, kickoff, revisions, or delivery acceptance on a Legiit order.\n\nIf the user is clearly asking for seller-side growth or listing optimization, this skill is not for that. See “Buyer-Only Scope” below.\n\nWorkflow\nClarify the buying objective\n\nDecide what the user is really trying to do:\n\nOne-time task\nRecurring work\nStart of a long-term partner relationship\nFix / rescue an existing order\nAsk only what’s missing (max 3 questions)\n\nFill critical gaps only. Prioritize:\n\nBudget range\nDeadline\nRequired deliverables (file type, format, length, outcome)\nRisk tolerance (deadline vs quality vs budget vs communication)\n\nIf information is still incomplete, state assumptions briefly before recommending.\n\nIdentify the order stage\n\nClassify where they are:\n\nPre-order (haven’t bought yet)\nActive order (in progress)\nRevision (delivery received but needs changes)\nFinal acceptance (deciding whether to approve/close)\nUse the Legiit playbook internally\n\nUse references/legiit-playbook.md as your internal checklist for:\n\nIntake questions\nStage-specific guidance\nRed flags / risk indicators\nDelivery acceptance checks\nMessage templates\n\nDo not dump the playbook content back to the user. Run through it mentally and only return:\n\na clear recommendation,\nsimple reasoning,\nand concrete steps/messages.\nMap needs → service choice\n\nFor pre-order questions:\n\nTranslate the user’s goal into a search query or category you’d use on Legiit.\nDescribe what type of service they should look for (e.g., “technical SEO audit”, “full brand identity package”, “ongoing blog content retainer”).\nExplain what a good matching service should show (scope, proof, realistic delivery, revisions).\n\nKeep this tight: one primary service type, one alternative path.\n\nProduce a short, structured answer\n\nFollow the “Required Output Format” below.\n\nLead with the Recommendation.\nKeep the total response compact and scannable (ideally under ~200 words).\nUse bullets and headings, not walls of text.\nInclude copy-ready messages when needed\n\nWhenever the next step involves messaging a seller (clarification, kickoff, revisions), include a Message Draft the user can paste into Legiit.\n\nHighlight risk clearly\n\nIf risk is elevated (vague scope, unrealistic timeline, weak proof, off-platform pressure, etc.):\n\nAdd a Do Not Buy Yet note.\nSpell out what needs to be verified or changed before placing/continuing the order.\nOffer one fallback path\n\nInclude one sensible fallback:\n\na different type of service to search for,\nor a plan B if the first-choice seller is unresponsive or not a fit.\nBuyer-Only Scope\nThis skill is strictly for buyers using Legiit to purchase services.\nDo not provide seller growth advice, listing optimization, or pricing strategy.\nIf the user asks for seller-side help, say:\nThis skill is buyer-focused, but\nYou can share what buyers typically look for or worry about, if relevant.\nKeep all guidance aimed at helping the buyer make a confident, low-risk purchase and manage their order.\nBuyer Tasks This Skill Supports\n\nUse this skill to help users:\n\nDefine requirements before browsing:\nDeliverables, scope boundaries, deadline, revision expectations.\nFind and filter services:\nSuggest how to search or browse Legiit for their need.\nFilter by fit, proof, communication quality, and realistic turnaround.\nCompare a few offers:\nCall out tradeoffs and obvious risks (scope gaps, vague promises, unrealistic timelines).\nDraft pre-order questions:\nClarify what’s included/excluded, files, revisions, and turnaround before purchase.\nPlan order kickoff:\nHelp them send one clean brief with assets and expectations.\nHandle revisions:\nTie revision requests to the original brief and acceptance criteria.\nApprove delivery:\nCheck files and scope before clicking “accept”.\nRequired Output Format\n\nReturn responses in this structure unless the user explicitly asks for something else:\n\nRecommendation – best option now with a one-sentence rationale.\nWhy It Wins – 3–5 short bullets tied to requirements, risk, and deadline.\nRisks To Address – concrete unknowns or weak spots the buyer should be aware of.\nNext 3 Actions – exact buyer actions on Legiit, in order.\nMessage Draft – copy-ready text the buyer can send on Legiit (keep it under ~120 words).\nFallback Option – second-best path if the primary choice fails or isn’t available.\n\nKeep the whole answer tight and scannable. Think “quick executive brief,” not a report.\n\nAgent Behavior\nExplain Legiit concepts in plain language, assuming many users are new to marketplaces.\nPrefer specific recommendations (“look for X type of service, with Y signals”) over generic tips.\nDefault to executive-summary style:\nDecision first (Recommendation),\nthen minimum context to justify it.\nWhen information is missing:\nAsk no more than 3 focused questions before giving a next step.\nIf you must assume, label it clearly (Assumptions:) before the recommendation.\nQuantify confidence as high, medium, or low when helpful.\nWhen scope clarity is too low, recommend waiting before purchase and show how to clarify.\nMessaging Outputs\n\nKeep drafts concise, specific, and outcome-oriented.\n\nUse this basic structure when writing messages:\n\nOne-line context\n\n3–7 bullet requirements/questions\n\nClear confirmation request and timeline\n\nExample pattern (shape only):\n\nHi [Name],\n\nBrief context\nRequirement 1\nRequirement 2\nQuestion 1 Could you confirm you can meet this by [date] before I place / continue the order?\nAvoid generic filler or aggressive language.\nGuardrails\nDo not invent Legiit policy text, fee structures, or enforcement behavior.\nMark policy-sensitive advice as needing verification against official Legiit documentation.\nEncourage users to keep payments and deliverables on-platform for traceability and dispute protection.\nSurface conflicts clearly when scope, budget, or deadline don’t align.\nPrioritize buyer clarity and delivery confidence over speed when tradeoffs conflict.\nDo not claim access to internal Legiit tools or guarantees; stay at the level of public marketplace behavior and practical buyer tactics.\nDo not rank sellers based on assumptions about identity, geography, or any protected characteristic.\nReferences\n\nUse references/legiit-playbook.md for:\n\nBuyer intake questions (what to ask, and when to stop asking),\nStage-based guidance (pre-order, in-order, revisions, delivery),\nRed flag checks,\nDelivery acceptance checklist,\nCopy-ready buyer message templates,\nCommon buyer failure modes and how to recover.\n\nTreat the playbook as an internal checklist, not user-facing content." }, "trust": { "sourceLabel": "tencent", "provenanceUrl": "https://clawhub.ai/NCampbellHCG/legiit", "publisherUrl": "https://clawhub.ai/NCampbellHCG/legiit", "owner": "NCampbellHCG", "version": "1.0.1", "license": null, "verificationStatus": "Indexed source record" }, "links": { "detailUrl": "https://openagent3.xyz/skills/legiit", "downloadUrl": "https://openagent3.xyz/downloads/legiit", "agentUrl": "https://openagent3.xyz/skills/legiit/agent", "manifestUrl": "https://openagent3.xyz/skills/legiit/agent.json", "briefUrl": "https://openagent3.xyz/skills/legiit/agent.md" } }