← Hive AxylCONTENT HISTORY
WHAT CHANGED
Update to Hive Axyl
Snapshot Oct 24, 2026 · 13:42 UTC · version 2.1.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Hive Axyl and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Use when implementing an Axyl feature that is not covered by a more specific skill; verify the official Axyl developer guide before coding uncovered login, payment, push, mailbox, TCB Connector, account/auth, or service access control behavior.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 246
},
{
"relative_path": "references/product-guides.md",
"size_in_bytes": 3071
}
],
"name": "axyl-developer-guide",
"skill_md_contents": "---\nname: axyl-developer-guide\ndescription: Use when implementing an Axyl feature that is not covered by a more specific skill; verify the official Axyl developer guide before coding uncovered login, payment, push, mailbox, TCB Connector, account/auth, or service access control behavior.\nmetadata:\n short-description: Implement Axyl features from official Axyl guides\n---\n\n# Axyl Developer Guide\n\nUse this skill when the user asks to develop or modify an Axyl feature and no more specific skill covers the requested feature or business flow.\n\n## Scope\n\n- Prefer a feature-specific skill when one exists. For mixed requests, use that skill for the covered portion and this skill only for the uncovered Axyl behavior.\n- Supported Axyl product areas are login, payment, push notification, mailbox, TCB Connector, account and authentication, and service access control.\n- Do not treat the absence of a feature-specific skill as evidence that Axyl does not support the requested feature.\n- Do not implement Axyl SDK, API, console, permission, or callback behavior from memory. Verify the current official guide first.\n\n## Official Documentation\n\nThe Axyl guide root is:\n\nhttps://developers.hiveplatform.ai/axyl/\n\nWhen implementation details are needed, read the relevant page under that Axyl documentation site. If a product-specific route is available, use [references/product-guides.md](references/product-guides.md) as the routing index. Treat that reference only as an index; never implement from the index text alone.\n\n## Workflow\n\n1. Identify the requested Axyl product, feature, SDK or API surface, target platform, and existing project conventions.\n2. Read [references/product-guides.md](references/product-guides.md) and select only the relevant product row.\n3. Open the product-specific guide URL when it is filled in. If the product URL is blank or stale, start from the Axyl guide root and navigate or search within the official Axyl developer site for the requested product and feature.\n4. Follow the documentation to the exact function, setup, configuration, callback, result-code, or platform-specific page required for the task. Do not rely on landing-page summaries.\n5. If the official Axyl page cannot be accessed or does not document the requested behavior, tell the user what could not be verified instead of guessing.\n6. Implement using the verified names, types, call order, result handling, and prerequisites from the official guide while preserving the project's existing architecture and style.\n\n## Implementation Rules\n\n- Match the SDK version, platform, engine, language, async model, and error-handling style already used by the project whenever possible.\n- Include required initialization, console setup, permissions, platform configuration, and dependency changes when the guide requires them.\n- Never invent an Axyl class, method, enum, parameter, callback, result code, endpoint, permission, or console setting.\n- If two official pages conflict and the conflict affects correctness, report the conflict and avoid implementing the affected portion until it is resolved.\n- If documentation requires user-side console configuration or credentials, make the code changes that are safe locally and clearly report what the user must configure outside the repository.\n\n## Completion Notes\n\nWhen finished, report:\n\n- what was changed;\n- which Axyl guide page or pages governed the implementation;\n- any console, credential, platform, permission, or deployment setup the user still needs to complete;\n- what was verified locally and what remains unverified.\n"
}SHA-256 of public snapshot: 378bbcd6509ed87113ef4edfcf4a2c3a3792a8e88fdcc7d26bd4600680b73a23