Agent Skills for Context Engineering
A comprehensive collection of Agent Skills for context engineering, multi-agent architectures, and production agent systems. Use when building, optimizing, or debugging agent systems that require effective context management.
Is Agent Skills for Context Engineering safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare Agent Skills for Context Engineering
How does it stack up against its Agent Skills neighbours?
Pick any agent to compare →In detail: Agent Skills for Context Engineering scores 50.7/100 (Grade C), ranked #229 of 351 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.6/10; 69% of recent commits are signed; last pushed 2026-09-11. Every point is earned from checkable signals — never paid placement. How scoring works →
How Agent Skills for Context Engineering compares in Agent Skills
- #227 Claude Code Skills 50.8 +0.1
- #228 Wondelai Skills 50.8 +0.1
- #229 Agent Skills for Context Engineering 50.7 this agent
- #230 Claude OSINT 50.6 −0.1
- #231 Itr Wala 50.6 −0.1
Bars show each HVTrust score; the tick marks Agent Skills for Context Engineering’s 50.7.
Where the 50.7 comes from
HVTrust dimensions vs the Agent Skills average
50.7 / 100 · 100.0% confidenceAgent Skills for Context Engineering Agent Skills average (351 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
63.2 / 100Supply Chain Trust
Common questions about Agent Skills for Context Engineering
Does Agent Skills for Context Engineering publish package provenance?
Does Agent Skills for Context Engineering have an OpenSSF Scorecard?
Is Agent Skills for Context Engineering actively maintained?
What license does Agent Skills for Context Engineering use?
Are Agent Skills for Context Engineering's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Agent Skills for Context Engineering's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Maintain Agent Skills for Context Engineering?
For maintainers
HVTrust scores Agent Skills for Context Engineering from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/agent-skills-for-context-engineering)
<a href="https://hvtracker.net/agents/agent-skills-for-context-engineering"><img src="https://hvtracker.net/badge/agent-skills-for-context-engineering.svg" alt="HVTrust"></a>
Other agents in Agent Skills
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON