- Change invocation to /sponsor owner/repo
- Rename 'Sponsor These' to 'Ways to Give Back'
- Soften language: never shame unfunded projects
- Add rule: always be encouraging, never shaming
- Regenerate READMEs
Major upgrade:
- deps.dev GetDependencies: full tree in one call (direct + transitive)
- deps.dev GetVersion: cross-ecosystem package→repo mapping (7 ecosystems)
- deps.dev GetProject: OSSF Scorecard health data per project
- Direct vs transitive column (✅ vs ⛓️)
- Health column from Scorecard Maintained check
- Actionable minimum: '💡 Sponsoring just N people covers all funded deps'
- Graceful fallback to registry APIs if deps.dev unavailable
Inspired by jshchnz/tribute, adds:
- Link verification: every funding URL is fetched before presenting
- Web search fallback: finds funding even without FUNDING.yml
- How Verified column: transparency about data source
- 5 ecosystems: npm, Python, Rust, Go, Ruby (was npm-only)
- Corporate-maintained package detection
- No Verified Funding Found section for unfunded deps
Teaches Copilot how to scan a repo's dependencies and find which ones
accept sponsorship via GitHub Sponsors, Open Collective, etc.
Workflow:
1. Fetch package.json from target repo
2. Resolve each dep to source GitHub repo via npm registry
3. Check npm funding field + .github/FUNDING.yml
4. Group by maintainer, present report with sponsor links
Tested against expressjs/express: found 9/28 deps sponsorable (32%)
across 3 funding destinations.
Adds a Copilot CLI skill that teaches absolute beginners how to use
GitHub Copilot CLI through guided, interactive lessons right in the
terminal. Features:
- Dual-track learning: Developer (8 lessons) and Non-Developer (7 lessons)
- Interactive exercises using ask_user
- SQL-based progress tracking
- On-demand Q&A with live doc fetching
- Beginner-friendly with CLI glossary and fallback handling
Source repo: https://github.com/DUBSOpenHub/copilot-cli-quickstart
- Move all reference docs from cli/, mcp/, framework/ subfolders into references/ per agentskills.io spec
- Update all cross-references in SKILL.md and reference files
- Version-gate MCP tools: 9 tools in 13.1+, docs tools (list_docs/search_docs/get_doc) in 13.2+
- Simplify integrations-catalog.md to lead with MCP tool discovery (list_integrations/get_integration_docs)
- Remove .vscode/mcp.json (test artifact from aspire mcp init)
The skill is about how to research docs, not a DevUI tutorial. Replace the 10-step DevUI workflow checklist with a research strategy table showing which tool to use for each type of DevUI information.
Tested all 5 Context7 Aspire library IDs with identical queries to compare content freshness and quality. Key findings: - /microsoft/aspire.dev (repo) has the best coverage including Aspire 13+ APIs - /websites/learn_microsoft-en-us-dotnet-aspire (website) is a good alternative - /dotnet/docs-aspire is the LEGACY repo being superseded, missing newer APIs - Added quality ranking table, usage guidance per source, and expanded query examples
Rewrite Section 1 (Researching Aspire Documentation) to use Context7 as the primary method for querying docs and code examples. Context7 provides a single-step lookup with code snippets and source links, vs the two-step GitHub search + file read approach. The GitHub method is preserved as a fallback.
