SyncSign AI Skill

SyncSign AI Skill packages AI-driven operations for SyncSign device management and content delivery scenarios. By calling the SyncSign public Web API, it allows users to use natural language to retrieve account data, inspect Hub and Display information, diagnose node issues, and submit rendering jobs to screens.

This skill is suitable for integrating SyncSign capabilities into AI assistants, intelligent operations workflows, internal tool platforms, and automation pipelines. Users do not need to call the API manually. They can simply describe what they want to do, and the AI can execute the corresponding action.

How to Use and Deploy

This skill currently works with the SyncSign public Web API. Before using it, prepare a SyncSign API Key.

Two common deployment methods are supported:

  1. Claude plugin marketplace

    /plugin marketplace add syncsign/skills
/plugin install syncsign-api@syncsign-marketplace

  2. skills.sh or npx

    npx skills add syncsign/skills@syncsign-api

After installation, configure the API key in the skill runtime directory.

  1. Create a .env file in the skill root directory, or copy .env.example to .env.

  2. Add the following setting:

    SYNCSIGN_API_KEY=your_syncsign_api_key

  3. Save the file and run the request again.

If you do not have an API key yet, open the SyncSign client, go to the Settings page, and copy the API key there.

Note

  • SYNCSIGN_API_BASE_URL is optional and does not need to be configured in most cases.

  • The current skill only relies on the API key. It does not require account-password login, token exchange, or credential recovery.

What This Skill Can Do

The current skill supports the following capabilities:

  • Retrieve the SyncSign account information associated with the current API key.

  • List the Hubs and devices under the current account.

  • View details for a specific Hub.

  • List all Displays, or list Displays under a specific Hub.

  • View details for a specific Display by node_id.

  • Query a specific Display under a specific Hub by sn and node_id.

  • Diagnose the calendar sync status of a specific Display.

  • Check whether a Display is bound to a calendar.

  • Check whether the calendar subscription is valid, for example whether watchResourceId and watchExpiration are still effective.

  • Analyze possible reasons for no-refresh or no-sync issues on supported models.

  • Submit a rendering job to a single Display.

  • Submit the same rendering job to multiple Displays in batch.

  • Check rendering task status by render_id.

Focused Diagnostic Support

For the following Display models:

  • D75C-LEWI

  • D42C-LE

  • D29C-LE

The skill can use real-time API responses to help determine:

  • Whether the Display is online.

  • Whether a calendar is bound.

  • Whether the calendar subscription has expired or become invalid.

  • Whether the Hub is offline.

  • Whether there may be a low-battery issue.

  • Whether there may be a weak-signal issue.

These diagnostics are based only on fields actually returned by the API. The skill does not invent device status, which makes it suitable for online support, remote troubleshooting, and first-pass issue isolation.

Typical Natural Language Requests

Users can issue requests in natural language, for example:

  • “Show my SyncSign account information.”

  • “List all Hubs under the current account.”

  • “Show all Displays under this Hub.”

  • “Get the screen details for node_id xxx.”

  • “Diagnose why this Display is not syncing its calendar.”

  • “Render this announcement and send it to the target Display.”

  • “Push the same content to multiple Displays.”

  • “Check whether this render job has finished.”

Suitable Business Scenarios

  • AI customer service and technical support

  • Device operations assistants

  • Screen content publishing automation

  • Multi-store or multi-meeting-room device inspection

  • Integration with internal operations platforms, knowledge bases, and automation workflows

Capability Boundaries

To keep results reliable and secure, the current skill focuses on capabilities already exposed by the SyncSign public API. It does not currently include:

  • Account-password login

  • Token retrieval or login session recovery

  • Calls to non-public APIs

  • Inference beyond the fields returned by the API