Aspectrr/linkedin connect new

.agents/skills/triage-reviews/SKILL.md

@@ -0,0 +1,66 @@
+---
+name: triage-reviews
+description: Fetch PR review comments, verify each against real code/docs, fix valid issues, commit and push
+disable-model-invocation: true
+argument-hint: '[PR number]'
+---
+
+# Triage PR Review Comments
+
+Fetch all review comments on the current PR, verify each finding against real code, fix valid issues, and push.
+
+## Phase 1: Gather Comments
+
+1. Determine the PR number:
+   - Use `$ARGUMENTS` if provided
+   - Otherwise: `gh pr view --json number --jq .number`
+
+2. Fetch ALL comments (reviewers post in multiple places):
+   ```
+   gh api --paginate repos/{owner}/{repo}/pulls/{pr}/reviews
+   gh api --paginate repos/{owner}/{repo}/pulls/{pr}/comments
+   gh api --paginate repos/{owner}/{repo}/issues/{pr}/comments
+   ```
+
+3. Extract unique findings — deduplicate across Copilot, Greptile, and human reviewers. Group by file and line.
+
+## Phase 2: Verify Each Finding
+
+For EVERY finding, verify against real code before accepting or rejecting:
+
+1. **Read the actual code** at the referenced file:line
+2. **Check if the issue still exists** — it may already be fixed in a later commit
+3. **Verify correctness** using:
+   - Code analysis (read surrounding context, trace call paths)
+   - Run `btca resources` to see what's available, then `btca ask -r <resource> -q "..."` for library/framework questions
+   - Web search for API behavior, language semantics, or CVEs
+4. **Classify** each finding:
+   - **Valid** — real bug, real gap, or real improvement needed
+   - **False positive** — reviewer misread the code, outdated reference, or style preference
+
+## Phase 3: Fix & Ship
+
+1. Fix all **Valid** findings
+2. Run the project's lint/test commands (check CLAUDE.md for exact commands)
+   - If lint/tests fail, fix the failures before committing
+   - If a failure cannot be fixed automatically, skip that fix and report it as **Valid (unfixed)** in the Phase 4 table
+3. `git add` only changed files, `git commit` with message:
+   ```
+   fix: Address PR review feedback
+
+   - <one-line summary per fix>
+   ```
+4. Push: `gt submit` (or `git push` if not using Graphite)
+
+## Phase 4: Report
+
+Present a final summary table of ALL findings with verdicts:
+
+| # | Source | File:Line | Finding | Verdict | Reason |
+|---|--------|-----------|---------|---------|--------|
+
+## Notes
+
+- Never dismiss a finding without reading the actual code first
+- If unsure, err toward "Valid" — it's cheaper to fix than to miss a bug
+- For library/API questions, always use btca or web search — don't guess

.coveragerc

@@ -0,0 +1,8 @@
+[run]
+source = linkedin_mcp_server
+branch = true
+omit = linkedin_mcp_server/__main__.py
+
+[report]
+fail_under = 45
+show_missing = true

.dockerignore

@@ -0,0 +1,164 @@
+# Based on .gitignore with Docker-specific additions
+
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pipenv
+#Pipfile.lock
+
+# poetry
+#poetry.lock
+
+# pdm
+.pdm.toml
+.pdm-python
+.pdm-build/
+
+# PEP 582
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Cursor
+.cursorignore
+.cursorindexingignore
+.cursor
+
+# Docker-specific exclusions
+.git
+.github
+README.md
+.DS_Store
+
+# DXT Extension
+*.dxt
+assets/*
+
+# other dev files
+.vscode
+.claude
+.github
+.docker

.env.example

@@ -0,0 +1,38 @@
+# LinkedIn MCP Server Environment Variables
+# Copy this file to .env and fill in your values
+
+# Persistent browser profile directory (default: ~/.linkedin-mcp/profile)
+# Run with --login to create a profile via browser login
+USER_DATA_DIR=~/.linkedin-mcp/profile
+
+# Browser mode (default: true)
+# true = headless, false = visible window
+HEADLESS=true
+
+# Logging level (default: WARNING)
+# Options: DEBUG, INFO, WARNING, ERROR
+LOG_LEVEL=WARNING
+
+# Transport mode (leave empty for interactive prompt, defaults to stdio in non-interactive)
+# Options: stdio, streamable-http
+TRANSPORT=
+
+# Browser timeout in milliseconds (default: 5000)
+TIMEOUT=5000
+
+# Custom browser user agent (optional)
+USER_AGENT=
+
+# HTTP server settings (for streamable-http transport)
+HOST=127.0.0.1
+PORT=8000
+HTTP_PATH=/mcp
+
+# Debugging options
+# Slow down browser actions by this many milliseconds (default: 0)
+SLOW_MO=0
+# Browser viewport size as WIDTHxHEIGHT (default: 1280x720)
+VIEWPORT=1280x720
+# Custom Chrome/Chromium executable path (optional)
+# Use this if Chrome is installed in a non-standard location
+CHROME_PATH=

.gemini/settings.json

@@ -0,0 +1,7 @@
+{
+  "mcpServers": {
+    "linkedin-mcp-server": {
+        "httpUrl": "http://127.0.0.1:8000/mcp"
+    }
+  }
+}

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,35 @@
+name: Bug Report
+description: Something is broken or not working as expected
+title: "[BUG] "
+labels: ["bug"]
+body:
+  - type: input
+    id: setup
+    attributes:
+      label: Setup
+      description: How you run the server, which MCP client, and what OS.
+      placeholder: "e.g. uvx on macOS, Claude Desktop"
+    validations:
+      required: true
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: What Happened
+      description: What broke and what you expected instead.
+    validations:
+      required: true
+  - type: textarea
+    id: steps-to-reproduce
+    attributes:
+      label: Steps to Reproduce
+      description: Minimal steps to trigger the bug. Include the tool name and arguments if relevant.
+    validations:
+      required: true
+  - type: textarea
+    id: logs
+    attributes:
+      label: Logs
+      description: Paste relevant log output. Remove credentials.
+      render: shell
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,15 @@
+# .github/ISSUE_TEMPLATE/config.yml
+blank_issues_enabled: false
+contact_links:
+  - name: 💬 General Questions & Discussion
+    url: https://github.com/stickerdaniel/linkedin-mcp-server/discussions/categories/general-questions-discussion
+    about: Ask questions about setup, usage, or get help from the community
+  - name: 📚 Share Your Setup & Get Help with Configuration
+    url: https://github.com/stickerdaniel/linkedin-mcp-server/discussions/categories/share-your-setup-get-help-with-configuration
+    about: Share how you set up the MCP in your favorite client or get help with configuration
+  - name: 💡 Ideas & Suggestions
+    url: https://github.com/stickerdaniel/linkedin-mcp-server/discussions/categories/ideas-suggestions
+    about: Share ideas for new features or improvements (before creating a formal feature request)
+  - name: 🙌 Show and Tell
+    url: https://github.com/stickerdaniel/linkedin-mcp-server/discussions/categories/show-and-tell
+    about: I would love to see how you're using the LinkedIn MCP server and what you're building with it!

.github/ISSUE_TEMPLATE/documentation_issue.yml

@@ -0,0 +1,27 @@
+name: Documentation Issue
+description: Report incorrect, missing, or confusing documentation
+title: "[DOCS] "
+labels: ["documentation"]
+body:
+  - type: input
+    id: location
+    attributes:
+      label: Location
+      description: File path, section name, or URL.
+      placeholder: "e.g. README.md, Docker setup section"
+    validations:
+      required: true
+  - type: textarea
+    id: problem
+    attributes:
+      label: Problem
+      description: What's wrong or confusing.
+    validations:
+      required: true
+  - type: textarea
+    id: suggested-fix
+    attributes:
+      label: Suggested Fix
+      description: What it should say instead. Leave blank if unsure.
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,26 @@
+name: Feature Request
+description: Suggest an improvement or new capability
+title: "[FEATURE] "
+labels: ["enhancement"]
+body:
+  - type: textarea
+    id: feature-description
+    attributes:
+      label: Feature Description
+      description: What you want to happen.
+    validations:
+      required: true
+  - type: textarea
+    id: use-case
+    attributes:
+      label: Use Case
+      description: Why this is useful.
+    validations:
+      required: true
+  - type: textarea
+    id: suggested-approach
+    attributes:
+      label: Suggested Approach
+      description: How you'd implement it. Leave blank if unsure.
+    validations:
+      required: false