Agent skill · Audited from source
competitive-analysis
skill · owl-listener/designer-skillsMIT licenceAudited 29 Oct 2026 · source 353bfcf4d7fc
Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit 353bfcf4d7fc and found no filesystem, network or shell access and no hard-coded secrets. What it does: Compare UX patterns, features, strengths, and gaps across rival products. Use when you need to know what others actually do. For deliberately adopting their conventions, use `jakobs-law` (interaction-design).
Cite
Cite this page
ModelsAtlas. “competitive-analysis (owl-listener/designer-skills)”. Retrieved 29 Oct 2026. https://modelsatlas.com/skills/owl-listener/competitive-analysis
2 skills are called “competitive-analysis”. You are viewing owl-listener/designer-skills.
- owl-listener/designer-skills★ 3.2k✓SAFE
- anthropics/financial-services-plugins★ 41k✓SAFE
Trust audit
Audit 0.4.1 · source read 29 Oct 2026
SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 13,985 of 14,816 audited skills.
What the source does
- FilesystemNone observedNo reads or writes in the source
- NetworkNone observedNo outbound calls in the source
- ShellNone observedNo commands run in the source
- DependenciesPinnedNothing floats
- SecretsNone foundNo keys in source
Five audit layers
| Layer | What we check | Result | Findings |
|---|---|---|---|
L0 Provenance | Repo owner, licence, archive status, activity | PASS | 0 |
L1 Static source | Secrets, path traversal, supply chain, hidden code | NA | 0 |
L2 Instructions | Prompt injection, authority framing, hidden directives | PASS | 0 |
L3 Inventory | The files and declarations match the source | PASS | 0 |
L4 Sandbox | Run in isolation and watch behaviour | SKIPPED why | 0 |
Gates applied: no behavioural pass.
Findings (0)
No findings at any severity. We re-audit when the source changes.
Audit 0.4.1 · source sha 353bfcf4d7fc · 29 Oct 2026Report an issue or request a re-scan
Provenance
Who published it, and what the verdict is pinned to
- Publisherowl-listener GitHub userOwner of the repository this skill is read from
- Source folderowl-listener/designer-skills/ux-strategy/skills/competitive-analysisThe exact folder we audited
- LicenceMITAs the repository states it
- Commit pinned for this verdict353bfcf4d7fcA new audit runs when the source changes
- Repository statusNot archivedLast push 53 days ago
- Sandboxed runNot runSkills are read, not executed; layer L4 is skipped
What it tells the agent
Full source on GitHub ↗Its description: Compare UX patterns, features, strengths, and gaps across rival products. Use when you need to know what others actually do. For deliberately adopting their conventions, use `jakobs-law` (interaction-design).
--- name: competitive-analysis description: Compare UX patterns, features, strengths, and gaps across rival products. Use when you need to know what others actually do. For deliberately adopting their conventions, use `jakobs-law` (interaction-design). --- # Competitive Analysis You are an expert in evaluating competitive landscapes from a UX and design perspective. ## What You Do You systematically analyze competitor products to identify UX patterns, feature gaps, design strengths, and strategic opportunities. ## Analysis Framework ### 1. Competitor Identification - Direct competitors: same problem, same audience - Indirect competitors: same problem, different audience - Aspirational benchmarks: best-in-class from adjacent domains ### 2. Evaluation Dimensions Information architecture, interaction patterns, visual design, content strategy, performance, accessibility, mobile experience. ### 3. Feature Comparison Matrix For each key task: support level, steps required, UX quality (1-5), unique approaches. ### 4. Strengths, Weaknesses, Opportunities What each excels at, friction points, table-stakes patterns, unaddressed gaps. ## Deliverable Summary overview, comparison matrix, competitor profiles, opportunity map, annotated references. ## Best Practices - Focus on UX quality, not just feature presence - Analyze full journeys, not isolated screens - Update regularly as competitors evolve - Include aspirational examples from outside the category
Excerpt, first 1,465 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.
Install
Pinned to the audited commit 353bfcf
git clone https://github.com/owl-listener/designer-skills git -C designer-skills checkout 353bfcf4d7fc
The author documents no install command, so this uses the repository directly. Our verdict covers commit 353bfcf4d7fc only.
Works in
The author has not said which agents this skill supports, and we have not tested it in any.
Audit history
Every audit, every source change
- ✓SAFE B 89 / 100
first audit · source
353bfcf4d7fc
README badge
For maintainers · shows the latest audit
[](https://modelsatlas.com/skills/owl-listener/competitive-analysis/)
The badge shows our verdict and grade for this skill, and links back to this page. It changes when the audit does.
Similar skills
All design & front-end skills →owl-listener/designer-skills
Specify one component — props, states, variants, accessibility, and usage rules. Use when defining a library component. For the reusable doc scaffold use `documentation-template`; for a problem-solution pattern use…
owl-listener/designer-skills
Build a product colour system — tonal scales, semantic roles, and contrast compliance. Use when defining or rebuilding colour from scratch. For dark-mode adaptation use `dark-mode-design`; for chart palettes use…
owl-listener/designer-skills
Design first-click and click tests for findability and navigation. Use when testing whether people can locate something. For full task-based observation, use `test-scenario`.
owl-listener/designer-skills
Craft a portfolio case study with narrative arc, process evidence, and outcomes. Use when telling a project's story to an external audience. For an internal stakeholder deck, use `presentation-deck`.
owl-listener/designer-skills
Analyse open or closed card sort results into a proposed grouping and label set. Use after running a sort study. For turning that evidence into a full structure, use `information-architecture` (ux-strategy).
owl-listener/designer-skills
Read financials, map competitive landscapes, and argue design decisions in the language of value. Use when defending design to commercial stakeholders. For the live negotiation itself, use `design-negotiation`…
Add this badge to your README
[](https://modelsatlas.com/skills/owl-listener/competitive-analysis/)
<a href="https://modelsatlas.com/skills/owl-listener/competitive-analysis/"><img src="https://modelsatlas.com/skills/owl-listener/competitive-analysis/badge.svg" alt="ModelsAtlas: SAFE B"></a>
Questions about competitive-analysis
What does the competitive-analysis skill do?
Is competitive-analysis safe to install?
What can competitive-analysis access on my machine?
How current is this page?
Sources
- github.com/owl-listener/designer-skills/tree/main/ux-strategy/sk — the audited source at commit 353bfcf4d7fc and every finding aboveObserved · 29 Oct 2026
Spotted something wrong? Report a correction · Methodology
Keep going in your AI
Opens with this page as the source. We add nothing else to the prompt.
- What does the competitive-analysis skill do?
- Is competitive-analysis safe to install?
- What can competitive-analysis access on my machine?