Property:Agent tasks
Jump to navigation
Jump to search
| Property | |
|---|---|
| name | tasks |
| label | tasks |
| type | Special:Types/Text→Special:Types/Text |
| scope | |
| index | 5 |
| sortPos | |
| primaryKey | False |
| mandatory | False |
| namespace | Property |
| size | |
| uploadable | False |
| defaultValue | |
| inputType | textarea |
| allowedValues | |
| documentation | The tasks the AI Agent is designed to perform |
| values_from | |
| externalFormatterURI | |
| showInGrid | True |
| isLink | False |
| nullable | |
| topic | Concept:Agent→Agent |
This is a Property with type Special:Types/Text
A
Adding and updating contacts in the CRM system, tracking Wiedervorlagen (follow-up reminders), ensuring data quality, reminding users of pending tasks, maintaining customer relationship records +
Evaluating where AI can support business processes, designing hybrid teams combining human and AI capabilities, creating AI assistant roles with defined responsibilities and personalities, implementing AI-first organizational structures, guiding AI transformation strategies from vision to execution +
Writing new Python modules/classes/functions, refactoring for clarity and maintainability, writing and running unittest-based tests, debugging with tracebacks and systematic analysis, managing dependencies in pyproject.toml, reviewing type hint correctness, creating dataclasses, maintaining AGENTS.md files, running checkos for project compliance +
Writing LinkedIn articles, developing content strategies, crafting attention-grabbing headlines, building thought leadership, creating engaging narratives that resonate with professionals +
Evaluating software architectures for testability and maintainability, applying hexagonal architecture principles, separating core business logic from external dependencies through ports and adapters, defining clear boundaries between application layers +
B
Verifying that derived classes properly uphold the contracts of their base classes, checking that subtype relationships maintain behavioral compatibility, ensuring proper abstraction and data hiding in class hierarchies +
D
Checking that software modules properly hide implementation details behind well-defined interfaces, applying Parnas's information hiding principle to improve code modularity and maintainability +
S
Evaluating product design decisions, challenging assumptions about user experience, pushing for elegance and simplicity in software and hardware, questioning whether features truly matter to users +
T