Sento Skills is a system for turning prompts, standards, and working methods into reusable capabilities. You can use official Skills right away or create your own custom Skills. Today, Skills are designed for text-based instructions and operating rules, not direct script execution. In the future, we plan to expand Skills with safer execution through sandboxing.
If a normal AI chat is temporary collaboration, Skills are closer to long-term working methods. Their value is not just adding another feature to AI. Their value is helping teams avoid re-explaining the same requirements, standards, and ways of working in every new conversation.
What Is Sento Skills
Sento Skills is a capability system that helps AI Chat remember how your team works. It is a good fit for things you use repeatedly, such as prompts, writing guidelines, task steps, role instructions, review standards, and team constraints.
In other words, Skills solves a simple problem: when your team already knows how something should be done, AI should not have to figure it out from scratch every time.
Why Teams Need Skills
Teams usually do not need Skills because they "do not know how to write prompts." They need Skills because proven methods are hard to reuse consistently.
Most teams run into the same issues:
- the same prompts get copied, edited, and rewritten again and again
- experienced people know what works, but their methods do not stick
- each teammate writes differently, so output becomes inconsistent
- as conversations and context grow, AI is more likely to drift
The biggest loss is often not failing to find a good method. It is finding one and still having to explain it over and over. Skills turns those scattered habits into reusable capability.
What Is the Difference Between Official Skills and Custom Skills
Sento Skills supports both official Skills and custom Skills. The first helps you start faster. The second helps you preserve your own way of working.
| Type | Best for | Best for whom |
|---|---|---|
| Official Skills | common tasks, familiar use cases, fast onboarding | people and teams who want to start immediately |
| Custom Skills | team standards, personal methods, long-term reuse | people and teams who want AI to follow their own working style |
This update also adds the new frontend-design skill, which helps tasks that need more complete UI direction and stronger visual output get to a better starting point faster.
If you are just getting started, the most natural path is usually to begin with official Skills and get a stable starting point. Once you already have a clear method worth preserving, you can turn it into a custom Skill.
What Custom Skills Are Good For
Custom Skills work best for things you find yourself explaining to AI repeatedly. If a method is likely to be reused later, it is probably worth turning into a Skill.
Common examples include:
- writing style and brand voice
- customer support, sales, or operations response principles
- internal review checklists and delivery standards
- product copy, design review, or research synthesis workflows
- decision frameworks used by founders, managers, or operators
Once these methods are captured as custom Skills, AI starts to feel less like a generic assistant and more like a system that follows your way of working.
What Sento Skills Is Best Suited for Today
At this stage, Skills is best for text-based rules, methods, and instructions. It is closer to a reusable library of working methods than a direct automation system.
| Better fit today | Not a fit today |
|---|---|
| writing rules, brand voice, task steps, review standards, role instructions, answer constraints | directly running scripts, calling local programs, treating a Skill as executable automation |
That is why Skills is especially useful today for content, operations, product, design, research, and team collaboration work. If the key to the task is how to think, write, judge, or execute against a standard, Skills is likely a strong fit.
Does Sento Skills Support Script Execution Today
Not yet.
Today, Skills is primarily built for text-based operations. You can write rules, steps, constraints, and even describe how a command should be used, but a Skill is still treated as a text-based method, not something that runs code directly.
We started with text on purpose. For most teams, getting the method clear matters more than jumping straight to execution. Over time, we plan to push Skills toward stronger execution capabilities and use sandboxing to support safer script execution. That would let some Skills do more than explain how to work. They could also perform practical actions inside an isolated environment.
How Skills Changes the AI Chat Experience
The core change is not "more features." It is less repetition and more consistent output.
In practice, that means:
- AI understands the task faster
- you do not have to rewrite the same prompts every time
- teams can align on one way of working more easily
- personal preferences and team standards can both be preserved
- repeated tasks become easier to reuse instead of re-figuring out
When official Skills and custom Skills exist together, AI Chat starts to feel less like a blank chat box and more like a workspace that gradually learns how you work.
Which Teams Are the Best Fit for Sento Skills
If your work includes repeated tasks or your team already has a standard way of doing things, Skills is likely a good fit.
These teams and roles often feel the value first:
- content teams that need consistency in voice, structure, and quality
- operations teams that handle similar plans, replies, and workflows every day
- design and frontend teams that want more consistent output and review standards
- founders and managers who want AI to reuse their decision framework
- small teams that want proven methods to live beyond one person's memory
In short, the more often a task repeats, the more it depends on experience, and the more it benefits from consistent standards, the more useful Skills becomes.
FAQ
Should I Start with Official Skills or Custom Skills
If you are new to Skills, official Skills is usually the best place to start because it is lighter, faster, and easier to build a habit around. Once you have a clear method worth preserving, adding custom Skills becomes natural.
What Should I Put into a Custom Skill
The best candidates are things you explain to AI repeatedly, such as writing requirements, brand voice, task steps, review standards, role instructions, and common constraints.
How Is a Skill Different from Saving a Prompt
Saving a prompt is more like saving a piece of text. A Skill is closer to organizing a reusable method of working. It is not only for one input. It is for helping AI stay more consistent across similar tasks over time.
Can Skills Run Scripts Directly
Not today. Right now, Skills is mainly for text-based rules, steps, style, and constraints. We plan to add safer script execution through sandboxing later, but the current focus is helping AI understand and reuse your method better.
Who Gets the Most Value from Skills
If you repeat the same type of work often, or if your team already has fixed ways of doing things, Skills will likely be useful. It is especially valuable for content, operations, design, product, and small-team leadership work.
This Is Just the Beginning
If AI Chat answers "how should we do this right now?", Skills is closer to "how do we keep doing this well over time?"
We want Skills to help teams preserve what already works, so AI does not just answer questions. It gradually starts to understand your standards, your preferences, and your way of working. You can start with official Skills today, then slowly build your own custom Skills over time. The first gives you speed. The second makes Sento feel more and more like an AI workspace built around your team.