agentsclimarketplace
Sign in

Export apm config

Skill synology-apm/apm-sdk-python/skills/export-apm-config

Export a structured snapshot of APM configuration (servers, storage, plans, hypervisors, file servers, M365 tenants and auto-backup rules) for audit or migration documentation. Use when the user asks to export, document, or snapshot the current APM setup.From its SKILL.md

Install
npx -y skills add synology-apm/apm-sdk-python --skill export-apm-config

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.2 KB, as published. Nobody here has run it

Export APM Configuration

When the user asks to export APM configuration, generate a configuration snapshot, or document the current APM setup for auditing or migration purposes:

See apm-mcp-conventions for shared conventions this skill relies on (list vs. get field completeness, pagination, permission modes).

  1. Collect all configuration objects in parallel:

    • apm://site — site info, external address (equivalent to calling get_site_info directly; prefer the resource when the client supports it)
    • apm://servers — all backup servers
    • apm://plans/protection — all protection plans (machine + M365): name/category/retention
    • apm://plans/retirement — all retirement plans
    • apm://plans/tiering — all tiering plans
    • list_remote_storages — remote storage destinations
    • list_hypervisors — registered hypervisors
    • apm://tenants — M365 tenants
    • list_machine_workloads with workload_types="fs" — file-server workloads
    • list_m365_auto_backup_rules for each tenant — M365 auto-backup rules and collab settings

  2. Organize the output as a configuration document with sections:

    # APM Configuration Export
## Site
## Backup Servers (N)
## Remote Storage (N)
## Hypervisors (N)
## Protection Plans (N)
## Retirement Plans (N)
## Tiering Plans (N)
## File Server Workloads (N)
## M365 Tenants (N)
## M365 Auto-Backup Rules (N)

  3. For each section, include the key fields:

    • Backup servers: name, model, role (primary/secondary), status, tiering plan
    • Plans: name, category, retention policy — all available from the apm://plans/protection list. Schedule frequency is not included there and isn't fetched by default (see apm-mcp-conventions for the list-vs-get caveat and when the extra per-plan calls are worth it).
    • Remote storage: name, type, endpoint, vault, encryption status
    • File server workloads: name, connection type, backup server, plan
    • M365 auto-backup rules: tenant, rule scope (Exchange/OneDrive/Teams Chat), included group IDs, collab settings

  4. The export describes configuration, not backup data. Sensitive fields (passwords, tokens) are never included in API responses.

    If the user wants more detail on one specific tenant or hypervisor than the list-level fields above provide, get_saas_tenant/get_hypervisor fetch that single record's full state (see apm-mcp-conventions for the list-vs-get caveat) — not needed for a full-environment export, only when drilling into one item.

  5. Present the export as a structured markdown document the user can save or share. Note the export timestamp so readers know when it was captured.

See also

  • provision-apm-config — the create/import counterpart; re-provision this same configuration on another APM server

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.