{"id":98125,"plugin_id":"plugin_asdk_app_6ae6b021e490819194a98a2512ec164c","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-16T13:47:10.555Z","digest":"99cf52621c0c63b9350ef114a44ca0a53dca02fd23464ccccadfbc5ad20df612","against":null,"payload":{"description":"Issue, email and verify certificates with CertSeal. Use when the user wants to give certificates to people who attended a course, event or program, email those certificates, check how many certificates they can still issue, fix a recipient's details, or check whether a certificate is genuine.","included_files":[],"name":"issue-certificates","skill_md_contents":"---\nname: issue-certificates\ndescription: Issue, email and verify certificates with CertSeal. Use when the user wants to give certificates to people who attended a course, event or program, email those certificates, check how many certificates they can still issue, fix a recipient's details, or check whether a certificate is genuine.\n---\n\n# Issue certificates with CertSeal\n\nCertSeal issues verifiable certificates for courses, events and programs the user runs. Every tool works in the one CertSeal workspace the user chose when connecting. Certificates are rendered from designs the user made in CertSeal; never describe them as AI-generated.\n\n## Issuing certificates\n\n1. **Find the batch.** A batch groups everyone who gets a certificate from one design, such as the attendees of one workshop. If the user names an existing batch, find it with `list_batches`. To start a new one, find the design with `list_designs`, then use `create_batch`. If the user doesn't say otherwise, the batch title becomes the course name, the organization's name the issuer, and the workspace's default email template is used.\n2. **Collect the recipients.** You need each person's name and email address. Use only the names and addresses the user gives you; never guess or invent them. If the list is unclear, ask.\n3. **Issue.** Use `issue_certificates`, up to 100 recipients per call. Issuing uses the workspace's certificate allowance; check it with `get_workspace_status` first if the user is issuing many.\n4. **Report back** each recipient's certificate ID. Say clearly whether anything was emailed.\n\n## Emailing certificates\n\n- Only email when the user asks to. Issuing and emailing are separate steps.\n- Use `list_recipients` to find who hasn't been emailed yet, then `send_certificate_emails`.\n- Emails can't be recalled. Before sending, tell the user how many emails will go out and to whom.\n- Sending needs the email permission the user chose when connecting. If it's missing, tell the user they can reconnect CertSeal and tick \"Email certificates to recipients\", or send the emails from the CertSeal app.\n- AI apps can send up to 200 certificate emails per organization per day.\n\n## Other tasks\n\n- **Fix a recipient's name, email or details:** `update_recipient`.\n- **Check a certificate:** `verify_certificate`, with the certificate ID (such as CERT-2026-003956-000001) or its link. It finds certificates issued from the connected workspace.\n- **How many certificates are left:** `get_workspace_status`. Quote `canStillIssue`, the number that actually limits issuing.\n\n## What CertSeal doesn't do\n\n- It doesn't make certificates, diplomas or other documents in the name of an institution the user doesn't run.\n- It can't change plans, billing or account settings; those are in the CertSeal app.\n- It can't create or edit designs or email templates; the user does that in the CertSeal app.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}