instantly-reference-architecture
Implement Instantly.ai reference architecture with best-practice project layout. Use when designing new Instantly integrations, planning multi-campaign systems, or building an outreach automation platform. Trigger with phrases like "instantly architecture", "instantly project structure", "instantly reference design", "instantly system design", "instantly integration layout".
80
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/instantly-pack/skills/instantly-reference-architecture/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description with excellent trigger term coverage and clear 'when to use' guidance. Its main weakness is that the 'what' portion is somewhat abstract—it mentions implementing a 'reference architecture' and 'best-practice project layout' without specifying what concrete artifacts or actions are produced (e.g., folder structures, config files, API integration modules). The distinctiveness is excellent due to the narrow Instantly.ai focus.
Suggestions
Add specific concrete actions/outputs like 'generates folder structure, API client modules, campaign configuration templates, webhook handlers' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (Instantly.ai reference architecture) and mentions some actions like 'designing new Instantly integrations, planning multi-campaign systems, building an outreach automation platform,' but doesn't list concrete specific actions like creating specific files, configuring specific components, or generating particular outputs. | 2 / 3 |
Completeness | Clearly answers both 'what' (implement Instantly.ai reference architecture with best-practice project layout) and 'when' (designing new Instantly integrations, planning multi-campaign systems, building outreach automation platforms), with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Includes explicit trigger phrases like 'instantly architecture', 'instantly project structure', 'instantly reference design', 'instantly system design', 'instantly integration layout' which are natural terms a user would say. Also includes contextual terms like 'multi-campaign systems' and 'outreach automation platform'. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Instantly.ai platform architecture specifically. The trigger terms are all prefixed with 'instantly' making it highly unlikely to conflict with other skills. The domain is narrow and well-defined. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid reference architecture skill with strong actionability through executable TypeScript code and a clear project layout. Its main weaknesses are verbosity (the full API client and template code could be more concise or split into referenced files) and missing validation checkpoints in the workflows. The data flow diagram and error table are good additions, but the skill would benefit from explicit verification steps and better content splitting.
Suggestions
Add explicit validation checkpoints to workflows—e.g., verify API key scopes before proceeding, validate lead import results before campaign activation, and include retry/fix loops for common failures.
Move the full API client implementation and campaign templates into separate referenced files (e.g., CLIENT.md, TEMPLATES.md) and keep only key patterns and a brief example in the main skill.
Add a quick-start section at the top showing the minimal steps to get a working integration (init project, configure env, test API connection) before diving into the full architecture.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes more detail than necessary in some areas—the full API client implementation is quite long and could be summarized with key patterns rather than exhaustive method listings. The campaign template system section adds bulk without proportional value. However, it doesn't explain basic concepts Claude already knows. | 2 / 3 |
Actionability | The skill provides fully executable TypeScript code for the API client, campaign templates, and project layout. The code is copy-paste ready with concrete implementations including retry logic, authentication, and typed method signatures. | 3 / 3 |
Workflow Clarity | The data flow summary provides a clear sequence, and the error handling table is useful. However, there are no explicit validation checkpoints—for example, no step to verify API key scopes before proceeding, no validation after lead import, and no feedback loops for error recovery in the campaign launch workflow. | 2 / 3 |
Progressive Disclosure | References to related skills ('instantly-performance-tuning', 'instantly-webhooks-events', 'instantly-multi-env-setup') and external docs are present, but the main file is quite long with inline code that could be split into referenced files. The project layout and full client implementation could live in separate reference documents. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
70e9fa4
- Reviewed
Table of Contents
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.