Name: project-architecture
Rating: 80 (1 reviews)
Author: ringcentral

project-architecture

Use this skill to understand the RingCentral App Connect project structure, including the monorepo layout, core package APIs, handlers, models, and how components interact.

1.16x

Quality

—

Does it follow best practices?

Impact

100%

1.16x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

80%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a lean, actionable architecture reference with executable code and concrete file/command mappings, but it keeps everything inline with no progressive disclosure to separate files and presents development steps without sequencing or validation.

Suggestions

Split the API Routes and Environment Variables sections into referenced files (e.g. references/api-routes.md, references/env-vars.md) and link them from the body to improve progressive disclosure.

Reformat the Development Workflow into a numbered sequence with validation checkpoints (e.g. run tests before build, verify build artifact before deploy).

Add a brief 'Where to look next' navigation block pointing to the extracted reference files so Claude can drill down one level.

Dimension	Reasoning	Score
Conciseness	The body is dense reference material — a directory tree, tables mapping handlers/models/libraries to files, code blocks, route lists, and commands — with no padding explaining concepts Claude already knows; every token earns its place.	3 / 3
Actionability	It provides copy-paste-ready code (require('@app-connect/core'), createCoreApp(), connectorRegistry usage), concrete file paths in tables, and real npm commands (npm run server, ngrok, test, build, deploy).	3 / 3
Workflow Clarity	The 'Development Workflow' section is a flat menu of commands with no sequenced steps or validation checkpoints, and the rest is reference material rather than a guided multi-step process.	2 / 3
Progressive Disclosure	The file is well-sectioned but exceeds 50 lines with all route and environment-variable reference content kept inline and no external file references (no bundle files exist in references/, scripts/, or assets/).	2 / 3
	Total	10 / 12 Passed

Description

57%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific to a single project niche and clearly states what it covers, but its action is singular and it lacks an explicit situational trigger, leaving completeness and trigger quality mid-range.

Suggestions

Replace the single verb 'understand' with multiple concrete actions, e.g. 'Map, navigate, and explain the RingCentral App Connect monorepo...'.

Add an explicit 'Use when...' situational trigger, e.g. 'Use when working in the rc-unified-crm-extension repo or when asked how packages, handlers, or models interact.'

Include common user phrasings ('how is the codebase organized', 'where are the handlers/models') to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain plus several concrete topics ('monorepo layout, core package APIs, handlers, models, and how components interact'), but the only action verb is the singular 'understand', so it lists subjects rather than multiple distinct concrete actions.	2 / 3
Completeness	The 'what' is clear ('understand the RingCentral App Connect project structure, including...'), and 'Use this skill to' gives purpose, but the 'when' triggering situation is only implied rather than stated as an explicit 'Use when...' condition.	2 / 3
Trigger Term Quality	Relevant project-specific keywords like 'RingCentral App Connect', 'monorepo layout', 'handlers', and 'models' appear, but they lean technical and omit common situational phrasings a user would naturally say.	2 / 3
Distinctiveness Conflict Risk	It is tightly scoped to the named 'RingCentral App Connect' project with its monorepo and core package, making it unlikely to trigger for unrelated skills.	3 / 3
	Total	9 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: ringcentral/rc-unified-crm-extension
Commit: 25fc4c6

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.