Install
$ agentstack add skill-anoopsg-agent-rules-create-client ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Client Creation Skill
This skill defines the process for creating a new low-level client in the infrastructure/_clients/ directory.
1. Overview
Clients are high-level wrappers around third-party plugins or system APIs (e.g., shared_preferences, dio, package_info). They encapsulate the configuration and complexity of these tools, providing a clean interface for the rest of the infrastructure layer.
2. Directory Structure
Clients are stored in lib/src/infrastructure/_clients/:
lib/src/infrastructure/_clients/
├── _clients.dart # Barrel file
├── my_plugin_client.dart # The client implementation
└── ...
3. Implementation Pattern
Follow these rules when creating a client:
- Naming: Use
PascalCase+Client(e.g.,LocationClient). - DI: Provide the client via a Riverpod provider with
keepAlive: true. - Encapsulation: Hide plugin-specific types behind your own methods where
possible.
- Error Handling: Use
try/catchblocks and log errors using
dart:developer.
3.1 Example Implementation
import 'dart:developer' as developer;
import 'package:riverpod_annotation/riverpod_annotation.dart';
import 'package:my_plugin/my_plugin.dart';
part 'my_plugin_client.g.dart';
@Riverpod(keepAlive: true)
MyPluginClient myPluginClient(Ref ref) => MyPluginClient();
class MyPluginClient {
final _plugin = MyPlugin();
Future doSomething() async {
try {
await _plugin.execute();
return true;
} on Object catch (e, st) {
developer.log(
'MyPluginClient.doSomething failed',
name: 'MyPluginClient',
error: e,
stackTrace: st,
);
return false;
}
}
}
4. Barrel File
Always export your new client in lib/src/infrastructure/_clients/_clients.dart:
export 'my_plugin_client.dart';
5. Usage in Repositories
Clients are injected into repositories via their constructors. Repositories then use the client's clean methods to perform data operations.
class MyRepository {
MyRepository({required MyPluginClient client}) : _client = client;
final MyPluginClient _client;
}
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: anoopsg
- Source: anoopsg/agent_rules
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.