Using Skippy

Choose a supported task

In a new Claude task, ask for the named skill and state the program and your intended result. Review the skill's requested inputs and any output before sending or changing a record.

Some workflows need Box, Monday, HubSpot, DocuSign or Slack through your own approved account. A successful Skippy connection does not grant those permissions or prove that a workflow has completed its external steps.

Read the evidence and freshness

For each factual answer, look for its named source and date. A source can be available while an import or the selected registry publication is older. If freshness is unclear, ask for the source time and the current Skippy data-health state. Do not treat a healthy connection as proof that every source refreshed successfully.

Many files remain in Box because they are cataloged for availability, are outside the current profile extraction scope, or need a different authorized workflow. “On file” does not mean missing, failed or important to a specific profile. A structured profile is not certified complete by document counts. When a fact matters, consult the current original in Box or the owning system and compare it with the cited Skippy answer.

Work through a task

1. Open a new private Claude task in the Donor Nexus organization and confirm the connector and plugin are enabled.
2. State the real work question and invoke the specific skill. Supply only a case you are authorized to handle.
3. Check the source names, dates, program and any missing or conflicting evidence. Ask the skill to identify what it could not verify.
4. Review the resulting document, checklist or proposed action against the current original. Follow the normal staff approval and sending process.
5. If the task stopped, inspect any file, folder or draft already created before retrying. Report the exact blocked step.

This guide includes no donor example. A staff walkthrough requires an authorized current case; development demonstrations require an approved, adequately anonymized real record.

Pause and resume

There is a server-side pause/resume control for scheduled work. A desktop one-click applet is described in source but must be installed and demonstrated for the person using it before it becomes their routine control. Ask the designated operations owner which control is currently available and have them confirm the observed paused or resumed state. Pausing Skippy does not replace the normal handling of already-created drafts or source-system work.

The reviewed account release adds a separate administrator page for creating a named staff account, requesting a password reset, and disabling an account. It is not installed yet. Once enabled, the administrator must confirm the recipient and one approved existing access tier before Cognito sends an invitation. A reset asks Cognito to email a code and sign out old tokens; the recipient must finish the provider's recovery steps. A disabled account cannot sign in. These actions do not change administrator grants or let a staff member choose their own data access. Until the controls are installed and verified, request account help from the designated Donor Nexus administrator. If an action says its outcome is unconfirmed, do not repeat it; ask the operator to check the account state first.