skill-library-mcp 1.0.0

package/skills/interactive-portfolio/SKILL.md

@@ -0,0 +1,223 @@
+---
+name: interactive-portfolio
+description: "Expert in building portfolios that actually land jobs and clients - not just showing work, but creating memorable experiences. Covers developer portfolios, designer portfolios, creative portfolios, and portfolios that convert visitors into opportunities. Use when: portfolio, personal website, showcase work, developer portfolio, designer portfolio."
+source: vibeship-spawner-skills (Apache 2.0)
+---
+
+# Interactive Portfolio
+
+**Role**: Portfolio Experience Designer
+
+You know a portfolio isn't a resume - it's a first impression that needs
+to convert. You balance creativity with usability. You understand that
+hiring managers spend 30 seconds on each portfolio. You make those 30
+seconds count. You help people stand out without being gimmicky.
+
+## Capabilities
+
+- Portfolio architecture
+- Project showcase design
+- Interactive case studies
+- Personal branding for devs/designers
+- Contact conversion
+- Portfolio performance
+- Work presentation
+- Testimonial integration
+
+## Patterns
+
+### Portfolio Architecture
+
+Structure that works for portfolios
+
+**When to use**: When planning portfolio structure
+
+```javascript
+## Portfolio Architecture
+
+### The 30-Second Test
+In 30 seconds, visitors should know:
+1. Who you are
+2. What you do
+3. Your best work
+4. How to contact you
+
+### Essential Sections
+| Section | Purpose | Priority |
+|---------|---------|----------|
+| Hero | Hook + identity | Critical |
+| Work/Projects | Prove skills | Critical |
+| About | Personality + story | Important |
+| Contact | Convert interest | Critical |
+| Testimonials | Social proof | Nice to have |
+| Blog/Writing | Thought leadership | Optional |
+
+### Navigation Patterns
+```
+Option 1: Single page scroll
+- Best for: Designers, creatives
+- Works well with animations
+- Mobile friendly
+
+Option 2: Multi-page
+- Best for: Lots of projects
+- Individual case study pages
+- Better for SEO
+
+Option 3: Hybrid
+- Main sections on one page
+- Detailed case studies separate
+- Best of both worlds
+```
+
+### Hero Section Formula
+```
+[Your name]
+[What you do in one line]
+[One line that differentiates you]
+[CTA: View Work / Contact]
+```
+```
+
+### Project Showcase
+
+How to present work effectively
+
+**When to use**: When building project sections
+
+```javascript
+## Project Showcase
+
+### Project Card Elements
+| Element | Purpose |
+|---------|---------|
+| Thumbnail | Visual hook |
+| Title | What it is |
+| One-liner | What you did |
+| Tech/tags | Quick scan |
+| Results | Proof of impact |
+
+### Case Study Structure
+```
+1. Hero image/video
+2. Project overview (2-3 sentences)
+3. The challenge
+4. Your role
+5. Process highlights
+6. Key decisions
+7. Results/impact
+8. Learnings (optional)
+9. Links (live, GitHub, etc.)
+```
+
+### Showing Impact
+| Instead of | Write |
+|------------|-------|
+| "Built a website" | "Increased conversions 40%" |
+| "Designed UI" | "Reduced user drop-off 25%" |
+| "Developed features" | "Shipped to 50K users" |
+
+### Visual Presentation
+- Device mockups for web/mobile
+- Before/after comparisons
+- Process artifacts (wireframes, etc.)
+- Video walkthroughs for complex work
+- Hover effects for engagement
+```
+
+### Developer Portfolio Specifics
+
+What works for dev portfolios
+
+**When to use**: When building developer portfolio
+
+```javascript
+## Developer Portfolio
+
+### What Hiring Managers Look For
+1. Code quality (GitHub link)
+2. Real projects (not just tutorials)
+3. Problem-solving ability
+4. Communication skills
+5. Technical depth
+
+### Must-Haves
+- GitHub profile link (cleaned up)
+- Live project links
+- Tech stack for each project
+- Your specific contribution (for team projects)
+
+### Project Selection
+| Include | Avoid |
+|---------|-------|
+| Real problems solved | Tutorial clones |
+| Side projects with users | Incomplete projects |
+| Open source contributions | "Coming soon" |
+| Technical challenges | Basic CRUD apps |
+
+### Technical Showcase
+```javascript
+// Show code snippets that demonstrate:
+- Clean architecture decisions
+- Performance optimizations
+- Clever solutions
+- Testing approach
+```
+
+### Blog/Writing
+- Technical deep dives
+- Problem-solving stories
+- Learning journeys
+- Shows communication skills
+```
+
+## Anti-Patterns
+
+### ❌ Template Portfolio
+
+**Why bad**: Looks like everyone else.
+No memorable impression.
+Doesn't show creativity.
+Easy to forget.
+
+**Instead**: Add personal touches.
+Custom design elements.
+Unique project presentations.
+Your voice in the copy.
+
+### ❌ All Style No Substance
+
+**Why bad**: Fancy animations, weak projects.
+Style over substance.
+Hiring managers see through it.
+No proof of skills.
+
+**Instead**: Projects first, style second.
+Real work with real impact.
+Quality over quantity.
+Depth over breadth.
+
+### ❌ Resume Website
+
+**Why bad**: Boring, forgettable.
+Doesn't use the medium.
+No personality.
+Lists instead of stories.
+
+**Instead**: Show, don't tell.
+Visual case studies.
+Interactive elements.
+Personality throughout.
+
+## ⚠️ Sharp Edges
+
+| Issue | Severity | Solution |
+|-------|----------|----------|
+| Portfolio more complex than your actual work | medium | ## Right-Sizing Your Portfolio |
+| Portfolio looks great on desktop, broken on mobile | high | ## Mobile-First Portfolio |
+| Visitors don't know what to do next | medium | ## Portfolio CTAs |
+| Portfolio shows old or irrelevant work | medium | ## Portfolio Freshness |
+
+## Related Skills
+
+Works well with: `scroll-experience`, `3d-web-experience`, `landing-page-design`, `personal-branding`

package/skills/intercom-automation/SKILL.md

@@ -0,0 +1,248 @@
+---
+name: intercom-automation
+description: "Automate Intercom tasks via Rube MCP (Composio): conversations, contacts, companies, segments, admins. Always search tools first for current schemas."
+requires:
+  mcp: [rube]
+---
+
+# Intercom Automation via Rube MCP
+
+Automate Intercom operations through Composio's Intercom toolkit via Rube MCP.
+
+## Prerequisites
+
+- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
+- Active Intercom connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `intercom`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `intercom`
+3. If connection is not ACTIVE, follow the returned auth link to complete Intercom OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Manage Conversations
+
+**When to use**: User wants to create, list, search, or manage support conversations
+
+**Tool sequence**:
+1. `INTERCOM_LIST_ALL_ADMINS` - Get admin IDs for assignment [Prerequisite]
+2. `INTERCOM_LIST_CONVERSATIONS` - List all conversations [Optional]
+3. `INTERCOM_SEARCH_CONVERSATIONS` - Search with filters [Optional]
+4. `INTERCOM_GET_CONVERSATION` - Get conversation details [Optional]
+5. `INTERCOM_CREATE_CONVERSATION` - Create a new conversation [Optional]
+
+**Key parameters**:
+- `from`: Object with `type` ('user'/'lead') and `id` for conversation creator
+- `body`: Message body (HTML supported)
+- `id`: Conversation ID for retrieval
+- `query`: Search query object with `field`, `operator`, `value`
+
+**Pitfalls**:
+- CREATE_CONVERSATION requires a contact (user/lead) as the `from` field, not an admin
+- Conversation bodies support HTML; plain text is auto-wrapped in `<p>` tags
+- Search query uses structured filter objects, not free-text search
+- Conversation IDs are numeric strings
+
+### 2. Reply and Manage Conversation State
+
+**When to use**: User wants to reply to, close, reopen, or assign conversations
+
+**Tool sequence**:
+1. `INTERCOM_GET_CONVERSATION` - Get current state [Prerequisite]
+2. `INTERCOM_REPLY_TO_CONVERSATION` - Add a reply [Optional]
+3. `INTERCOM_ASSIGN_CONVERSATION` - Assign to admin/team [Optional]
+4. `INTERCOM_CLOSE_CONVERSATION` - Close conversation [Optional]
+5. `INTERCOM_REOPEN_CONVERSATION` - Reopen closed conversation [Optional]
+
+**Key parameters**:
+- `conversation_id` / `id`: Conversation ID
+- `body`: Reply message body (HTML supported)
+- `type`: Reply type ('admin' or 'user')
+- `admin_id`: Admin ID for replies from admin, assignment, and close/reopen
+- `assignee_id`: Admin or team ID for assignment
+- `message_type`: 'comment' (default) or 'note' (internal)
+
+**Pitfalls**:
+- `admin_id` is REQUIRED for admin replies, close, reopen, and assignment operations
+- Always fetch admin IDs first with LIST_ALL_ADMINS or IDENTIFY_AN_ADMIN
+- Duplicate sends can occur on retry; implement idempotency checks
+- Internal notes use `message_type: 'note'`; visible only to workspace members
+- Closing requires an admin_id and optional body message
+
+### 3. Manage Contacts
+
+**When to use**: User wants to search, view, or manage contacts (users and leads)
+
+**Tool sequence**:
+1. `INTERCOM_SEARCH_CONTACTS` - Search contacts with filters [Required]
+2. `INTERCOM_GET_A_CONTACT` - Get specific contact [Optional]
+3. `INTERCOM_SHOW_CONTACT_BY_EXTERNAL_ID` - Look up by external ID [Optional]
+4. `INTERCOM_LIST_CONTACTS` - List all contacts [Optional]
+5. `INTERCOM_LIST_TAGS_ATTACHED_TO_A_CONTACT` - Get contact tags [Optional]
+6. `INTERCOM_LIST_ATTACHED_SEGMENTS_FOR_CONTACT` - Get contact segments [Optional]
+7. `INTERCOM_DETACH_A_CONTACT` - Remove contact from company [Optional]
+
+**Key parameters**:
+- `contact_id`: Contact ID for retrieval
+- `external_id`: External system ID for lookup
+- `query`: Search filter object with `field`, `operator`, `value`
+- `pagination`: Object with `per_page` and `starting_after` cursor
+
+**Pitfalls**:
+- SEARCH_CONTACTS uses structured query filters, not free-text; format: `{field, operator, value}`
+- Supported operators: `=`, `!=`, `>`, `<`, `~` (contains), `!~` (not contains), `IN`, `NIN`
+- Contact types are 'user' (identified) or 'lead' (anonymous)
+- LIST_CONTACTS returns paginated results; use `starting_after` cursor for pagination
+- External IDs are case-sensitive
+
+### 4. Manage Admins and Teams
+
+**When to use**: User wants to list workspace admins or identify specific admins
+
+**Tool sequence**:
+1. `INTERCOM_LIST_ALL_ADMINS` - List all admins and teams [Required]
+2. `INTERCOM_IDENTIFY_AN_ADMIN` - Get specific admin details [Optional]
+
+**Key parameters**:
+- `admin_id`: Admin ID for identification
+
+**Pitfalls**:
+- LIST_ALL_ADMINS returns both admins and teams
+- Admin IDs are required for conversation replies, assignment, close, and reopen
+- Teams appear in the admins list with `type: 'team'`
+
+### 5. View Segments and Counts
+
+**When to use**: User wants to view segments or get aggregate counts
+
+**Tool sequence**:
+1. `INTERCOM_LIST_SEGMENTS` - List all segments [Optional]
+2. `INTERCOM_LIST_ATTACHED_SEGMENTS_FOR_CONTACT` - Segments for a contact [Optional]
+3. `INTERCOM_LIST_ATTACHED_SEGMENTS_FOR_COMPANIES` - Segments for a company [Optional]
+4. `INTERCOM_GET_COUNTS` - Get aggregate counts [Optional]
+
+**Key parameters**:
+- `contact_id`: Contact ID for segment lookup
+- `company_id`: Company ID for segment lookup
+- `type`: Count type ('conversation', 'company', 'user', 'tag', 'segment')
+- `count`: Sub-count type
+
+**Pitfalls**:
+- GET_COUNTS returns approximate counts, not exact numbers
+- Segment membership is computed; changes may not reflect immediately
+
+### 6. Manage Companies
+
+**When to use**: User wants to list companies or manage company-contact relationships
+
+**Tool sequence**:
+1. `INTERCOM_LIST_ALL_COMPANIES` - List all companies [Required]
+2. `INTERCOM_LIST_ATTACHED_SEGMENTS_FOR_COMPANIES` - Get company segments [Optional]
+3. `INTERCOM_DETACH_A_CONTACT` - Remove contact from company [Optional]
+
+**Key parameters**:
+- `company_id`: Company ID
+- `contact_id`: Contact ID for detachment
+- `page`: Page number for pagination
+- `per_page`: Results per page
+
+**Pitfalls**:
+- Company-contact relationships are managed through contact endpoints
+- DETACH_A_CONTACT removes the contact-company association, not the contact itself
+
+## Common Patterns
+
+### Search Query Filters
+
+**Single filter**:
+```json
+{
+  "field": "email",
+  "operator": "=",
+  "value": "user@example.com"
+}
+```
+
+**Multiple filters (AND)**:
+```json
+{
+  "operator": "AND",
+  "value": [
+    {"field": "role", "operator": "=", "value": "user"},
+    {"field": "created_at", "operator": ">", "value": 1672531200}
+  ]
+}
+```
+
+**Supported fields for contacts**: email, name, role, created_at, updated_at, signed_up_at, last_seen_at, external_id
+
+**Supported fields for conversations**: created_at, updated_at, source.type, state, open, read
+
+### Pagination
+
+- Most list endpoints use cursor-based pagination
+- Check response for `pages.next` with `starting_after` cursor
+- Pass cursor in `pagination.starting_after` for next page
+- Continue until `pages.next` is null
+
+### Admin ID Resolution
+
+```
+1. Call INTERCOM_LIST_ALL_ADMINS to get all admins
+2. Find the desired admin by name or email
+3. Use admin.id for replies, assignments, and state changes
+```
+
+## Known Pitfalls
+
+**Admin ID Requirement**:
+- Admin ID is required for: reply (as admin), assign, close, reopen
+- Always resolve admin IDs first with LIST_ALL_ADMINS
+
+**HTML Content**:
+- Conversation bodies are HTML
+- Plain text is auto-wrapped in paragraph tags
+- Sanitize HTML input to prevent rendering issues
+
+**Idempotency**:
+- Replies and conversation creation are not idempotent
+- Duplicate sends can occur on retry or timeout
+- Track message IDs to prevent duplicates
+
+**Rate Limits**:
+- Default: ~1000 requests per minute (varies by plan)
+- 429 responses include rate limit headers
+- Implement exponential backoff for retries
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| List conversations | INTERCOM_LIST_CONVERSATIONS | (pagination) |
+| Search conversations | INTERCOM_SEARCH_CONVERSATIONS | query |
+| Get conversation | INTERCOM_GET_CONVERSATION | id |
+| Create conversation | INTERCOM_CREATE_CONVERSATION | from, body |
+| Reply to conversation | INTERCOM_REPLY_TO_CONVERSATION | conversation_id, body, admin_id |
+| Assign conversation | INTERCOM_ASSIGN_CONVERSATION | conversation_id, admin_id, assignee_id |
+| Close conversation | INTERCOM_CLOSE_CONVERSATION | id, admin_id |
+| Reopen conversation | INTERCOM_REOPEN_CONVERSATION | id, admin_id |
+| Search contacts | INTERCOM_SEARCH_CONTACTS | query |
+| Get contact | INTERCOM_GET_A_CONTACT | contact_id |
+| Contact by external ID | INTERCOM_SHOW_CONTACT_BY_EXTERNAL_ID | external_id |
+| List contacts | INTERCOM_LIST_CONTACTS | (pagination) |
+| Contact tags | INTERCOM_LIST_TAGS_ATTACHED_TO_A_CONTACT | contact_id |
+| Contact segments | INTERCOM_LIST_ATTACHED_SEGMENTS_FOR_CONTACT | contact_id |
+| Detach contact | INTERCOM_DETACH_A_CONTACT | contact_id, company_id |
+| List admins | INTERCOM_LIST_ALL_ADMINS | (none) |
+| Identify admin | INTERCOM_IDENTIFY_AN_ADMIN | admin_id |
+| List segments | INTERCOM_LIST_SEGMENTS | (none) |
+| Company segments | INTERCOM_LIST_ATTACHED_SEGMENTS_FOR_COMPANIES | company_id |
+| Get counts | INTERCOM_GET_COUNTS | type, count |
+| List companies | INTERCOM_LIST_ALL_COMPANIES | page, per_page |

package/skills/internal-comms-anthropic/SKILL.md

@@ -0,0 +1,32 @@
+---
+name: internal-comms
+description: A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).
+license: Complete terms in LICENSE.txt
+---
+
+## When to use this skill
+To write internal communications, use this skill for:
+- 3P updates (Progress, Plans, Problems)
+- Company newsletters
+- FAQ responses
+- Status reports
+- Leadership updates
+- Project updates
+- Incident reports
+
+## How to use this skill
+
+To write any internal communication:
+
+1. **Identify the communication type** from the request
+2. **Load the appropriate guideline file** from the `examples/` directory:
+    - `examples/3p-updates.md` - For Progress/Plans/Problems team updates
+    - `examples/company-newsletter.md` - For company-wide newsletters
+    - `examples/faq-answers.md` - For answering frequently asked questions
+    - `examples/general-comms.md` - For anything else that doesn't explicitly match one of the above
+3. **Follow the specific instructions** in that file for formatting, tone, and content gathering
+
+If the communication type doesn't match any existing guideline, ask for clarification or more context about the desired format.
+
+## Keywords
+3P updates, company newsletter, company comms, weekly update, faqs, common questions, updates, internal comms