membranedev/application-skills
12 skills12.7k installs2.1k starsGitHub
Install
npx skills add https://github.com/membranedev/application-skillsSkills in this repo
1Google DriveGoogle Drive is an agent skill that wires your coding agent to Google Drive through Membrane’s CLI so you can work with cloud files, folders, permissions, and shared links instead of rebuilding OAuth and token refresh. Solo builders use it when a product or internal workflow must read, write, organize, or share Drive assets—think document pipelines, customer file intake, or agent-assisted folder hygiene. The skill documents installing @membranehq/cli globally, authenticating with membrane login, and leaning on Membrane for credentials while you focus on integration logic aligned with Google’s Drive API docs. It assumes network access and a Membrane account (free tier noted). Pair it with backend or agent features that need durable file storage in Google’s ecosystem; it is not a substitute for choosing Drive versus S3—that decision stays in your architecture notes.2.1kinstalls2ConfluenceConfluence is an agent skill for solo builders and tiny teams who want agents to interact with Atlassian Confluence—spaces, pages, attachments, and blog posts—without maintaining OAuth clients and token refresh logic. It runs through the Membrane CLI: install globally, log in with tenant and client name, then invoke named actions against live Confluence data. The skill frames Confluence as the org’s documentation hub for specs, meeting notes, and knowledge base content, which makes it valuable when your agent must publish build notes, fetch requirements, or sync runbooks. Network access and a Membrane account (free tier supported) are required. It complements other application-skills in the same repo for multi-tool workflows. Choose it when the user explicitly wants Confluence data operations; skip it when documentation lives only in-repo with no Atlassian footprint.1.4kinstalls3Microsoft SharepointMicrosoft SharePoint is a Membrane-backed agent skill for organizations that already store files and collaboration data in SharePoint Online. Solo and indie builders use it when an AI coding agent must list sites, work with lists and list items, or interact with files and folders without spending a sprint on OAuth, token refresh, and Graph endpoint plumbing. The SKILL.md positions SharePoint as a central repository and team hub, and routes all interaction through the Membrane CLI after `membrane login --tenant --clientName=<agentType>`. That pattern fits agent-first products, internal automation, and SaaS features that sync customer or ops content from SharePoint. Install the CLI globally, authenticate once per tenant, then invoke named Membrane actions with parameters as your integration logic requires. It is a task integration skill: narrow scope, high leverage when SharePoint is already the system of record.1.3kinstalls4SalesforceSalesforce is a Membrane-backed agent skill that helps solo builders integrate cloud CRM data into agents and applications using the Membrane CLI instead of bespoke OAuth plumbing. It documents how Salesforce teams use Accounts, Contacts, Leads, Opportunities, Cases, Tasks, and reporting objects, and steers you toward discovering available actions with search and info commands before writing integration logic. Authentication runs through Membrane login with tenant and client name, after which credentials refresh automatically while you focus on business workflows like syncing leads or updating opportunities. The skill emphasizes running actions programmatically, loading remote skill references for full connector docs, and falling back to authenticated HTTP requests when no packaged action exists. It fits SaaS and agent products that need sales and marketing automation during build. Network access and a Membrane account are required; compatibility is framed for coding agents that can execute terminal commands safely.1.3kinstalls5Boxbox is a Membrane application skill that lets coding agents manage Box content—folders, file versions, collaborations, users, groups, tasks, events, and search—using the Membrane CLI instead of custom OAuth plumbing. Solo builders shipping SaaS or internal tools for teams on Box install it when they need reliable, documented API operations from the terminal or agent session. The skill emphasizes authentication flow (`membrane login`), action naming aligned with Box’s object model, and network-backed calls through Membrane’s hosted bridge. It is intermediate complexity: you should understand which Box entity you are mutating and respect enterprise sharing rules. Prism lists it as a task integration for Build, not a replacement for Box’s admin console or DLP policy design.1.2kinstalls6DropboxDropbox is a phase-specific agent skill for wiring Dropbox cloud storage into agent-driven workflows using the Membrane platform. Solo builders reach for it when users ask to list folders, manage files, or work with shared links without implementing OAuth refreshes by hand. The skill documents Membrane CLI installation, tenant login (browser or headless URL), and the Dropbox object model at a high level—files, shared links, and folders—delegating concrete action names to Membrane’s integration layer. It fits SaaS features that sync documents, backup pipelines, or personal-cloud automations where Dropbox remains the system of record. Network access and a valid Membrane account are required; official Dropbox API documentation is the underlying contract. Treat it as an integration playbook, not a full Dropbox SDK tutorial.1.2kinstalls7OnedriveThe onedrive skill teaches agents to manage Microsoft OneDrive through Membrane instead of hand-rolling Microsoft Graph auth. Solo builders shipping SaaS, internal tools, or agent workflows that read and write user documents in the cloud get a repeatable pattern: install the CLI, run membrane login with tenant and client name, then call documented actions for files, folders, permissions, and search. Membrane centralizes OAuth and token refresh so the agent spends cycles on integration logic—listing folders, syncing uploads, or checking sharing—not plumbing. It fits the Build phase when you already chose your stack and need dependable storage backed by accounts users already have at work. Pair it with other Membrane application skills when a feature spans CRM, email, and file storage. Review Membrane’s security model and your tenant policies before granting agents production access.1.2kinstalls8HubspotHubSpot is a Membrane-backed agent skill that lets solo builders interact with HubSpot CRM and marketing automation data without hand-rolling OAuth and token refresh. When a user wants to read or update contacts, companies, deals, tickets, or run HubSpot-oriented workflows, the agent installs the Membrane CLI, logs in with tenant context, and invokes Membrane actions against the official HubSpot APIs. It fits indie SaaS and agent products that need sales and marketing data in the loop during implementation. The skill emphasizes integration logic over auth plumbing, which matters when you are shipping fast with Claude Code or similar agents. Network access and a Membrane account are required; triggers are natural-language requests to work with HubSpot data or automate CRM tasks.815installs9Microsoft OutlookMicrosoft Outlook is a Membrane application skill that lets solo builders and agents manage Outlook-backed email, calendaring, contacts, and tasks through a consistent CLI instead of hand-rolling Microsoft Graph auth. You install the Membrane CLI, log in with tenant and client name, then call action-oriented operations for attachments, events, mailboxes, users, groups, and rooms while Membrane refreshes tokens in the background. It fits SaaS products, internal tools, and agent workflows that must sync with how businesses already communicate in Microsoft 365. Use it when the user explicitly wants Outlook data or workflows—not as a general email abstraction. Pair it with your product’s business logic in the integrations layer and validate scopes and compliance before shipping customer-facing automation.539installs10SlackSlack is a Membrane application skill that lets a solo builder’s agent interact with Slack workspace data—channels, messages, and users—using the official Slack API surface documented at api.slack.com. It is for builders who want agents to automate comms workflows (post updates, pull threads, sync records) without spending a sprint on OAuth plumbing. Membrane handles authentication and token refresh after you install the global CLI and log in with a valid Membrane account (free tier supported). The skill expects network access and pairs naturally with other Membrane application skills when you orchestrate cross-app automations. Invoke it when the user explicitly wants to work with Slack data; keep human approval on destructive or broad channel actions. It is an integration skill package, not a hosted Slack bot framework—your agent runs the Membrane commands in your environment.530installs11Zoho CrmZoho CRM is an agent skill that connects your Claude Code, Cursor, or Codex workflow to Zoho CRM through the Membrane CLI. It is aimed at solo and indie builders who are shipping SaaS, agents, or APIs that need dependable CRM operations—listing and updating leads, contacts, accounts, deals, tasks, calls, and meetings—without spending days on OAuth flows and token refresh. Invoke it whenever a user asks to interact with Zoho CRM data, automate pipeline updates, or prototype marketing and sales workflows inside an agent session. Membrane owns authentication and credential lifecycle so you focus on integration logic and record-level behavior. The skill documents standard Zoho modules and points to official API v6 documentation, making it a practical bridge between conversational development and a live CRM tenant.529installs12Dynamics CrmDynamics-crm is an agent skill that standardizes how solo builders and small teams talk to Microsoft Dynamics 365 through the Membrane integration layer. Dynamics is the Microsoft CRM and ERP suite for sales, marketing, and service workflows—often chosen alongside or instead of Salesforce in mid-market accounts. The skill explains what entities matter for day-one integrations, points to official Microsoft Learn documentation, and routes all runtime access through Membrane so OAuth and token rotation do not become a weekend project. It fits builders shipping internal tools, vertical SaaS, or automation agents that must create leads, update opportunities, or mirror account data. Invoke it when the user explicitly wants Dynamics 365 data in chat-driven workflows. Pair it with your own data-mapping and idempotency rules before writing to production tenants.526installs