Feature Proposal: Stitch MCP Integration for Google Skills
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- powershell
- Domain
- ai-infra-agents
Research direction
Review the proposed implementation in the fork’s stitch/SKILL.md and stitch/scripts/generate-stitch.ps1, then compare it with the repository’s existing skill format and contribution guidance. The issue describes validation already performed but does not explain the expected Stitch MCP behavior or acceptance criteria; clarify those with maintainers before making changes.
Written by the indexing model from the issue text.
Description
Technical Overview:
Feature: Stitch MCP Integration.
Purpose: To enable integration between Google Skills and Stitch MCP.
Implementation: Available in my fork and feature branch.
Modified files: stitch/SKILL.md, stitch/scripts/generate-stitch.ps1
Testing:
Validated SKILL.md contains correct YAML frontmatter (name, description) matching the repository's skill format.
Verified generate-stitch.ps1 is syntactically valid PowerShell with proper parameter handling.
Ran git status to confirm no unintended file changes — only the new stitch/ directory was added.
Searched the full repository for existing "stitch" references — no duplicates or conflicts found.
Pushed to GitHub and confirmed "Able to merge" with zero conflicts against upstream google/skills main.
Branch and Implementation:
Repository: https://github.com/hiteshchoudhary738-alt/skills
Branch: stitch-mcp-feature
Code: https://github.com/hiteshchoudhary738-alt/skills/tree/stitch-mcp-feature
I would appreciate feedback on the implementation and guidance on the appropriate contribution process. I'm happy to make any required modifications based on your feedback.
Thank you for your time!
- Dominant language
- Python
- Stars
- 23.1k
- Forks
- 1.9k
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from google/skills
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Similar issues
-
namespace
Difficulty 1/5 Under an hour Newbie friendliness 68/100
EclipseFdn/open-vsx.org#15604 ·
Maintainers usually reply within 1 day
-
app: scripts severity: low status: backlog type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
netbox-community/netbox-scripts#164 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 5 days
-
Public function to read participants.tsvPossibly taken @bruAristimunha claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
huggingface/tau#799 ·
Maintainers usually reply within 2 days