SkillWallet*

SkillWallet* is a permissioned skill runtime and marketplace for autonomous wallet automation.

The project explores a safer approach to AI-powered wallets by separating reasoning from execution.

Today, AI models are increasingly capable of understanding context, analyzing information, and making decisions. However, blockchain execution is irreversible, and giving an AI unrestricted control over a wallet creates significant trust and security concerns.

SkillWallet* introduces a different model.

Instead of giving AI direct wallet access, users install bounded wallet skills. Each skill defines its own trigger, configuration, execution policy, and permission scope. Users explicitly review and approve what a skill is allowed to do before it becomes active.

Examples of skill permissions include:

• Which contracts may be called

• Which assets may be used

• Maximum spending limits

• Execution frequency

• Trigger conditions

Once installed, a skill can operate autonomously within the boundaries approved by the user.

The system consists of several layers.

The user-facing wallet experience is powered by MetaMask Smart Accounts and MetaMask Snap integration. Users install skills, review permission scopes, and approve delegated execution capabilities through the wallet experience.

The SkillWallet runtime acts as the orchestration layer. It manages installed skills, monitors triggers, loads configuration, validates permissions, records execution history, and determines whether a skill should execute.

Triggers can be time-based (cron schedules) or event-based (onchain activity).

When a trigger fires, the runtime loads the corresponding skill installation and evaluates its execution flow.

Some skills are fully deterministic and execute based on predefined rules.

Other skills are AI-assisted.

For AI-assisted skills, the runtime can first retrieve paid external data through x402. This allows skills to consume premium information sources rather than relying solely on public blockchain data.

For example, an AI-Powered DCA skill can retrieve market analysis data through x402 before making a decision.

The retrieved context is then provided to Venice AI together with:

• Skill description

• User configuration

• Execution objectives

• Permission constraints

• Runtime context

Venice AI functions strictly as a reasoning engine.

It does not receive private keys.
It does not sign transactions.
It does not execute wallet actions.

Instead, Venice returns a structured response that indicates whether execution should proceed, along with supporting reasoning.

Examples include:

• Execute

• Skip

• Confidence level

• Explanation

If the response indicates that execution should proceed, the backend validates the result against the skill's approved permission scope.

The transaction is then constructed by the SkillWallet execution engine and submitted through 1Shot.

1Shot serves as the delegated execution layer that enables approved wallet actions to be executed without requiring the user to manually sign every interaction.

This architecture allows users to benefit from automation while maintaining control over what actions can occur.

The project demonstrates a complete workflow:

1. Discover a skill in the marketplace

2. Install the skill

3. Review and approve permission scope

4. Create delegated permissions through MetaMask Smart Accounts

5. Activate the skill

6. Trigger execution through schedule or event

7. Optionally retrieve premium data through x402

8. Optionally perform reasoning through Venice AI

9. Build approved transaction payloads

10. Execute through 1Shot delegated execution

11. Record execution history and reasoning

The core design principle behind SkillWallet* is:

AI reasons.
Backend executes.
User controls permissions.

By separating reasoning from execution and enforcing user-approved permission boundaries, SkillWallet* explores a safer and more transparent model for autonomous wallet automation.

Built for the MetaMask Smart Accounts Kit × 1Shot API × Venice AI Dev Cook Off.

During the hackathon, I built the SkillWallet* MVP as a working skill runtime and marketplace backend for delegated wallet automation.

Completed progress includes:

- Skill catalog API for discovering available wallet skills

- Skill installation flow with prepare / confirm delegation endpoints

- MetaMask wallet integration for the user-facing demo flow, including Snap-related wallet UX where relevant

- Support for skill parameters, permission scopes, and human-readable delegation metadata

- Runtime support for cron-triggered and onchain event-triggered skills

- Execution history for successful, failed, and skipped runs

- Pause, resume, and revoke controls for installed skills

- 1Shot delegated execution integration for submitting approved wallet actions

- x402 integration for paid external data fetching

- Venice AI reasoning flow for AI-assisted skills such as AI-Powered DCA

- Deterministic non-AI skill flow for event-based automation

- Landing page and product narrative around permissioned wallet skills

The main demo flow shows a user installing a bounded skill, reviewing its permission scope, optional x402 + Venice reasoning, and backend execution through delegated permission.

Not fundraising. SkillWallet* is currently a hackathon MVP / prototype. I am focused on validating the technical architecture, user experience, and permissioned wallet automation model before considering fundraising.