agent-slack vs linear-claude-skill — Trust Score Comparison
Side-by-side trust comparison of agent-slack and linear-claude-skill. Scores based on security, compliance, maintenance, popularity, and ecosystem signals.
Detailed Metric Comparison
| Metric | agent-slack | linear-claude-skill |
|---|---|---|
| Trust Score | 84.4/100 | 76.2/100 |
| Grade | A | B |
| Stars | 311 | 42 |
| Category | communication | coding |
| Security | 0 | 0 |
| Compliance | 100 | 100 |
| Maintenance | 1 | 1 |
| Documentation | 1 | 1 |
| EU AI Act Risk | minimal | minimal |
| Verified | Yes | Yes |
Verdict
agent-slack leads with a trust score of 84.4/100 compared to linear-claude-skill's 76.2/100 (a 8.2-point difference). agent-slack scores higher on maintenance (1 vs 1). Both agents should be evaluated based on your specific requirements.
Detailed Analysis
Security
agent-slack leads on security with a score of 0/100 compared to linear-claude-skill's 0/100. This score reflects dependency vulnerability analysis, known CVE exposure, and security best practices. A higher security score means fewer known vulnerabilities and better security hygiene in the codebase.
Maintenance & Activity
agent-slack demonstrates stronger maintenance activity (1/100 vs 1/100). This metric captures commit frequency, issue response times, and release cadence. Actively maintained tools receive faster security patches and are less likely to accumulate technical debt.
Documentation
agent-slack has better documentation (1/100 vs 1/100). Good documentation reduces onboarding time and helps teams adopt the tool safely. This score evaluates README completeness, API documentation, code examples, and tutorial availability.
Community & Adoption
agent-slack has 311 GitHub stars while linear-claude-skill has 42. agent-slack has significantly broader community adoption, which typically means more Stack Overflow answers, more third-party tutorials, and faster ecosystem development.
When to Choose Each Tool
Choose agent-slack if you need:
- Higher overall trust score — more reliable for production use
- More actively maintained with faster release cadence
- Larger community (311 vs 42 stars)
Choose linear-claude-skill if you need:
- Consider if it better fits your specific use case
Switching from agent-slack to linear-claude-skill (or vice versa)
When migrating between agent-slack and linear-claude-skill, consider these factors:
- API Compatibility: agent-slack (communication) and linear-claude-skill (coding) serve different categories, so migration may require significant refactoring.
- Security Review: Run a security audit after migration. Check the agent-slack safety report and linear-claude-skill safety report for known issues.
- Testing: Ensure your test suite covers all integration points before switching in production.
- Community Support: agent-slack has 311 stars and linear-claude-skill has 42. Larger communities typically mean better Stack Overflow answers and migration guides.
Related Pages
Frequently Asked Questions
Related Comparisons
Last updated: 2026-04-05 | Data refreshed weekly
Disclaimer: Nerq trust scores are automated assessments based on publicly available signals. They are not endorsements or guarantees. Always conduct your own due diligence.