HIPAA Safe Harbor Coverage Audit
maziyarpanahi/openmed
Checks OpenMed de-identified clinical text against the 18 HIPAA Safe Harbor identifier categories and reports gaps and residual re-identification risk.
Data handling best practices for Lindy AI agents. An agent skill from jeremylongshore/tons-of-skills-marketplace.
Install Lindy Data Handling
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-data-handling -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace lindy-data-handling --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/lindy-data-handling .claude/skills/lindy-data-handling && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "lindy-data-handling" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/lindy-data-handling into .claude/skills/lindy-data-handling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lindy-data-handling", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/lindy-data-handlingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-data-handling -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace lindy-data-handling --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/.curated/lindy-data-handling .agents/skills/lindy-data-handling && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "lindy-data-handling" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/lindy-data-handling into .agents/skills/lindy-data-handling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lindy-data-handling", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-data-handling -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace lindy-data-handling --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/.curated/lindy-data-handling .cursor/skills/lindy-data-handling && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "lindy-data-handling" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/lindy-data-handling into .cursor/skills/lindy-data-handling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lindy-data-handling", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jeremylongshore/tons-of-skills-marketplace.git --path skills/.curated/lindy-data-handling--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-data-handling -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace lindy-data-handling --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/.curated/lindy-data-handling .gemini/skills/lindy-data-handling && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "lindy-data-handling" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/lindy-data-handling into .gemini/skills/lindy-data-handling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lindy-data-handling", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jeremylongshore/tons-of-skills-marketplace lindy-data-handlingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-data-handling -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/.curated/lindy-data-handling .github/skills/lindy-data-handling && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "lindy-data-handling" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/lindy-data-handling into .github/skills/lindy-data-handling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lindy-data-handling", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-data-handling -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace lindy-data-handling --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/.curated/lindy-data-handling .opencode/skills/lindy-data-handling && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "lindy-data-handling" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/lindy-data-handling into .opencode/skills/lindy-data-handling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lindy-data-handling", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
lindy-data-handling- GitHub stars
- 2.8k
- Token cost
- ~1.9k tokens
- SKILL.md length
- 707 words
- Files
- 2 (incl. references)
- Skills in repo
- 3,342
- Repo updated
- First seen
- Licence
- MIT
At a glance
Data handling best practices for Lindy AI agents. An agent skill from jeremylongshore/tons-of-skills-marketplace.
- Works in 8 steps: Classify Data in Agent Workflows → PII Controls in Agent Prompts → Knowledge Base Data Safety → …
- Managing sensitive data in agent workflows
- SKILL.md covers Overview, Prerequisites, Lindy Data Architecture and Instructions, plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Lindy Data Handling is an agent skill from jeremylongshore/tons-of-skills-marketplace. Data handling best practices for Lindy AI agents. Use when managing sensitive data in agent workflows, implementing data privacy controls, or ensuring compliance. Trigger with phrases like "lindy data", "lindy privacy", "lindy PII", "lindy data handling", "lindy GDPR", "lindy HIPAA".
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/implementation-guide.md`). Compatibility notes: Designed for Claude Code
It sits in Legal & Compliance, covering Privacy and GDPR and Healthcare and finance regulation. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.
When your agent uses it
- Managing sensitive data in agent workflows
- Implementing data privacy controls
- Ensuring compliance
- With phrases like lindy data
Example prompts
- “lindy data”
- “lindy privacy”
- “lindy PII”
- “/lindy-data-handling”
Requirements
- Compatibility (from SKILL.md): Designed for Claude Code
- Pre-approved tools (allowed-tools): Read, Write, Edit
Workflow steps
8 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteEdit
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
lindy.aigdpr.eudocs.lindy.ai
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Designed for Claude Code
From compatibility in the SKILL.md frontmatter.
Context cost
Lindy Data Handling loads about 1.9k tokens when it runs, and up to ~3.7k if it reads all its reference files. Until then it costs about 76 tokens; SKILL.md has 707 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 707 words, ~1,876 tokens.
Download SKILL.mdSave it as
.claude/skills/lindy-data-handling/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- lindy-data-handling
- description
- Data handling best practices for Lindy AI agents. Use when managing sensitive data in agent workflows, implementing data privacy controls, or ensuring compliance. Trigger with phrases like "lindy data", "lindy privacy", "lindy PII", "lindy data handling", "lindy GDPR", "lindy HIPAA".
- allowed-tools
- Read, Write, Edit
- compatibility
- Designed for Claude Code
- version
- 1.20.0
- license
- MIT
- author
- Jeremy Longshore <jeremy@intentsolutions.io>
- tags
- saas, lindy, compliance
Lindy Data Handling
Overview
Lindy agents process data through triggers, LLM calls, actions, knowledge bases, and memory. Data flows through Lindy's managed infrastructure with AES-256 encryption at rest and in transit. This skill covers data classification, PII handling, prompt-level data controls, and regulatory compliance.
Prerequisites
- Understanding of data types processed by your agents
- Knowledge of applicable regulations (GDPR, CCPA, HIPAA)
- For HIPAA: Business Associate Agreement (BAA) with Lindy (Enterprise plan)
Lindy Data Architecture
| Component | Data Storage | Retention |
|---|---|---|
| Tasks | Task inputs, outputs, step data | Visible in dashboard |
| Memory | Persistent snippets across tasks | Until manually deleted |
| Context | Per-task accumulated context | Task lifetime only |
| Knowledge Base | Uploaded files, crawled sites | Until manually removed |
| Integrations | OAuth tokens, connection data | Until disconnected |
| Computer Use | Browser session, screenshots | 30 days after last use |
Instructions
Step 1: Classify Data in Agent Workflows
Map what data each agent processes:
| Data Category | Examples | Handling |
|---|---|---|
| Public | Product info, FAQs, pricing | No restrictions |
| Internal | Sales reports, meeting notes | Limit to authorized agents |
| Confidential | Customer emails, CRM data | Access controls + audit |
| Restricted | PII, PHI, payment data | Minimize exposure + compliance |
Step 2: PII Controls in Agent Prompts
Add data handling instructions directly to agent prompts:
## Data Handling Rules
- Never include full email addresses in summaries — use "[name]@[domain]"
- Redact phone numbers in logs — show only last 4 digits
- Do not forward customer personal information to Slack channels
- When storing to spreadsheet, omit columns: email, phone, address
- If asked to share customer data externally, decline and escalateStep 3: Knowledge Base Data Safety
Knowledge base files are searchable by the agent. Control what goes in:
DO upload:
- Product documentation
- FAQ articles
- Policy documents
- Public knowledge articles
DO NOT upload:
- Customer databases with PII
- Credentials or API keys
- Internal HR documents (unless agent specifically needs them)
- Financial records with account numbers
Resync considerations: KB auto-refreshes every 24 hours. If you upload sensitive content by mistake, remove it AND trigger a manual Resync.
Step 4: Secure Memory Usage
Agent memories persist across all future tasks. Be deliberate:
Safe memory: "Customer prefers email communication over phone"
Safe memory: "Billing questions should escalate to finance@company.com"
Risky memory: "John Smith's SSN is 123-45-6789" ← NEVER store PII in memory
Risky memory: "API key for Stripe: sk_live_xxxx" ← NEVER store secretsAdd to agent prompt:
## Memory Rules
- Never store personally identifiable information (PII) in memory
- Never store credentials, API keys, or passwords in memory
- Memories should contain preferences, patterns, and procedures onlyStep 5: Computer Use Data Isolation
If using Computer Use (browser automation):
- Sessions persist for 30 days with saved credentials
- Enable Incognito mode for sessions handling sensitive data
- Use dedicated (not shared) computer assignments for sensitive agents
- Review screenshots captured during execution for data exposure
Step 6: Integration Account Isolation
- Authorize dedicated service accounts per agent (not personal accounts)
- Use Gmail with a team alias, not an individual inbox
- Create read-only database credentials where possible
- Revoke access immediately when an agent is decommissioned
Step 7: Regulatory Compliance
GDPR (EU Data Protection):
- Document what personal data each agent processes
- Ensure agents only process data with valid legal basis
- Implement data subject access/deletion capabilities
- Agent prompt includes "do not retain personal data beyond task completion"
- Review Lindy's data processing agreement
CCPA (California Consumer Privacy):
- Identify agents processing California resident data
- Ensure opt-out mechanisms exist for data processing
- Agent prompt prevents selling/sharing personal information
HIPAA (Healthcare):
- Enterprise plan with BAA in place
- Agents only access minimum necessary PHI
- No PHI in agent memory or knowledge base
- Audit trail enabled for all PHI access
- Agent prompt includes PHI handling restrictions
Show full SKILL.md (237 more words)Show less
Step 8: Data Retention Management
Agent Prompt Addition:
## Data Retention
- Do not reference data from tasks older than 30 days
- Clear task context after each run (do not accumulate indefinitely)
- When updating memory, remove outdated entries
- Summarize customer interactions, do not store verbatim transcriptsData Handling Checklist
- Each agent's data classification documented
- PII handling rules in every agent prompt
- Knowledge base audited for sensitive content
- Memory creation restricted (no PII, no secrets)
- Integration accounts isolated per agent
- Computer Use sessions set to dedicated + incognito where needed
- Regulatory compliance requirements mapped
- BAA in place if handling healthcare data
- Data retention policy defined and enforced in prompts
Output
Produce a data-handling record for each agent that identifies its data classification, permitted integrations, memory policy, retention decision, and the owner responsible for periodic review. Escalate restricted-data workflows that lack a documented legal basis, BAA, or deletion path before enabling them.
Examples
For a lead-routing agent, record customer email as confidential, prohibit it from agent memory and public Slack channels, limit the CRM integration to a service account, and retain only an aggregate routing metric. If the workflow starts processing health information, stop deployment until the Enterprise BAA and minimum-necessary controls are confirmed.
Error Handling
| Issue | Cause | Solution |
|---|---|---|
| PII in Slack channel | Agent forwarded customer email | Add "never forward PII to Slack" to prompt |
| Sensitive file in KB | Uploaded by mistake | Remove file + trigger KB resync immediately |
| Memory contains PII | Agent auto-created memory | Delete memory + add "never store PII" to prompt |
| Audit finding | Agent accessing unnecessary data | Remove unused integrations from agent |
Resources
Next Steps
Proceed to lindy-enterprise-rbac for access control.
© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in skills/.curated/lindy-data-handling of jeremylongshore/tons-of-skills-marketplace.
- SKILL.md
- references/implementation-guide.md
Open the folder on GitHubat commit cfae287
Compare with similar skills
Lindy Data Handling next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Lindy Data Handling this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.9k | Automated safety check: Pass | MIT | |
| HIPAA Safe Harbor Coverage Auditmaziyarpanahi/openmed | 5.5k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Hipaa ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance | 946 | 1 repos | ~2.3k | Automated safety check: Pass | MIT | |
| Audit Reportharness/harness-skills | 115 | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Anne WojcickiK-Dense-AI/mimeographs | 129 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Dpa Checklist ReviewLegalQuants/lq-ai | 150 | — | ~3.7k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Hipaa Compliance
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
Expert HIPAA compliance assistant for healthcare and software contexts.
Audit Report
harness/harness-skills
Generate audit reports and compliance trails using Harness audit trail data via MCP v2 tools.
Anne Wojcicki
K-Dense-AI/mimeographs
Applies the strategic frameworks and mental models of Anne Wojcicki, co-founder and CEO of 23andMe.
Dpa Checklist Review
LegalQuants/lq-ai
A skill your agent uses when the user provides a Data Processing Agreement, Data Processing Addendum, or HIPAA Business Associate Agreement and asks whether it contains the terms required under the…
Auditing Deidentification Runs
maziyarpanahi/openmed
Produce a signed, reproducible, no-PHI audit trail for an OpenMed de-identification run via deidentify(audit=True).
More from jeremylongshore/tons-of-skills-marketplace
All 3,342 skills in this repoPerforming Security Code Review
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.
Adapting Transfer Learning Models
jeremylongshore/tons-of-skills-marketplace
Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.
Agent Context Loader
jeremylongshore/tons-of-skills-marketplace
Execute proactive auto-loading: automatically detects and loads agents.md files.
Aggregating Performance Metrics
jeremylongshore/tons-of-skills-marketplace
Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.
Analyzing Capacity Planning
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.
Analyzing Database Indexes
jeremylongshore/tons-of-skills-marketplace
Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.
Related
Categories
Questions about Lindy Data Handling
What does Lindy Data Handling do?
Data handling best practices for Lindy AI agents. An agent skill from jeremylongshore/tons-of-skills-marketplace. Lindy Data Handling is an agent skill from jeremylongshore/tons-of-skills-marketplace. Data handling best practices for Lindy AI agents.
When should I use Lindy Data Handling?
Lindy Data Handling fits situations like: managing sensitive data in agent workflows; implementing data privacy controls; ensuring compliance; with phrases like lindy data.
How do I install Lindy Data Handling in Claude Code?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-data-handling -a claude-code`. Or copy the skill folder (skills/.curated/lindy-data-handling in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/lindy-data-handling in your project. Claude Code loads it when a task matches its description.
How do I install Lindy Data Handling in Codex?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-data-handling -a codex`. Or copy the skill folder (skills/.curated/lindy-data-handling in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/lindy-data-handling in your project. Codex loads it when a task matches its description.
Can I use Lindy Data Handling in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-data-handling -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/lindy-data-handling, .gemini/skills/lindy-data-handling, .github/skills/lindy-data-handling and .opencode/skills/lindy-data-handling in your project.
What does Lindy Data Handling need to run?
SKILL.md names no scripts, command-line tools or credentials: Lindy Data Handling is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Edit. Compatibility (from SKILL.md): Designed for Claude Code.
Does Lindy Data Handling access the network?
SKILL.md names 3 domains. As links in the text: lindy.ai, gdpr.eu and docs.lindy.ai. This is read from the text; nothing was executed.
Is Lindy Data Handling safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Lindy Data Handling use?
Lindy Data Handling is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Lindy Data Handling use?
About 1.9k tokens (SKILL.md is roughly 7.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.8k tokens, read only when the agent opens those files.
What are the alternatives to Lindy Data Handling?
Skills that share tags, products or a category with Lindy Data Handling: HIPAA Safe Harbor Coverage Audit (maziyarpanahi/openmed, 5.5k stars), Hipaa Compliance (Sushegaad/Claude-Skills-Governance-Risk-and-Compliance, 946 stars), Audit Report (harness/harness-skills, 115 stars) and Anne Wojcicki (K-Dense-AI/mimeographs, 129 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Lindy Data Handling?
jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.
Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.