Syrs Clarity
Install when you want clearer agent outputs or structured clarity checks from the ai.lge.com skill pack, with public listing metadata only until SKILL.md is published.
Overview
syrs-clarity is an agent skill listed from ai.lge.com that Prism indexes from skills.sh while full SKILL.md triggers and procedures are not yet available in the public ingest.
Install
npx skills add https://github.com/ai.lge.com --skill syrs-clarityWhat is this skill?
- Listed on skills.sh under source ai.lge.com with well-known source type
- Public ingest shows 1 install and rank 2654 at time of catalog snapshot
- Skill slug syrs-clarity—detail page should be updated when full SKILL.md lands
- No procedural body in ingest—treat capabilities as unspecified until upstream docs ship
- Compatible with generic agent skill loaders (Claude Code, Cursor, Codex) like other skills.sh entries
- 1 install in public skills.sh snapshot
- rank 2654 in ingest metadata
Adoption & trust: 1 installs on skills.sh.
What problem does it solve?
You found syrs-clarity on a journey hub but the ingest has no SKILL.md body, so you cannot tell what it does or when to invoke it.
Who is it for?
Builders auditing ai.lge.com or skills.sh listings who want a catalog pointer before cloning the full skill repo.
Skip if: Teams that need verified procedures, security notes, or invokeWhen gates today—wait for published SKILL.md or skip until docs exist.
When should I use this skill?
Invoke only after upstream SKILL.md publishes explicit triggers; current ingest has no invokeWhen text.
What do I get? / Deliverables
After upstream SKILL.md is published, you can re-run tagging and invoke the skill with explicit triggers, deliverables, and journey placement instead of guessing from the name alone.
- agent skill package reference (capabilities TBD until docs ship)
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Listed under Build because clarity-oriented agent skills are typically wired into coding-agent workflows during implementation, even though naming suggests broader use. agent-tooling is the default shelf for installable agent capabilities without a published procedural SKILL.md in this ingest.
Where it fits
Compare syrs-clarity against documented clarity skills before adding it to an agent stack.
Install from skills.sh routing once SKILL.md defines invokeWhen for coding sessions.
Re-evaluate the skill after upstream docs clarify whether it gates completion claims or output formatting.
How it compares
Directory listing stub, not a documented checker or workflow skill with an iron-law gate like verification-before-completion.
Common Questions / FAQ
Who is syrs-clarity for?
Solo and indie builders exploring ai.lge.com agent skills on Prism or skills.sh who want a bookmark until full documentation is available.
When should I use syrs-clarity?
Use after you pull the upstream package and read its SKILL.md—potentially during Build agent-tooling setup or Validate scoping once triggers are known; do not invoke blindly from the stub ingest alone.
Is syrs-clarity safe to install?
Review the Security Audits panel on this Prism page and inspect the upstream source on ai.lge.com before enabling it in agents with shell or network access.
SKILL.md
READMESKILL.md - Syrs Clarity
# syrs-clarity Installs: 1 Source: ai.lge.com { "url": "https://www.skills.sh/site/ai.lge.com/syrs-clarity", "name": "syrs-clarity", "rank": 2654, "slug": "syrs-clarity", "change": 0, "source": "ai.lge.com", "installs": 1, "skillsShId": "ai.lge.com/syrs-clarity", "sourceType": "well-known", "installsYesterday": 1 }